Security
Last updated 6 November 2026
What we do to keep your account and the visitors you count safe. The binding version is section 4 of the data processing agreement, and this page never promises more than it does. Questions, or something to report: [email protected].
Where your data lives
The service and its databases run on servers in the EU. Cloudflare sits in front of them for TLS and a web application firewall. Session recordings, page snapshots and backups are kept in a private bucket at OVHcloud in Frankfurt, Germany. Paid plans are sold by Paddle, our merchant of record, so card details never reach our servers.
| Company | What for | Where |
|---|---|---|
| Cloudflare, Inc. | Edge network, DNS, TLS and web application firewall in front of the portal and the collector; the bot check on the sign-in form (Turnstile) | Global edge |
| Hetzner Online GmbH | Servers running the service, its databases and their nightly backups | EU (Germany / Finland) |
| OVH SAS (OVHcloud) | Storage for session recordings, page snapshots for heatmaps, and database backups (Object Storage) | Germany (Frankfurt, EU) |
| Scaleway SAS (Transactional Email) | Email: sign-in codes, workspace invitations, allowance notices and scheduled reports | France (EU) |
| Paddle.com Market Ltd | Merchant of record for paid plans: checkout, invoices, VAT, refunds | UK / EU |
| Slack Technologies, LLC | Notices to our own team about new accounts, with email addresses shortened to their first letter and domain | United States |
Your visitors
- Cookieless by default: the script sets no cookie and stores nothing in a visitor's browser until your site says they consented.
- No IP address is ever stored, logged or put in a backup. A visitor is a hash made with a secret that changes every day and is never backed up, so a visitor cannot be followed from one day to the next.
- Query parameters that carry tokens, email addresses and the like are dropped before anything is stored.
- The script counts only on the domains you list for the site, and is served from a separate collector domain, never from the portal's.
- Session recordings mask what visitors type, and are made by default only of visitors who consented or whom your site identified.
- Recordings and page snapshots are played on a separate domain of their own, in a frame that cannot reach the portal, through links that expire.
- A logged-in user is linked to your own id only when your site says so, and can be signed by your server so nobody can claim to be someone else.
Your team's accounts
- You sign in with a one-time code we email you, so there is no password to leak. The code is stored only as a keyed hash, lives ten minutes, and wrong guesses burn it. Asking for a code answers the same whether or not the address has an account.
- Before a code is sent, a bot check (Cloudflare Turnstile) makes sure a person is asking, and codes are limited per connection and per address.
- Two-step sign-in with an authenticator app is on every plan, with ten backup codes that each work once.
- On Business you can require two-step sign-in for everyone in the workspace, and sign your team in through your company's own provider over OpenID Connect.
- Workspaces have owner, admin, member and viewer roles. A viewer reads everything and changes nothing, and viewers are unlimited on every plan, so nobody shares an account to save a seat.
- An audit log records who changed what, on every plan, and you can read it from Pro.
Keys and AI assistants
- A site's key (
ans_) is public: it only says which site an event belongs to, and counts only on that site's domains. - API keys (
ank_) are scoped, shown once, stored only as hashes and revocable. - AI assistants connect over MCP with OAuth 2.1 and PKCE, act with the role of the person who connected them, and your workspace chooses who may connect one.
- We run no AI ourselves and send nothing to an AI company.
How we run it
- TLS on every connection, with HSTS. The portal loads scripts only from its own address, never the tracker or anyone else's, and no other site can frame it.
- Server secrets are kept encrypted, out of the code and the databases.
- Every image is scanned for known vulnerabilities before it deploys.
- Our logs record identifiers and outcomes only: which route was called, never a body, an IP address, an email or a query value.
- Our operator console answers only on our private network and asks for an authenticator code at every sign-in.
If something goes wrong
If a breach affects personal data we hold for you, we tell you without undue delay, as the data processing agreement sets out.
Report a vulnerability
Email [email protected] with what you found, how to reproduce it and what it affects. Please test in a workspace of your own, touch no one else's data beyond what shows the problem, don't degrade the service for others, and give us the chance to fix it before telling anyone. Good-faith reports are welcome, and we will tell you what we do about yours.
Machine-readable contact: /.well-known/security.txt.