Security and privacy, built in.
How we protect your data and your players' data today, and the work still in progress before the hosted launch. Each item says whether it is in place, in progress or planned.
Privacy by design
The collector uses the IP address only in memory to look up the country. It never stores or logs it.
A first-party anonymous ID and the user IDs that you send. No third-party cookies and no fingerprinting.
Bot traffic is labelled at ingest and left out of every report by default.
Project and data subject exports and deletions run through a documented procedure on request.
Encryption
The app, the API and the collector are served over HTTPS. Database connections verify TLS certificates.
Our database and analytics providers encrypt stored data at rest.
Webhook URLs, webhook signing secrets and billing and Steam provider keys are encrypted with AES-256-GCM before they are stored.
Secret keys and API keys are stored only as SHA-256 hashes. A key is shown once, when you create it. Publishable keys are public by design and only allow sending website and game events.
SDK and supply chain
The script snippet pins an exact SDK version with its SRI hash, so a changed file on the CDN cannot run on your site.
The app sends a CSP in report-only mode. We will enforce it before the public launch.
The npm package will be published from CI with provenance and no long-lived tokens.
Access control
Workspaces have Owner, Admin, Editor and Viewer roles, with least privilege on every project route.
Sensitive actions, such as key creation, member changes and billing, need a verified MFA session.
Changes to members, keys, dashboards, segments and alerts are recorded with who made them.
Each API key carries only the scopes it needs. MCP requests have per-key and per-workspace rate limits.
Google and SAML sign-in are supported in the app and are being set up for the hosted service.
Application security
SQL Explorer validates each query and runs it with a short-lived credential limited to your project.
Alert webhooks go only to public HTTPS addresses and are signed, so you can verify each delivery.
Ingest rate limits per project, and workspace suspension for Terms of Service violations.
Every change runs unit tests and CodeQL code scanning before it merges. Analytics query tests run against a local copy of the analytics store.
An external penetration test before general availability.
Infrastructure and operations
The service runs on Vercel, Railway, Supabase, Tinybird and AWS. Event ingestion and analytics storage run in the AWS Frankfurt region (eu-central-1).
We are confirming and documenting backup and restore for the database and the analytics store.
Error tracking, uptime checks, alarms and an incident response process, with a public status page.
Compliance and payments
Paddle processes all payments. We never see or store card data.
Our DPA and the list of subprocessors are being finalized.
We plan a SOC 2 readiness review after launch.
Report a vulnerability
If you find a security issue, please contact us before you disclose it publicly. We will confirm receipt and keep you informed while we fix it.
Privacy policy · Data processing agreement · Read the collection model