Encrypted before storage
AES-256-GCM with a fresh random nonce per key, bound to your account and provider so a key can't be decrypted for anyone else. The encryption key is kept apart from the database.
TraxAgent only ever reads usage and billing data, from your AI providers, coding agents and seats. Here is exactly how keys, accounts and data are protected, and how we check it.
TraxAgent needs one thing from you: a read-only view of your bill. Here is everything that happens to the key.
Never: reads prompts or outputs, creates keys, changes provider settings, or sits in front of your traffic. Security team can't share an admin key? Use the self-hosted collector (Integrations). Everything we do to keep it safe →
AES-256-GCM with a fresh random nonce per key, bound to your account and provider so a key can't be decrypted for anyone else. The encryption key is kept apart from the database.
Keys are used only to read usage and cost reports. TraxAgent never sends prompts, creates keys or changes provider settings.
After you connect, only the last 4 characters are shown. Keys are never written to logs or sent to your browser.
Disconnect removes the key at once. You can also revoke it in your provider's console any time.
Sign-in is by single-use email link, redeemed only by a button press so email scanners can't use it up. Replies are the same whether or not an account exists.
Owner, admin, member and viewer permissions are checked on every request, not only hidden in the page. Your data is always scoped to your own account.
Session cookies are HttpOnly, Secure and SameSite. Every change needs a CSRF token tied to your session, compared in constant time.
Sign-in emails, sign-ups, uploads, data ingest and the AI assistant are rate-limited. Bot sign-ups are filtered.
Every database query uses bound parameters; user input never becomes SQL text.
The AI expert has no tools and can't take actions. Your account data is passed as clearly marked data, never as instructions, and anything shaped like a key is masked from its answers and from emails.
Pages escape all user and provider text. A strict Content Security Policy blocks framing, foreign scripts and form posts to other sites.
HTTPS only with HSTS, nosniff, a strict referrer policy, X-Frame-Options and a locked-down permissions policy. Request sizes are capped.
Provider reports hold token counts and dollars, not message content. Claude Code and Codex telemetry is configured without prompt text, and Cursor usage exports and usage events carry only models and token counts.
TraxAgent stores usage totals, key names and the people on your account, and nothing it doesn't need to show you spend.
Security teams that can't share an admin key can run the collector on their side and send only the usage data.
What a security review usually asks, in one place.
| Provider | What for | Notes |
|---|---|---|
| Railway | Application hosting and database | United States |
| Stripe | Payments and subscriptions | Card details go to Stripe, never to us |
| Resend | Sending emails | Alerts, invites, reports |
| Anthropic | TraxAgent AI expert answers and daily model tips | Summary figures only, never prompts; not used for training |
| Sentry | Error reports when something breaks | No provider keys or passwords included |
The AI providers you connect (Anthropic, OpenAI) are the sources TraxAgent reads, under your own agreements with them. Full details in the Privacy Policy.
No. TraxAgent doesn't train models on your data, and Anthropic doesn't train on the API data our AI expert sends.
No. TraxAgent only calls the endpoints that read usage, cost and key lists. It never creates or changes keys, settings or workspaces, and never makes model calls with your admin key.
No. Provider usage reports contain token counts and dollars, not content. The optional usage tags your code can send carry token counts and labels only.
In the United States, on Railway. While your account is active. Disconnecting a provider deletes its key at once; closing the account deletes the rest within 30 days, except billing records the law requires.
Keys are encrypted before they're stored and only decrypted to fetch reports. Where your provider offers read-only admin keys, use one. You can revoke the key in your provider's console at any time, and disconnecting it deletes it from TraxAgent.
TraxAgent reads your usage from these fixed addresses: 162.220.232.251, 152.55.177.181, 152.55.177.193. Add them to the allowlist before you connect the key, or the nightly read is refused. If one is refused, Connections says so and names these addresses.
Send your questionnaire to support@traxagent.io with "Security review" in the subject. We answer within 2 business days and can walk your team through the data flow on a call.
Last code review: October 17, 2026. Covered: SQL injection, AI prompt injection, cross-site scripting, access control between accounts and roles, secrets handling, rate limits and security headers. Every finding was fixed or scheduled.