CREATOR RADAR

Privacy Policy

Last updated: August 10, 2026

Summary

Creator Radar runs almost entirely in your own browser. Everything it reads from Trybe, Meta, Amazon, and TikTok stays on your device, and — only if you choose to connect it — in a Google Sheet in your own Google Drive. The one exception is license activation: the email you enter to activate your purchase is checked against our payment processor to confirm it's valid, as described below.

What Creator Radar reads

Creator Radar only runs on pages you're already logged into on these sites, and only reads what's already visible on the page:

It does not read any other site, and it does not read private messages, payment information, or account credentials on any of these sites.

Where your data is stored

Everything Creator Radar captures — your brands, commission terms, ad activity, and everything else it reads — is stored locally in your browser (using Chrome's built-in storage API), on your own device, and is never transmitted anywhere. The only thing that ever leaves your browser is the email you use to activate your license, described below.

Google Sheets sync (optional)

If you choose to connect a Google Sheet, Creator Radar requests one Google permission: see, edit, create, and delete files you open or create with this app (auth/drive.file). This is a narrow, file-scoped permission — it only ever applies to the one spreadsheet Creator Radar itself creates for you. Creator Radar cannot see, access, list, or read any other file in your Drive, and never requests broader access to your Google Sheets or Drive account as a whole.

This spreadsheet is created in your own Google Drive, under your own Google account, and no one other than you has access to it unless you choose to share it. You can revoke Creator Radar's access at any time from your Google Account permissions page.

How this data is protected: the OAuth access token used to write to your spreadsheet is issued and held entirely by Chrome's own built-in identity API — Creator Radar's code never stores it, and it is never transmitted to or held by any server Creator Radar operates. All communication with Google's APIs happens directly between your browser and Google's servers over HTTPS. The only thing Creator Radar stores locally about this connection is the created spreadsheet's ID (so it knows which sheet to keep syncing to) — never the spreadsheet's actual contents, which live solely in your Google account.

Retention and deletion: the locally stored spreadsheet ID is kept only for as long as you stay connected. Clicking Disconnect in the dashboard immediately deletes this local reference (Creator Radar never deletes the underlying Google Sheet itself, since it's your file — you can delete it directly in Google Drive at any time). Revoking access from your Google Account permissions page immediately and permanently revokes Creator Radar's ability to access that file, independent of anything in the extension itself. Uninstalling the extension has the same effect as Disconnect — all locally stored data, including this reference, is deleted by Chrome automatically.

License activation

Creator Radar requires a valid purchase to run. When you enter your email to activate it, that email is sent to a small server function we operate, which checks it against our payment processor (Stripe) to confirm a matching purchase exists, then returns a yes/no answer. We don't keep a database of activation attempts — the check happens live, on demand, and nothing beyond what's needed to process that one request is retained on our end.

Your browser stores the activation result locally (your license email and whether it's currently valid), and re-checks it periodically in the background to keep your access up to date.

What Creator Radar does not do

Changes to this policy

If Creator Radar's data handling changes in the future, this page will be updated first, with a new "last updated" date above.

Contact

Questions about this policy or how Creator Radar works can be sent to wendy.jo.davis@gmail.com.