This page is a working product document, not legal advice. Replace the placeholder domain and contact details, then have the final policy reviewed for the jurisdictions where you publish the extension.
1. Scope
This Privacy Policy applies to the Table Capture & Extractor Chrome extension and this website. The extension’s single purpose is to let a user capture tabular content they choose, inspect or repair the result, and export it in a useful format.
2. Data the extension handles
When you ask the extension to capture a table, it reads the relevant content from the active page. Depending on the source, that content may include visible cell text, links, values from form controls, table structure, the page URL, and diagnostic information needed to build the capture.
When you use PDF capture, the extension processes the PDF file you select. If you paste a direct PDF URL, the browser requests that file from the remote host. The remote host may receive ordinary request information such as your IP address and browser headers under its own privacy policy.
3. Local storage
The extension uses Chrome local extension storage for settings such as language and enabled state, user-created extraction recipes, and the current Table Studio draft. A draft may include captured cells, links, structural diagnostics, source URL, source type, and capture time.
This information stays in the browser profile unless you export it, copy it, explicitly load a remote file, or use a future integration that clearly states a different data flow. You can remove locally stored extension data by clearing the extension’s storage or uninstalling the extension.
4. Data we do not currently collect
The current version does not require an account, send captured tables to a developer-operated processing server, use captured content for advertising, sell captured data, or run third-party analytics inside the extension.
If any of these practices change, this policy and the Chrome Web Store privacy disclosures must be updated before the new handling begins. Where required, the product must also show a prominent disclosure and obtain informed consent.
5. Permissions
The extension uses Chrome permissions to access the active page, run capture scripts, store local preferences and drafts, create downloads, provide context menu actions, use an offscreen document for supported processing, and write requested data to the clipboard. Host access supports table detection and user-initiated capture on websites.
Permissions should be limited to what the current user-facing features require. The Chrome Web Store listing, developer dashboard disclosures, this policy, and actual extension behavior should remain consistent.
6. Sharing and Limited Use
Captured page and PDF content is used only to provide the table capture, repair, and export features requested by the user. It is not used for personalized advertising and is not made available for humans to read.
The use of information received through Chrome APIs will comply with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data will not be transferred except where necessary to provide a clearly disclosed feature, comply with applicable law, protect security, or complete a business transfer with any consent required by policy or law.
7. Security and retention
Local processing reduces external transmission but does not remove every risk. Protect your browser profile and device, review captures that may contain personal or sensitive information, and avoid exporting data to locations you do not trust.
The current Table Studio draft remains in Chrome local extension storage until it is replaced or the storage is cleared. Exported files are retained wherever you choose to save them and are outside the extension’s control.
8. Contact and changes
Before publication, replace this paragraph with a monitored privacy contact email and the legal name and address of the developer or business responsible for the extension.
Material changes will be reflected by updating the effective date. If a change introduces a new user data practice, additional notice or consent may be required before that practice begins.