Privacy Policy
Last updated: April 2026
ScraperQ ("the Extension", "we", "our") is a Chrome Extension that helps users extract structured data from web pages. This policy explains what data we collect, how we use it, and your rights.
1. Data We Collect
1.1 Account Data (Google Sign-In)
When you sign in with Google, we receive from Google's OAuth service:
- Your name, email address, and profile picture URL
We use this to create and identify your account. We do not store your Google password.
1.2 Authentication Tokens
We store JWT access tokens and refresh tokens issued by our
backend server in chrome.storage.local so users do not need to sign in every time
they reopen the extension. These tokens are used only to authenticate requests to our backend
API and are cleared when the user signs out.
1.3 Scrape Templates
Templates you create (selectors, field names, target URL patterns) are stored on our servers, linked to your account. They are not shared with other users.
1.4 Scraped Data
Data extracted from web pages is processed locally in your browser and transferred directly to your chosen export destination (e.g. Google Sheets, downloaded file). We do not store, read, or retain the scraped page content on our servers.
1.5 Page Inspection and API Replay Refresh (chrome.debugger)
When you set up a new scrape template, and when you explicitly start an API-based scraping job, the Extension may use Chrome's DevTools Protocol (CDP) to inspect the current page's DOM structure and network requests. This inspection:
- Runs only while you are actively configuring a template or explicitly starting an API-based job — never for unrelated background browsing
- Is performed locally inside your browser to detect endpoint structure and temporarily refresh runtime request authentication details
- Does not store
Authorizationvalues, cookie values, CSRF values, signed headers, or session tokens on ScraperQ servers - May send the first page of a matched API response to ScraperQ's backend only when the user asks ScraperQ to generate an API-based template, so the backend can identify the items array path, pagination pattern, and stable field structure
- Stores only a bounded first-page sample of the matched API response for template-analysis purposes; ScraperQ does not store the entire paginated dataset for the site
- Does not store secret auth values even when a first-page API sample is retained; secret-bearing headers, cookies, tokens, and similar credentials are excluded from backend storage
- Requires your explicit one-time consent before first use
1.6 Usage / Telemetry
We do not collect analytics, usage telemetry, or crash reports.
2. How We Use Your Data
| Data | Purpose |
|---|---|
| Name, email, profile picture | Account identification, display in the Extension UI |
| JWT tokens | Authenticating API requests to our backend |
| Scrape templates | Storing and syncing your templates across devices |
| Page inspection data | Building an accurate scrape configuration, identifying API pagination and items paths, and refreshing local API replay auth when the user starts an API-based job |
3. Data Sharing
We do not sell, rent, or share your personal information with third parties, except:
- Google OAuth — used solely to authenticate you; governed by Google's Privacy Policy
- Legal obligation — if required by law
4. Data Retention
- Account data and templates are retained as long as your account is active.
- You may delete your account and all associated data by contacting us at privacy@scraperq.com.
- JWT tokens remain in
chrome.storage.localuntil the user signs out or the extension data is cleared.
5. Security
- Access tokens are stored in
chrome.storage.localso login persists across extension reopen. - All communication with our backend uses HTTPS.
- We do not store secret API authentication values on our servers.
- We store only sanitized API metadata and the first-page response context needed to generate scraper configuration, infer items paths, and detect pagination behavior.
6. Permissions Explained
| Permission | Why it is needed |
|---|---|
sidePanel | Display the ScraperQ UI in Chrome's side panel |
activeTab | Read the URL and title of the current tab |
storage | Persist templates, settings, and scrape state locally |
scripting | Inject selection-helper and crawler scripts into pages on demand |
tabs | Manage background scraping tabs |
identity | Perform Google OAuth sign-in via chrome.identity |
downloads | Save scraped data files to your computer |
debugger | Inspect page structure and network requests during template setup and, for API-based templates, at job start to locally refresh temporary replay auth details |
<all_urls> (optional) | Access any website you want to scrape — requested at time of first scrape |
7. Your Rights
- Access: You can request a copy of data we hold about you.
- Deletion: You can request deletion of your account and all associated data.
- Portability: Templates can be exported at any time.
Contact: privacy@scraperq.com
8. Changes to This Policy
We will notify users of material changes by updating the "Last updated" date above. Continued use of the Extension after changes constitutes acceptance.
9. Limited Use Statement
ScraperQ uses information obtained from web pages and web requests only to provide the user-facing scraping and API replay functionality requested by the user. ScraperQ does not use this information for advertising, profiling, resale, or unrelated analytics. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Also see our User Data Disclosure for the Chrome Web Store submission details.