Privacy policy
Every claim below names the file in this repo that backs it.
Research behind the shape of this document: docs/research/2026-10-30-scraper-extension-policies.md (nine scraping
extensions) and docs/research/2026-10-30-refund-withdrawal-patterns.md (twelve products, EU/UK withdrawal).
1. Scope
This policy covers the Rowspell Chrome extension, its side panel and full-tab grid, the optional local bridge
(127.0.0.1), the optional AI assist, and this website (https://rowspell.com). It does not cover pages you visit with other software.
2. The short version
Rowspell extracts data from the page you are on, in your browser, and gives it back to you as a file. Scraped rows stay on your device. There is no account, no sign-up, no telemetry, and no analytics in the extension. Nothing is sent anywhere unless you turn on a feature that sends it, and each of those is listed in §4 with what it sends. We run no database of customers: when you buy Pro, the payment provider holds the purchase and we hold a signing key and nothing else (§7). Uninstalling the extension deletes everything it kept (§11).
3. What never leaves your device
- Rows you scrape, and every edit you make to them. They live in the panel’s memory while it is open, and in the full-tab grid’s memory while that tab is open. Neither survives closing it — the done screen says so.
- Rows an agent reads through the bridge (Pro). They are held in Chrome’s session storage, which Chrome keeps in memory and never writes to disk, so a run survives Chrome restarting the extension’s background worker. They are gone when you close the browser, reload or remove the extension, or once 20 newer agent runs have replaced them. Web pages cannot read this storage.
- Your recipes, your settings, your theme, your column choices.
storage.local, nothing else. - Exports. CSV, XLSX, JSON and NDJSON are built by the extension and handed to Chrome’s own download mechanism.
No server is involved in producing or delivering a file. With the agent bridge (Pro), your agent can also ask for a run
to be exported: the bridge running on your computer writes the files into
Downloads/Rowspell, and nowhere else. - Your API key for the AI assist, and the badge token for the bridge. Both are stored locally and marked
trusted-contexts only, so no page’s script can read them (
src/entrypoints/background.ts,tests/storage-access.spec.ts).
Removing the extension deletes all of the above. Chrome deletes an extension’s storage on uninstall; there is no copy anywhere else to ask us to delete.
4. What leaves your device, and only when you ask
4.1 The AI assist — off by default, and only on a page where you press the button.
When you enable it and use it, the extension sends two things to the endpoint you configured, using the key you
entered: your own query (≤300 characters) and an outline of the page built from its HTML
(src/lib/digest.ts). That outline contains the page’s title and the structure and text of its elements, truncated
to a fixed budget. It does not contain the page’s address — no URL, no hostname. The extension sends nothing to us
and nothing to any provider we choose: the provider is your choice and the key is yours.
We never receive, log, or store what your provider returns or what you sent it.
4.2 The local bridge — off by default, and it never leaves your computer.
When you pair a companion application, the extension connects to ws://127.0.0.1 — the loopback interface, which is
unreachable from any other machine. The connection is authenticated with a pairing token over a challenge-response
handshake, so the token is never sent to a port that cannot prove it already holds it (R-059). While it is connected,
the agent you installed can read the pages you scrape and run your recipes. Disconnecting ends it; nothing about the
bridge is stored anywhere but locally.
4.3 The licence check — only when Pro exists. Licensing makes three calls to one small service of ours, and only these three:
- Activate (when you press Activate): your licence key, a scrambled form of a random device id (a SHA-256 hash — the id itself never leaves the browser), and a device label such as “Chrome on Windows”.
- Renew (at browser start, from about day 30 of each 60-day lease): your licence key and the current lease.
- Release (when you free a device, this one or another): your licence key, the current lease, and for another device its activation id. If our service cannot be reached, this browser stops using Pro at once and the release is sent at the next browser start.
- Show devices (when you ask for the list): your licence key and the current lease. The answer lists the device labels your key is activated with. They pass through our service and are not kept.
The service checks the key with Dodo Payments and signs a 60-day lease. Dodo keeps a record of each activation, under its device label. The answer to Activate includes the name on your purchase, so the extension can show “Licensed to …”. That name passes through our service once and is kept only in your browser. It is not in the lease, so it is never sent back. Our service stores no customer data — no database, no customer list, no logs of who asked (R-053). After that, the lease is checked on your machine, offline. No page content is ever part of a licence call.
4.4 This website. We use no advertising or tracking cookies. If you email us, we have your email.
5. AI providers
The provider is whatever you configure: an OpenAI-compatible endpoint or Anthropic, with your own key. We are not a party to that call and cannot see it. Whether your provider trains on what you send is governed by your agreement with them, not this policy — which is precisely why the key is yours and not ours. The extension sends no identifier of you, no account, no device id, and no page address with the digest.
6. Account and licence data
There is no account. A Pro purchase creates a licence key, which the payment provider emails to you and which you enter in the panel. Our licence service sees the name on the purchase once, at activation, and does not keep it (§4.3). We never see your address or card.
7. Payments
Payments are handled by Dodo Payments as merchant of record: Dodo is the seller for the transaction, issues the
invoice, charges the applicable tax, and processes any refund. Card data never reaches the extension or us. Dodo
holds the purchase record and the email you gave it; that relationship is covered by Dodo’s own privacy policy, which
we link at checkout. See docs/store/refunds.md for how a refund works.
8. Other services we use
| Service | What for | What it holds |
|---|---|---|
| Dodo Payments | checkout, invoice, tax, refunds; licence-key issuance and activations | the purchase, your email, each activation and its device label |
| Our licence service (a Cloudflare Worker) | checking an activation with Dodo, signing a 60-day lease, listing your devices | nothing — only its signing key and a Dodo API key |
| Web hosting / email | this site, and answering you if you write | whatever you send us in an email |
We name each one because a list with “and other partners” in it is not a disclosure.
9. Cookies
The website sets none for advertising or tracking. The extension sets none and has no access to cookies it does not need.
10. What we never do
No telemetry. No analytics in the extension. No selling data. No advertising identifiers. No account. No reading pages
you have not scraped. These sentences match the listing copy word for word, and tests/privacy-copy.spec.tsx fails if
the app’s own wording stops agreeing with them.
11. Retention and deletion
- Scraped rows: until you close the panel or tab, or export them. Never anywhere else.
- Recipes and settings: until you delete them or uninstall.
- Licence: Dodo holds the purchase for as long as tax law requires; we hold nothing to delete.
- Emails: kept while the thread is live and then archived for reference, deleted on request.
To have anything of yours deleted, write to the address in §16. Because we hold no customer records, in practice that means “uninstall the extension” — and we will say so rather than pretend a deletion process exists.
12. Security
The extension’s storage is trusted-contexts only, so a page cannot read your key or token. The bridge handshake requires the token before the token is sent. Data files never transit a server. What we cannot promise: that your browser, your operating system, or a provider you configured is secure.
13. Your rights
EU/EEA/UK: you have the rights of access, rectification, erasure, restriction, portability and objection for any
personal data we hold — which, per §7 and §11, is essentially none. You also have the consumer rights in §4 of
docs/store/refunds.md, including the 14-day right to cancel a purchase.
California: you have the rights of the CCPA/CPRA, including to know, delete and opt out of sale — we do not sell personal information.
Contact route and response time: §16, answered within 30 days.
14. Children
Rowspell is not directed at children under 13, and we do not knowingly collect anything from them.
15. Changes
A change that affects what leaves your device is stated in the extension’s release notes and at the top of this page with a new date. We do not rewrite a policy to cover a feature we already shipped.
16. Contact and effective date
- Legal entity: Utkarsh Benjwal, trading as Unfolding Dimensions (sole proprietorship)
- Contact address: 23 Kanan Kunj, Sahastradhara Road, Dehradun 248001, India
- Email: unfoldingdimensions@gmail.com
- Effective date: 2026-11-16
Version: 1 (2026-11-16; draft 1 was 2026-10-30)
Research: docs/research/2026-10-30-scraper-extension-policies.md
Backing claims: src/lib/digest.ts, src/entrypoints/background.ts, R-053, R-059, docs/store/refunds.md