Privacy
A short list, because there is not much on it. Selling a privacy tool while harvesting its users would be an odd way to run a business.
Last updated 21 August 2026
What we never receive
The browser runs on your machine. It connects to your targets over your network and your proxies, and no traffic passes through us. We do not receive, and could not produce if asked:
- The URLs you visit or the pages you load
- Page content, screenshots, form data or credentials
- Your proxy addresses or their credentials
- The personas you generate or the profiles you store
- Anything about what you automate or why
What we do hold
Your account
An email address, the time the account was created, and a Stripe customer id. The address is how you sign in and how we send your license key. There is no password, so there is no password to lose.
License checks
When the client validates a key it sends the key, a machine id derived locally, and optionally a hostname. We store the machine id and hostname so the dashboard can show you which machines hold seats and so you can free one. The key itself is never stored, only a SHA-256 hash of it, which is why we cannot show you a key twice.
The machine id is a stable local identifier, not a hardware serial number, and it is meaningful only to your own licence. Hostnames are whatever your machines call themselves; if that is sensitive in your environment, the client can omit it.
Payments
Handled entirely by Stripe. Card numbers never reach this site, checkout happens on Stripe's own pages, so we are outside PCI scope by construction. We keep the Stripe customer and subscription ids needed to know whether your licence is paid up. Stripe holds the rest under its own privacy policy.
Operational logs
Ordinary server logs, request paths, status codes, timestamps and IP addresses, kept briefly to debug failures and to enforce rate limits. Rate-limit counters are keyed on a hash rather than on the raw key.
Analytics and tracking
None. No analytics scripts, no advertising pixels, no third-party tags, no cookie banner because there is nothing to consent to. The single cookie this site sets is your session cookie, which exists only so that being signed in means something. It is HttpOnly, SameSite=Lax, and expires after thirty days.
How long it is kept
| Data | Kept |
|---|---|
| Account and licence records | While the account exists, then deleted on request |
| Sign-in links | 15 minutes, single use, deleted once expired |
| Sessions | 30 days, or until you sign out |
| Seat activations | Until you release the seat or the licence ends |
| Payment records | As long as tax and accounting law requires |
Your rights
Write to support@normalbrowser.com to get a copy of what we hold, correct it, or have it deleted. Deletion means the account, its licences and its activation records; payment records we are legally required to retain are the exception, and we will say so specifically rather than using it as a general excuse.
If you are in the UK or EU, the lawful basis is contract for anything needed to provide the licence, and legitimate interest for security logging and rate limiting.
Who else touches it
- Stripe, payments and billing
- Resend, transactional email (sign-in links, licence keys)
- Our hosting and database provider, running this site
That is the complete list. There is no data broker, no advertising network and no analytics vendor on it.
Changes
If this page changes in a way that affects what we collect, the date at the top changes and we will email account holders. See also terms and acceptable use.