Skip to main content

Data privacy

Privacy friendly

No third-party cookies, no fingerprinting, and no stored IP addresses.
The collector does not store:
  • IP addresses. It looks up the country in memory (Cloudflare’s published geofeed, then the DB-IP country database) and discards the address. No IP is sent to a lookup service, stored, queued or logged. For projects with a game, install attribution keeps a keyed hash of the IP for 72 hours to link a first game open to a website visit. An owner or admin can turn it off.
  • Raw user agents. It keeps only the derived device, OS and browser.
  • Full URLs. It removes query strings and fragments, and keeps only allowlisted campaign fields.
  • Fingerprints. The visitor ID is a random UUID that the SDK stores in a first-party cookie. It is never derived from request data.
See what we collect for every field. Use consent mode if your site needs consent before analytics storage.

Data storage

  • Events, profiles and traits are stored in the analytics database (Tinybird).
  • Application data (workspaces, members, projects, dashboards, alerts, key hashes) is stored in Postgres.
  • Secrets are never stored in clear text. Secret keys and API keys are stored only as SHA-256 hashes, and each one is shown once. The Publishable key is safe to ship in a page or a game build: it can only send website and game events. Alert destinations, webhook signing secrets and billing provider secrets are encrypted with AES-256-GCM.

Data export and deletion

Contact support to export or delete a project’s data, or one user’s data by user_id. Anonymous events that cannot be linked to a known user are outside a per-user request.

SDK source

The Web SDK has the MIT license. During early access, the SDKs are available on request (use the Contact page of the Untitled Analytics website, /contact), and you can read exactly what runs on your site. The source will be published at launch.

Dependency and code scanning

Dependabot checks the npm packages, GitHub Actions and the API Docker image every week, and opens pull requests for security fixes. CodeQL scans the TypeScript and JavaScript code and the CI workflows on every pull request and every week.

Subresource Integrity and CSP

The setup page gives a pinned SDK script with a Subresource Integrity hash, so a changed file cannot run on your site. If your site sends a Content Security Policy, allow the SDK’s script host and the collector endpoint.

Bot traffic

Known bots and crawlers are labelled with the device bot. Reports exclude them by default, so bots do not inflate visitors or page views.

Account security

SSO

Sign in with an email code, Google or SAML single sign-on.

MFA

Authenticator codes, and a verified session for sensitive changes.

Roles

Owner, admin, editor and viewer, invitations and the audit log.

CSP

Content Security Policy for your site and for the dashboard.
The dashboard and API send Strict-Transport-Security, X-Content-Type-Options: nosniff, Referrer-Policy and X-Frame-Options: DENY on every response.