Privacy

What never leaves your browser.

Scrapewright infers selectors from the page you click on, renders the live preview and generates the Python export — all of it inside the extension, in your browser. Page content, browsing history and anything you pick, preview or export is never sent anywhere. There is no telemetry: no usage analytics, no crash reporting, no event pings, in either the free or paid build.

Two things are read locally, and it is worth being exact about the difference between reading and sending. The panel describes one page at a time, so it looks at the tabs open in the current window and reads their addresses to work out which page that is — and to tell you when a saved recipe belongs to a different site than the tab you are on. When you save a recipe, the address it started from is stored inside that recipe, in the extension's own storage on your machine, until you delete it. Neither is transmitted, and no record of where you have been is assembled from either.

The network calls this extension can make.

Picking, previewing and copying CSV never touch the network — they work fully offline. Exactly two requests exist in the codebase, both to api.scrapewright.dev, both about licensing, and both absent entirely from the plain build (the one the automated tests run). Here is every occasion either one is sent:

• Licence validation — when you enter a Pro key, the extension sends that key and a random per-install identifier. The identifier is a UUID generated once on your machine; it is not a device fingerprint and carries no information about your browser, OS or identity.
• Licence re-check — once a key is activated the extension re-checks it with the licence server at most every 30 days, sending only the key and install id. This is the same validation request, made without you asking for it: it runs when you open the side panel, never on its own timer, and only once the 30 days have elapsed. It is what lets a refunded or revoked key stop working. If it fails, for any reason, nothing changes and your key keeps working.
• Free-key request — when you ask for a free key, the extension sends the email address you type in, so a key can be emailed to you.

Apart from that 30-day re-check, no call happens unless you take that action. Nothing is sent on install, and nothing about the pages you visit or the data you pick is ever sent anywhere.

What the licence server stores.

For each key: the email address it was issued to, the plan (free or Pro), and the small list of per-install identifiers that have activated it (used only to enforce the per-key install limit, with timestamps of first and last use). It does not and cannot store page content, browsing history or anything else the extension does not send it — described above, that's the key and the install identifier or an email address, nothing more.

Payment and email are handled by someone else.

Stripe processes the one-time Pro purchase. We never see or store your card details; Stripe's own checkout collects them directly. Resend delivers the licence-key emails on our behalf and sees the address and the key content of that one email — nothing else about you or your use of the extension.

This website has no cookies and no analytics.

Nothing on this site sets a cookie, runs an analytics script or tracks you across pages. The only assets it loads from elsewhere are the two Google Fonts used for typography.

Questions, deletion, anything else.

Write to [email protected] — for a question about this policy, to ask what's on file against your key, or to have your email and key record deleted. We reply from a person, not a ticket queue.

Changes to this policy.

If what the extension sends or what the server stores changes, this page changes with it and the date at the top moves. There is no separate changelog to check against.