Security & Compliance
How Xantly protects your data: encryption in transit and at rest, the tiered content retention model and its Zero-Retention option, the guarantee that prompts are never used to train a language model, access controls, 72 hour breach notification, the sub-processor list, and certification status.
How Xantly protects your data: encryption, retention tiers, access controls, breach notification, sub-processors, and certification status.
This page summarizes Xantly's security posture for developers. For the full, canonical detail, see the marketing site's Security overview and the Data Processing Agreement.
Encryption
| Layer | Protection |
|---|---|
| In transit | All API and dashboard traffic is protected with TLS 1.2 or higher. |
| At rest | Stored data is encrypted using AES-256. |
API keys are additionally bound with DPoP (Demonstrating Proof of Possession) to reduce the impact of a leaked token.
Data retention
Xantly uses a tiered content-retention model. You choose how prompt and response content is handled; metadata, audit, and billing records retain on separate clocks. By default (Tier 1), content is stored for a window you control and then auto-purged, Xantly is not a strict pass-through by default.
| Tier | What happens to prompt / response content |
|---|---|
| Tier 0, Zero-Retention | Content is not persisted at rest. Only metadata and a non-reversible prompt hash are kept, plus anything preserved under the legal / abuse carve-out. No content-derived embedding is persisted. |
| Tier 1, Default retention | Content is retained for a window you configure, default 30 days, presets of 7 / 30 / 90 days, or 0 days for zero-retention, then automatically purged. Stored content is visible only to you, for your own debugging. |
| Tier 2, Metadata + audit | Operational metadata and audit records retain on their own schedule (see below), independent of the content window. |
| Tier 3, Tenant controls | A content-deletion endpoint, a no-content-LLM-training guarantee, and region residency where configured and available. |
Retention windows, on independent clocks:
| Data | Retention |
|---|---|
| Prompt / response content | Your configured window (default 30 days; presets 7 / 30 / 90; 0 = zero-retention); deleted on request |
| API request metadata | 90 days (rolling window) |
| Security and audit logs | 12 months |
| Billing and invoice records | 7 years (legal / tax requirement) |
After retention periods expire, data is permanently deleted or irreversibly anonymized.
Derived routing signals
To route each request, Xantly computes non-reversible derived signals: token counts, an inferred task class, latency, cost, success outcomes, and a numeric semantic embedding. These train a per-customer routing policy (our Bayesian adaptive routing loop, BaRP) and update aggregate model-performance stats. Content text is not stored to produce these signals, and the signals cannot reconstruct it. For Zero-Retention accounts, no content-derived embedding is persisted.
No content used to train language models
Xantly never uses your prompts or responses to train, fine-tune, or improve any large language model, its own or a provider's. The only models Xantly trains are internal routing / selection models, trained solely on the non-content signals above. Any optional cross-customer aggregation for improving routing uses only aggregated, anonymized, non-content outcomes, and excludes Zero-Retention and opted-out customers.
When you route a request to a third-party provider, the content needed to fulfill it is sent to that provider and is then subject to that provider's own data-usage terms.
Access controls
Account and organization access is protected by:
- Authentication methods: passwords, passkeys (WebAuthn), MFA (TOTP), email one-time passcodes, and Google / GitHub social login.
- Organization RBAC: role-based access control scopes what each member can do within an organization.
- MFA for administrative functions: multi-factor authentication is required for sensitive administrative actions.
- API key scoping: assign each key only the permissions it needs, and rotate or revoke keys from the dashboard.
- Audit logging: administrative and security-relevant actions are recorded.
Enterprise single sign-on (SAML / OIDC SSO) is not available today.
Breach notification
If Xantly becomes aware of a personal data breach affecting data processed on your behalf, it will notify affected customers without undue delay and in any case within 72 hours. The notification describes, to the extent known, the nature of the breach, the categories and approximate number of data subjects and records affected, the likely consequences, and the measures taken to address it.
Sub-processors
Xantly uses a defined set of sub-processors to operate the Service. The content of a request is shared with a model platform only when your request is routed to a model running there.
Model platforms. Measured over the 90 days to September 9, 2026, these three carried 96.1% of all inference attempts.
| Sub-processor | Purpose |
|---|---|
| Amazon Web Services | Model inference (Bedrock); compute, managed database, and object storage hosting |
| Google Cloud | Model inference (Vertex AI) |
| Microsoft Azure | Model inference |
Direct model providers. The remaining 3.9% of attempts reached a model vendor's own API, because the model was not available on a platform above or the platform attempt failed. The full list, with locations, is Annex III of the DPA. Several are outside the EEA, including in the People's Republic of China. If that conflicts with your data-residency requirements, enable Compliant Mode or set a routing policy, which confines routing to a verified catalog on the attested platforms above.
Infrastructure and business operations.
| Sub-processor | Purpose |
|---|---|
| Cloudflare | DNS, CDN, front-end hosting, object storage for exports |
| Stripe | Payment processing |
| Resend | Transactional email |
| PostHog | Product analytics, subject to cookie consent |
Everything else in the stack, including the database, cache, vector store, graph store, analytics warehouse, and monitoring, runs on infrastructure Xantly operates itself inside its own AWS account and is not a separate sub-processor.
The authoritative sub-processor list, and the 10 business day change-notification commitment, are in Annex III of the DPA.
Certifications
SOC 2 Type II, in progress. Xantly is actively pursuing SOC 2 Type II certification. It does not yet hold the certification. The audit report will be published once available.
Learn more
- Security overview, current security posture
- Data Processing Agreement, sub-processors, SCCs, breach terms
- Authentication, tokens, key handling, and best practices
- Bring your own key, route through your own provider keys