Security
You sign in with a one-time code or link sent to your email. Each works once and expires after 15 minutes.
Server API keys and any remaining passwords are stored only as one-way hashes, so even we can’t read them back.
The tracking code carries an integrity fingerprint. Browsers refuse to run a copy that has been changed.
Emails, phone and card numbers, tokens and passwords are stripped from addresses, events and error messages before anything is saved.
HTTPS everywhere, a strict content security policy, no framing, and rate limits on sign-in and every API.
Uptime checks, scans and data reads never reach private network addresses, and only run on sites you’ve proved you own.
Supabase and your own endpoints share counts through token-protected connections. Analify never holds database passwords. Google Search Console access is encrypted at rest.
The database is copied every day: seven days of copies on the server and 30 days off-site. Server errors alert the team straight away.
Analify runs on Fly.io in London, United Kingdom. Analytics history is kept for as long as your plan allows, then deleted automatically. Deleting a website or your account deletes its data. Where it’s stored, who processes it and how long each kind is kept are on the data handling page.
Please tell us privately through the contact form (choose “Security report”) with steps to reproduce it. Give us a reasonable time to fix it before sharing it publicly, and don’t access other people’s data or disrupt the service while testing. We’ll keep you updated and credit you if you’d like.