privacy policy
Last updated: 2026-05-21
TL;DR: Review Guardian runs entirely on your device. We don't have a server. We don't collect, transmit, sell, or rent your data. No analytics, no telemetry, no tracking. Every feature is free — there are no payments, so there's no payment processor to share data with.
Our privacy stance
- No servers. The AI runs in your browser, not ours. We have no infrastructure that sees your data.
- No tracking. We don't see what you analyze, ever.
- No account. Install and go. No sign-up, no email required.
- No data collection. Reviews stay on Amazon's page; trust scores stay on yours.
- Minimal permissions. Amazon domains only. No "all websites" creep.
1. Who runs this extension
Review Guardian is published by Ethan Carlton ("we", "us"). Contact: open an issue on GitHub.
2. What data the extension processes
When you visit an Amazon product page on a supported storefront, the extension reads content that your browser has already loaded into the page — product title, average rating, and visible reviews. This processing happens locally in your browser. None of it is sent to any server we control.
2a. On-device AI
When you click "Deep Analyze with AI", a small sample of the visible reviews is passed to Chrome's built-in on-device AI model (Gemini Nano), available via the LanguageModel API in Chrome 138 and later. The model runs locally on your device. No network request is made by the extension to perform the analysis.
2b. What we store, where, and for how long
| What | Where | How long |
|---|---|---|
| Latest analysis (current product's trust grade + parsed reviews) | chrome.storage.session (preferred) or chrome.storage.local |
Session-only when supported; otherwise cleared on extension uninstall |
None of this data leaves your browser. We have no way to read it.
3. What we don't do
- We do not send your browsing history anywhere.
- We do not send reviews, product titles, or any Amazon page content to any server we control.
- We do not run any analytics, telemetry, error reporting, or crash logging.
- We do not sell, rent, or share your data with anyone, because we never have it.
- We do not embed third-party trackers, pixels, fingerprinting scripts, or ad SDKs.
4. Permissions we request and why
| Permission | Why we need it |
|---|---|
storage |
To remember the latest analysis locally on your device. |
activeTab |
So the popup can read which Amazon page you're currently looking at — only when you click the extension icon. |
scripting |
So the extension can inject the trust-grade badge into Amazon product pages. |
Host permissions for https://*.amazon.* |
So the content script can run on Amazon product pages. Chrome loads the script on all pages of the supported Amazon storefronts because Amazon's canonical product URLs put a product slug before /dp/, which narrower match patterns can't target. The script performs no work on non-product pages — it immediately returns on search results, the homepage, cart, checkout, and account pages. It never runs on any non-Amazon site. |
5. Where the extension activates
The content script is loaded by Chrome on all pages of Amazon's supported storefronts (.com, .co.uk, .ca, .com.au, .de, .fr, .es, .it, .in, .com.mx, .com.br, .co.jp, .nl, .se, .pl). This broad load is necessary because Amazon's canonical product URLs place a product-slug segment before /dp/ (e.g. amazon.com/Some-Product-Name/dp/B0XXXXXXXX), which Chrome's narrower path-match patterns can't target.
The content script performs no work — no DOM parsing, no badge injection, no message passing — on any URL whose path does not contain /dp/, /gp/product/, or /product-reviews/. On all other Amazon pages, the script is loaded but immediately returns.
6. Children's privacy
Review Guardian is not directed to children under 13 and does not knowingly collect data from anyone — including children.
7. Changes to this policy
If we change anything material about how the extension handles data, we'll update this page and bump the "Last updated" date at the top. We don't have a mailing list (because we don't collect emails), so check this page if you want the latest version.
8. Contact
Questions or concerns: open an issue on GitHub.