Privacy

What never leaves your browser.

Scrapejig 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 (your picks, the flow mode and any drill-down, kept together) 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.

Why a local web scraper is different.

Most web scraping tools are cloud services: you point them at a page, their servers fetch it, and the extracted data sits in someone else's database until you export it. Scrapejig is a local web scraper. Working out the selectors, the preview and writing the code all run inside the extension on your machine, and the Python scraper it exports runs on your machine too, talking only to the site you are scraping. No server of ours has ever seen a page you scraped, because there is no server in the scraping path at all. The only requests the extension makes are the licensing calls listed in the next section, and none of them carries page content.

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.scrapejig.com, 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 — the one request you did not personally trigger, so here it is in full. 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. That address is then used for one thing more: a single follow-up email from [email protected] about a week later, asking whether Scrapejig worked for you and inviting an honest review of it on the Chrome Web Store, good or bad. That is the whole of it — no marketing, no newsletter, no second ask — and replying "stop", or using the unsubscribe line in that email, ends it.

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. A key record is kept for as long as the key exists. A launch-list address is deleted after the launch email is sent, or sooner if you ask.

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 sends the email that carries your key, so it handles that email's address and contents, and nothing else about you. It is named here because a sub-processor you cannot see is worse than one you can. The address you bought under is used for one thing more, the same as above: a single follow-up email from [email protected] about a fortnight after the purchase, asking whether the export earned its keep and inviting an honest review, good or bad. No marketing, no second ask, and replying "stop" — or using the unsubscribe line in that email — ends it.

Who is responsible for this data.

Scrapejig is the trading name of a sole trader in England, and that sole trader is the data controller for everything on this page. The operation is one person, so there is no data protection officer. Write to support@scrapejig.com and you have reached the controller, not a department.

Why we are allowed to hold it.

Different things are held for different reasons, and UK GDPR treats those reasons differently, so they are listed separately rather than as one blanket claim.

• Your email address and licence key — the contract you entered when you bought Pro or asked for a free key (Article 6(1)(b)). Without the address there is nowhere to send the key; without the record there is nothing to validate against.
• The per-install identifiers on a key — our legitimate interest in enforcing the per-key install limit and letting a refunded or revoked key stop working (Article 6(1)(f)). The identifier is a random UUID, not a fingerprint, and it is the least we can store and still enforce the limit.
• The single follow-up email described above — our legitimate interest in finding out whether the thing worked and being reviewed honestly (Article 6(1)(f)). One email, it carries an unsubscribe line, and replying "stop" ends it. That is the right to object, exercised in one word.
• The launch-list address — your consent, given by typing it in and pressing the button (Article 6(1)(a)). You can withdraw it at any time by writing to support@scrapejig.com, and withdrawing costs you nothing else.

There is no marketing list. Beyond that one follow-up and the one launch email you asked for, we do not email you. If that ever changes you will be asked to opt in first.

How long it is kept.

Plainly: nothing on the licence server deletes itself on a timer. A key record — the address, the plan, the install identifiers — is kept until you ask for it to go, and asking is enough, with no reason required. The install identifiers go when the record they belong to goes.

Two things are worth knowing before you ask. Deleting a live Pro record deactivates the key, so we will say so first and only do it if you still want it. And the payment reference on a Pro record is kept for six years, because that is how long UK tax law requires records of a sale to be kept — the reference, not your card details, which we never had.

A launch-list address is removed once the launch email has gone out, or sooner if you ask. That removal is done by hand, not by a schedule.

Where in the world it goes.

Three companies touch it, and all three are American. Stripe processes the payment, Resend delivers the email that carries your key, and Cloudflare serves this site and runs the licence server. All three are certified under the UK extension to the EU–US Data Privacy Framework, which is what makes the transfer lawful; anything falling outside it is covered by the UK's International Data Transfer Addendum to the standard contractual clauses. So your email address leaves the UK. Nothing about the pages you visit or the data you pick ever does, because it never leaves your browser in the first place.

What you can make us do.

Under UK GDPR you can ask us to tell you what we hold about you and give you a copy; correct it if it is wrong; delete it; restrict what we do with it; hand it to you or to another provider in a machine-readable form; and object to anything we do on the legitimate-interest basis above. Write to support@scrapejig.com. We answer within one month, it costs nothing, and you do not have to say why you are asking.

If we handle it badly you can complain to the Information Commissioner's Office, at ico.org.uk/make-a-complaint or 0303 123 1113. We would rather you came to us first, but that is your right, not our permission.

This website has no cookies, no analytics, and one form.

Nothing on this site sets a cookie, runs an analytics script or tracks you across pages. The two typefaces are served from this domain, not from Google, and the Content-Security-Policy this site sends blocks third-party scripts, styles, fonts and images outright. The one thing we do not control: Cloudflare serves the site, so it sees the IP address of every request, and it rewrites the plain-text email addresses on this page into an obfuscated form to keep scrapers off them — which is why this page loads one small script from a /cdn-cgi/ path. It is Cloudflare's, it decodes an email address, and it is the only script on the page. Cloudflare's response headers also carry a network-error policy that would report a failed connection to a.nel.cloudflare.com, its own reporting service — the only other place any data about this page's requests can go.

The one exception is the launch-email box on the homepage. It sends the address you type, and nothing else, to api.scrapejig.com over HTTPS when you press the button — never before. It is stored in the same store as licence records, under a hashed key, alongside the address and the time. It is used for one email from support@scrapejig.com when the extension reaches the Chrome Web Store, and for nothing else. To have it removed, before or after that email, write to support@scrapejig.com.

Questions, deletion, anything else.

Write to support@scrapejig.com — 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. A change worth noticing is written up on the changelog as well.