Overview
ScrapeMaster (“the Extension”) is a free Chrome browser extension that helps you extract structured data from webpages. We are committed to protecting your privacy. This policy explains exactly what data the Extension collects, how it is used, where it is stored, who it is shared with, and the rights you have over it.
1. Data Collection
The Extension processes data in two distinct, well-defined scenarios, described below. Outside of these scenarios, no data is collected, transmitted, or retained.
1.1 Data extracted by you (stored locally only)
When you use the Extension to extract data from a webpage, the records you select — product names, prices, links, table rows, image URLs, free text, etc. — are read by the Extension and stored in your browser's local IndexedDB. This extracted data:
- Stays entirely on your device
- Is never transmitted to our servers or any third party
- Is exported to your device (as CSV, XLSX, or JSON) only when you click Download
1.2 Page HTML structure sent to auto-detect API (user-initiated)
When you click the auto-detect button, the Extension sends the HTML structure of the current page to our analysis API. The API returns suggested CSS selectors; the Extension then uses those selectors locally to perform extraction.
What is included in this request:
- The HTML markup of the page you are viewing
What is not included:
- Cookies, authentication tokens, or session data — Chrome strips these before our request
- Your IP address is not logged for purposes other than transient request handling
- Any personal account information
1.3 What is NEVER collected
Under no circumstances does the Extension collect any of the following:
- The data you extract — it stays on your device
- Your browsing history, URLs visited, or tab activity
- Cookies, login tokens, form data, or session data
- Analytics, telemetry, or usage statistics tied to your identity
- Device fingerprints, advertising identifiers, or persistent identifiers
- Personally identifying information
- Health, financial, authentication, or location data
2. Data Handling and Use
The data the Extension processes is used solely for these purposes:
- Extracted data (Section 1.1)is used only to populate the table you see in the Extension's side panel and to be exported by you. The Extension does not use it for anything else.
- Page HTML sent to auto-detect (Section 1.2) is used only to compute and return CSS selectors. After the request returns, the API discards the HTML — it is not stored, logged beyond standard transient request handling, used to train models, sold, or shared.
Your data is never used for any of the following:
- Advertising, retargeting, or marketing
- Sale, rental, or licensing to third parties
- Profiling, automated decision-making, or scoring
- Training of machine-learning models
- Any purpose unrelated to the Extension itself
3. Data Storage and Retention
3.1 Local storage (on your device)
The Extension stores the following data locally in your browser using chrome.storage.local and IndexedDB. This data never leaves your device:
- Extraction configurations — selectors and rules you create. Retained until you delete the configuration or uninstall.
- UI preferences — settings, delays, panel state. Retained until you change them or uninstall.
- Extracted records — the rows of data you extract. Retained in IndexedDB until you delete the run, export it and remove it, or uninstall the Extension.
You can delete all locally-stored data at any time by uninstalling the Extension or by deleting extraction runs from within the Extension's side panel.
3.2 Server-side storage (auto-detect API)
When you trigger auto-detect (Section 1.2), the page's HTML is processed by our analysis API in memory to generate selectors, and discarded after the response is returned. The API:
- Does not retain page content after the request completes
- Does not store user identifiers or session data
- Uses standard transient request logs (timestamps, error rates) for operational health; these logs do not contain page content
- Encrypts all transmission via HTTPS (TLS)
4. Data Sharing
The Extension does not sell, rent, lease, license, or otherwise distribute any user data to third parties for any purpose.
The only external network call the Extension makes is to our own page-structure analysis API (Section 1.2), and only when you actively click auto-detect. No other external services, analytics, tracking pixels, advertising networks, or telemetry endpoints are contacted.
We will only disclose user data to other third parties when required by valid legal process (subpoena, court order) and only to the extent legally compelled.
5. Permissions Explained
The Extension requests certain Chrome permissions to function. Each is documented below with its specific purpose; none enable data collection beyond what is described in Section 1.
| Permission | Purpose |
|---|---|
tabs | Identify the active webpage you want to extract from and open background tabs during multi-page crawls. |
scripting | Inject the extraction script that reads page content and pulls the data you have selected. |
sidePanel | Display the ScrapeMaster interface in Chrome's side panel alongside the page you are extracting from. |
storage | Save your configurations and preferences locally so they persist between sessions. |
unlimitedStorage | Store large extraction results locally without hitting Chrome's default storage limits. |
notifications | Alert you when long-running extraction jobs complete. |
webRequest | Detect when pages have finished loading during multi-page extraction so the script runs at the right time. |
declarativeNetRequest | Handle network requests so pages load correctly during extraction. |
host permissions | Allow extraction on any website you choose to use the Extension on. The Extension only reads pages when you actively run it. |
6. Your Rights and Data Deletion
You have the following rights at all times:
- Right to know. This policy lists every category of data the Extension processes. If you have questions about a specific item, email us (Section 9).
- Right to deletion of local data.Uninstalling the Extension deletes all locally-stored data immediately. You can also delete individual extraction runs from within the Extension's side panel.
- Right to access.You can review all locally- stored data through Chrome's DevTools storage panel, or export it to CSV / XLSX / JSON at any time.
- Right to control website access.Use Chrome's extension settings to limit which sites the Extension can access.
- Right to opt out of auto-detect. Never clicking auto-detect means no page HTML is ever sent to the analysis API. You can build extraction configurations entirely by hand if you prefer.
7. Data Security
All communication with the auto-detect API is encrypted in transit using HTTPS (TLS). The API does not retain page content after responses are returned. Locally-stored data uses Chrome's built-in storage isolation, which scopes it to the Extension and the browser profile.
We will publicly disclose, within 7 days, any unauthorized access to the auto-detect API affecting user requests, via an update to this page and the Extension's Chrome Web Store listing.
8. Cookies & Tracking
The Extension does not:
- Set or read cookies
- Track your browsing activity
- Collect analytics or usage data tied to your identity
- Use any third-party tracking tools
- Display advertisements
9. Children's Privacy
The Extension is not directed at children under 13 and we do not knowingly collect personal data from children. If you believe a child has used the Extension and you would like any locally- stored data deleted, simply uninstall the Extension — there is no server-side personal data to remove on our side.
10. Contact
Questions about this privacy policy, requests for data access or deletion, or any other concerns should be sent to:
Email: [email protected]
We respond to data-related requests within 30 days.
11. Changes to This Policy
If we update this privacy policy, the revised version will be posted at this URL with an updated effective date at the top of the page. We will never change the Extension to collect new categories of data without first updating this policy. Material changes that affect how existing user data is handled will be announced in the Extension's Chrome Web Store listing description.