Sub-processors & Data Residency

Sub-processors

Cytra engages the following sub-processors to deliver the AI-governance platform and managed MCP gateway. Each is engaged under a contract requiring appropriate confidentiality and security measures. This list is enumerated from the services that actually receive data at runtime. It is cross-referenced from our Data Processing Addendum and our trust page.

AI model providers receive the test prompts you run through Cytra. Test execution uses the API key you supply for the selected provider (bring your own key), so you hold the direct relationship with that provider while Cytra mediates the request.

• Cloudflare, Inc. (United States) — Edge compute (Workers), D1 database, R2 object storage, Analytics Engine telemetry, browser rendering for PDFs, CDN, DNS, and DDoS mitigation. Data category: Account data, platform content, governed-action records, and product telemetry.
• Amazon Web Services, Inc. (United States) — Transactional email (SES); the support audit archive uses S3, Athena, and Firehose. Data category: Contact data in emails and support audit-archive records.
• Google LLC (United States) Model provider — Optional OAuth sign-in and the Gemini AI models used for test execution and bias analysis. Data category: Authentication metadata and customer test content.
• Anthropic, PBC (United States) Model provider — Claude models used for Cytra-mediated test execution. Data category: Customer test content.
• OpenAI, L.L.C. (United States) Model provider — OpenAI (and Azure OpenAI-compatible) models used for Cytra-mediated test execution. Data category: Customer test content.
• Voyage AI, Inc. (United States) Model provider — Text embeddings (voyage-3) for semantic search over the support knowledge base. The support chat/RAG path sends the customer query and indexed document text to Voyage to produce the embedding vectors. Data category: Support knowledge-base content and query text.
• Functional Software, Inc. (Sentry) (United States) — Application error monitoring. Data category: Diagnostic error data (stack traces, request context).
• Wentzel Investments LLC (Nexus) (United States) — Internal Wentzel platform service for structured logging and lifecycle (drip) email. Data category: Operational logs and contact data for lifecycle email.

Not currently engaged

For transparency, the following vendors are present in our dependencies or marketing material but are not live sub-processors today. We will add a vendor to the list above before it begins processing your data.

• Stripe, Inc. — Installed, but the billing portal is a stub — no live payment flow processes customer data today. Stripe will be listed when a live payment flow ships.
• Kong / Kong Konnect — Appears only in marketing topology copy, not in any runtime code path — it is not a live sub-processor.

Change notifications

We will provide notice before a new sub-processor begins processing your personal data, giving you an opportunity to object on reasonable data-protection grounds. To subscribe to sub-processor change notifications, email legal@cytra.io or reach us through the contact page.

Data residency

Cytra production data is processed and stored in the United States on Cloudflare (D1 database and R2 object storage) and Amazon Web Services (SES email and the support audit archive). Cytra does not currently offer EU-only or region-pinned data residency.

For customers in the European Economic Area, the United Kingdom, or Switzerland, transfers of personal data to the United States are governed by the Standard Contractual Clauses, the UK International Data Transfer Addendum, and the Swiss adaptations, together with the technical measures described in our Data Processing Addendum. This is a lawful transfer mechanism — it is not the same as EU data residency, and we do not claim residency we do not have.

If EU data residency is a requirement for your organization, raise it during contracting so we can assess the available options. The full statement is maintained in our internal documentation (docs/compliance/DATA_RESIDENCY.md).