TokenAtlasBuilt on a secure, privacy-first foundation.
We take protecting your data seriously. Here's a transparent look at how TokenAtlas is built — what we encrypt, what we isolate, and what we never collect.
Email + OAuth via a hardened auth provider, with session rotation and revocation.
TLS in transit and encryption at rest for all stored records.
We collect only what's necessary to run the product — never your raw prompts or completions.
Edge-served app, isolated tenant data, and row-level security on every customer table.
Data Protection
Customer data is logically isolated per account. Every database table enforces row-level security so users can only read and write their own records. Backups are encrypted and access is restricted to a small set of operators.
Authentication
Sign-in uses a managed identity provider with secure session tokens, refresh rotation, and email verification. OAuth flows are supported for password-less access. Sensitive routes require an authenticated session on every request.
Encryption
All traffic between your browser and TokenAtlas is encrypted in transit using TLS. Data at rest is encrypted using industry-standard ciphers managed by our infrastructure provider.
Privacy
We do not sell user data. We don't store your raw model prompts or completions for analytics. Usage metadata is kept only as long as needed to provide the service and produce your own reports.
Infrastructure Security
TokenAtlas runs on modern edge infrastructure with isolated runtime sandboxes, automated dependency scanning, and continuous monitoring of our backend services for anomalies.
A note on compliance: TokenAtlas is built with security and privacy best practices, but we do not currently make formal compliance claims (such as SOC 2, ISO 27001, or specific regulatory certifications). If your team needs a security review for procurement, please contact us.