How Troxy handles your data

Last updated: May 2026

What Troxy cannot see — ever

Troxy integrates as an MCP tool, not as a proxy or intermediary. This means Troxy is architecturally incapable of accessing anything beyond what the AI model explicitly passes when calling the payment evaluation tool.

Troxy has no access to:

• Your conversation history or messages
• Files, photos, or documents on your device or connected to your agent
• Other MCP servers or tools running alongside Troxy
• Credentials, passwords, or tokens in your agent's context
• Browsing activity, screen content, or application data
• Anything your agent does before or after a payment evaluation

This is not a policy — it is enforced by how the MCP protocol works. Troxy's server process receives only the arguments you explicitly pass to evaluate_payment. There is no mechanism by which it can reach anything else.

What we receive from your AI agent

When an AI agent initiates a payment, the only data sent to Troxy is:

• Merchant name — the domain or label of the merchant (e.g. amazon.com)
• Amount — the payment amount as a number
• Currency — currency code, defaults to USD
• Agent name — an optional label you assign to the agent
• Merchant category — optional category provided by the agent

That is all. Five fields. Nothing else leaves your machine.

Data in transit

All communication between the MCP server and the Troxy API is over HTTPS. Database connections require TLS — plaintext connections are rejected at the server level.

Authentication

API keys — generated as random tokens and stored in our database as bcrypt hashes. The raw key is never persisted. Keys can be revoked instantly from the dashboard and take effect immediately.

Dashboard sessions — authenticated via passwordless email sign-in (one-time code, expires in 15 minutes). Sessions are issued as signed JWTs valid for 30 days and stored only in your browser's local storage — not cookies, so they are not vulnerable to cross-site request forgery.

Escalation approval tokens — generated with 256 bits of cryptographic randomness and expire after 1 hour.

Secret management

Database credentials, JWT signing secrets, and all other sensitive configuration are stored in AWS Secrets Manager and fetched at runtime. Nothing sensitive is stored in source code, environment variables, or infrastructure configuration files.

What is stored in the audit log

Every payment evaluation creates one immutable audit record containing: merchant name, amount, currency, decision (ALLOW / BLOCK / ESCALATE / NOTIFY), agent name, and which policy matched. Audit records are scoped to your account — you can see them in the dashboard, and no other user can access them.

We do not store conversation content, credentials, card numbers, or raw API key values.

Data deletion

You can delete your account and all associated data at any time from the dashboard Settings page. Data is permanently deleted within 30 days of the request.

Questions

If you have a security concern or question, contact us at support@troxy.io.