Where your data goes.
This policy covers the Web To Tables browser extension and its information website. Extension behavior depends on the JSON profiles you import and the site permissions you grant.
Updated: November 6, 2026
1. Publisher and contact
Publisher: Pathnomic Labs FZ-LLC
Support and privacy requests: support@webtotables.com
2. Data processed
The extension stores JSON profiles, enabled states, site matches, extraction rules and destination configuration in local extension storage. API keys, bearer tokens and authentication headers that you include in a profile are stored as part of that configuration.
Depending on the profile, the extension may process page text, field values and selected network response bodies, including names, contact details or other information present in the source. Records may contain source URLs and page titles, timestamps, extracted fields, extraction metadata, raw response content and delivery results. A profile can disable retention of raw network payloads.
The extension does not enumerate general browser history, but it includes the processed page URL in records. It does not request access to browser cookies, the password vault, camera, microphone or geolocation APIs. Page and response content can nevertheless contain sensitive information; review the profile and the data you process.
3. When processing occurs
Once you grant site access to an enabled profile, extraction can run automatically on matching pages. The one-time run option injects the runtime into the active page for that visit. The latest ready draft is written to local storage before you click save.
Saving or sending updates the saved-record list. If a profile defines a destination status check (pageStatus), it can automatically contact the configured endpoint as soon as a draft is ready, without a separate send click. The request may include the source URL, profile-selected record fields and configured authentication credentials.
4. Purposes and sharing
Data is used for profile-defined extraction, local record management, checking for existing destination records, choosing a destination and sending records. JSON exports and clipboard copies require user action.
The extension contains no built-in advertising, analytics, tracking service or fixed publisher collection endpoint. The publisher does not sell extension data or use it to build advertising profiles. If your profile configures a remote destination, the relevant data goes to that destination’s operator. A destination could itself be a publisher-operated service; the profile configuration determines the recipient.
Destination services have their own privacy and retention practices, and their location determines where transferred data is processed. Use trusted profiles, inspect their destinations and use HTTPS for personal data transfers.
5. Retention and control
Profiles, saved records and the last ready draft remain in chrome.storage.local without a fixed expiry. The extension does not use browser sync storage. This is not a separately encrypted credential vault.
You can delete individual saved records or clear the record list from the records tab. Deleting a profile preserves saved records. Clearing the record list does not clear profiles or the separately stored last ready draft. Disabling a profile stops further processing; it does not recall prior requests or delete previously stored data.
You can revoke site permissions, close matching pages and uninstall the extension to remove its local extension storage. Exported files and data already sent to destinations remain separate and must be deleted at their respective locations or services.
6. Permissions
storage stores profiles, settings, records and the last draft. unlimitedStorage accommodates large records and raw response content. activeTab enables a user-triggered one-time run. scripting runs bundled extraction code on permitted pages. Optional host permissions cover profile-configured source pages and destination APIs; installation does not grant persistent access to all sites. Review the browser permission prompt, especially for profiles requesting broad matches.
7. Website and support
This information website has no analytics scripts, advertising cookies, contact form or user accounts. Hosting and network infrastructure processes IP addresses, requested URLs and technical connection information to serve pages. Application web-server access logging is disabled; reverse-proxy, security and error logs may be retained according to infrastructure configuration.
If you email support, your address, message and information you choose to share are processed to respond to your request. Do not send API keys, tokens, full profiles or real personal records; use redacted examples.
8. Requests and updates
Contact support@webtotables.com for access, correction, deletion or other applicable requests concerning support correspondence or personal data held by the publisher. The publisher cannot remotely access your browser’s local records. Use the local deletion controls described above and contact destination operators for data already transferred to their services.
We will update this page and its date when product behavior or data practices change.