Data, storage and privacy

What stays on your machine, what the account stores and how to remove it.

Mockrew is built around one constraint: your API traffic must never leave your browser. This page is the practical version; the legal one is the Privacy Policy.

Stays on your machine

Projects and rules — URL patterns, methods, conditions, status, delay, headers and bodies.
Faker templates and JS Hook source.
Sequence state, the request log (memory only, cleared when DevTools closes) and UI preferences.
Everything above lives in chrome.storage.local or in memory.

Never collected

Request URLs, headers, cookies, authorization tokens and request bodies of the pages you debug.
Response bodies — including the ones you capture into the log; capture is local and off by default.
Browsing history, form input or page content.

Stored on the server, only with an account

Data	Why
Name, email, avatar URL	Provided by GitHub / Google at sign-in, to identify the account
Subscription status and plan	To grant Pro and show the account page
Connected browser records	A label, connection date and a one-way hash of the device key — used to enforce the device limit and to let you unbind
Support emails	Only what you send us

There is no analytics or advertising script on this website, and the extension contains no telemetry.

Removing your data

Local rules — panel top bar → Export for a backup, then delete the project or uninstall the extension.
Account — email support to delete the account; device records and subscription data go with it.
Log — closing DevTools clears it; Clear empties it immediately.
Single browser — unbind it on the account page; the extension falls back to Free at its next check.

Export before you uninstall

Uninstalling removes the extension’s local storage. If the rules matter, export them first — the JSON file can be imported again in seconds.

Stuck, or need something clarified? support@mockrew.com·Terms of Service