Website Roast

Last updated: 6 August 2026

Privacy Policy

This is the linkable policy for the Chrome Web Store listing. It is written to be true rather than reassuring; where the honest answer is "it depends which model you chose", it says that.

There is no server. Nobody operates a backend for this extension, so there is no account, no telemetry, no analytics, and no way for the developer to see anything you do with it.

The short version

What leaves your device depends entirely on which model you select:

Provider Does page content leave your device?
Chrome built-in (default) No. The model runs on your machine.
Your own API key Yes — to the vendor you chose, using your key.
Hosted Not implemented. There is no hosted option.

That distinction is shown in the extension's own interface, next to the choice, at the moment you make it. It is not only in this document.

What the extension reads

When — and only when — you click the toolbar icon and ask for a review, the extension reads the page in that one tab:

  • the document title, meta description, canonical link, robots directives, language, viewport tag, Open Graph and Twitter Card tags, and JSON-LD;
  • headings, navigation links, footer links, buttons and calls to action;
  • images, and their alt text, dimensions and formats;
  • form structure — how many fields there are, their types, and whether they have labels (never what has been typed into them);
  • computed styles: fonts, sizes, colours, element positions;
  • navigation and resource timing for that page load;
  • a sample of the page's visible text;
  • a screenshot of the visible part of the page.

What it never reads

  • Your browsing history.
  • Any tab other than the one you asked it to review.
  • Cookies, localStorage, sessionStorage, or any session state.
  • The contents of form fields, including anything you have typed.
  • Any page in the background, or before you ask.

The extension holds no host permissions. It is technically unable to read a page you have not explicitly asked it to review.

Redaction

Before the extracted content is sent anywhere or written to your disk, the extension removes:

  • email addresses;
  • phone numbers;
  • card-shaped numbers;
  • API keys, bearer tokens and JWTs;
  • anything labelled as a password or secret;
  • credentials and secret parameters embedded in URLs.

This is deliberately over-eager: it will sometimes redact something that was not sensitive. It runs even for the on-device model, because the review is also saved to your local history. The rules are in src/core/redact/ and are unit-tested against a fixture built to contain every category.

Provider A — Chrome built-in (the default)

Page content never leaves your device. Chrome's on-device model runs locally. The extension makes no network requests in this mode.

Chrome itself downloads the model. That download is between your browser and Google, is governed by Google's own terms, and happens once.

Provider B — your own API key

If you choose this, the extracted page content described above — and, only if you separately tick the box, a downscaled screenshot — is sent over HTTPS directly from your browser to the API vendor you selected:

It is sent with your API key, to your account. What that vendor does with it is governed by their terms, not by this document. Please read them; they differ on whether inputs may be retained or used for training.

Nothing is sent to the developer of this extension, because there is no server to send it to.

What is stored, and where

Everything is in chrome.storage.local on your device:

  • your settings;
  • your API key, if you supplied one — masked in the interface, never logged, removable with one click;
  • your last 50 reviews, including the screenshot of each;
  • a result cache so an unchanged page is not re-analysed, or re-charged for.

chrome.storage.sync is deliberately not used, so none of this is written to your Google account or synced to your other devices.

You can delete all of it at any time: Settings → "Wipe everything", which clears the history, the cache, the settings and any stored API key.

Third parties

None, other than the API vendor you explicitly choose in Provider B. There is no analytics, no crash reporting, no advertising and no data broker of any kind.

Children

The extension is not directed at children and collects nothing from anyone.

Changes

If this policy changes in a way that affects what leaves your device, the change will be described in the extension's release notes, not only here.

Contact

Raise an issue on the repository. There is no support address, because there is no organisation behind this — which is also why there is nowhere for your data to go.