Security / controls overview
Prompts and completions stream through memory in the regional data plane and are never written to disk or used for training. What we do keep, receipts and configuration, is encrypted, signed and verifiable without trusting us.
Two planes, one rule: content never goes up.
The control plane is where you configure tenants, write policy and manage access. It runs in Frankfurt am Main with a standby in Paris, on EU-headquartered infrastructure, and it never receives a prompt.
Requests are handled by a data plane in the tenant's zone. The control plane pushes signed policy bundles down; data planes send decision metadata and hourly Merkle roots up. On Sovereign Dedicated both planes run in your VPC or on-prem, including air-gapped sites.
Control plane
Frankfurt am Main primary / Paris standby / EU-headquartered infrastructure
Holds no prompts, no completions and no identifier values.
Signed policy bundles and routing config
Decision metadata and Merkle roots, never content
Regional data planes
EUUKCHGCCAPACUSThe prompt path, in green, stays inside one data plane and one legal zone. Each stage works on the request in memory; only the receipt is written.
Security questionnaires ask where each kind of data lives. Pick an element to see, component by component, whether it is held in memory for the life of the request, stored encrypted, reduced to a hash or label, or never present at all.
Edge gateway
Data plane, in zone
Streamed in memory
Read from the TLS stream and forwarded; buffers are released when the response completes.
PII guardrail
Data plane, in zone
Streamed in memory
Scanned in memory for names, IBANs, national IDs and health terms.
Pseudonymization vault
Data plane, origin region
Never present
The vault holds token mappings, not prompts.
Policy engine (OPA)
Data plane, in zone
Never present
Policy sees classification labels and metadata, not the text.
Model endpoint
Certified provider, in zone
Provider ZDR terms
Receives the masked prompt; processing falls under the provider's zero data retention terms.
Notary and receipt ledger
Data plane, in zone
Hash or label only
SHA-256 request hash in the receipt.
Control plane
Frankfurt, Paris standby
Never present
Prompts never reach the control plane.
Your SIEM export
Your environment
Hash or label only
Receipts carry the hash only.
Prompt text
Never written to disk by YTT Secunet. Only its SHA-256 hash outlives the request.
Persisted by
Nothing. Memory only.
Prompts and completions stream through memory in the regional data plane. They are never written to disk, never logged in clear text and never used for training. What persists is metadata: the decision, the receipt and a SHA-256 hash of the request.
All plans
TLS 1.3 from your client to the gateway and from the gateway to the provider. The upstream certificate's SHA-256 thumbprint is written into every receipt, so the connection that served a request is on record.
All plans
Receipts, policy packs and tenant configuration are encrypted with AES-256. Pseudonymization vault entries use a per-tenant key and stay in the origin region.
All plans
Receipts are signed with Ed25519 keys held in hardware-backed key management, and public keys are published so the verifier works offline. On Sovereign Dedicated the signing keys are generated and held in your own HSM; YTT Secunet never sees them.
Customer-held on Dedicated
SAML SSO and SCIM provisioning on Enterprise Sovereign, with role-based access and a read-only audit role for internal audit or a regulator. Production access by YTT Secunet staff is just-in-time, approved and logged.
SSO and SCIM on Enterprise
SOC 2 Type II report covering security, availability and confidentiality. ISO/IEC 27001 and ISO/IEC 27701 certification across the Chennai and Frankfurt sites. Reports are in the Trust Center.
SOC 2 Type II, ISO 27001, ISO 27701
An independent penetration test of the gateway, console and APIs every year and after major changes to the data path. Researchers can report vulnerabilities to security@yttsecunet.com; we acknowledge within 24 hours and do not pursue good-faith research that follows this policy.
Summary in the Trust Center
A 24/7 on-call rotation with documented runbooks for data plane, key and subprocessor incidents. As your processor we notify you without undue delay after becoming aware of a personal data breach, as Article 33(2) GDPR requires, with the details set out in the DPA.
Status at /status
| Control | Growth | Enterprise Sovereign | Sovereign Dedicated |
|---|---|---|---|
| Zero data retention for prompts and completions | |||
| TLS 1.3 in transit, AES-256 at rest | |||
| Signed receipt on every response | |||
| Receipt signing keys | YTT Secunet-managed | YTT Secunet-managed | Customer-held, in your HSM |
| Proof ledger retention | 90 days | 7 years | In your storage, your schedule |
| SAML SSO and SCIM | |||
| Read-only audit role | |||
| Reversible pseudonymization vault | |||
| Control plane location | EU (Frankfurt, Paris standby) | EU (Frankfurt, Paris standby) | EU-only or in-country, in your environment |
| Air-gapped deployment with offline licensing | |||
| Gateway SLA | Standard | 99.95% | 99.99% |
The CLOUD Act lets US authorities require a provider subject to US jurisdiction to produce data in its possession, custody or control, wherever that data is stored. YTT SECUNET PRIVATE LIMITED is incorporated in India, not the US, but a foreign company with enough US contacts can still receive US process, and Indian law has its own access powers. We design around that rather than claiming an exemption.
What we reduce
What we cannot change
Where this matters most, the answer is policy. The endpoint registry records each provider's parent jurisdiction, so a pack can keep special category data on EU-parented providers or on your own vLLM cluster, and allow US-parented regional deployments only for pseudonymized traffic.
Every response carries an X-YTT-Proof-Signature header: an Ed25519-signed JWS over this payload. It names the policy and version that allowed the request, the endpoint, provider region and facility that served it, and the upstream certificate thumbprint.
It does not contain the prompt, the completion or any identifier value. The request is represented by its SHA-256 hash, which you can recompute from your own logs to match a receipt to a call.
{
"v": 1,
"rid": "rcpt_01JBX7Q4M2W8KD3T",
"ts": "2026-11-04T09:14:22.418Z",
"tenant": "tnt_de_4417",
"req_sha256": "9f2c1e7ab04d55c38e1f62d0b7a9c4e1f03b6d82a5e7c9104f2b8d6e3a7c1e81",
"policy": { "id": "eu-gdpr-strict", "version": "4.2.0", "decision": "allow" },
"endpoint": "de-fra-az-02",
"provider_region": "germanywestcentral",
"facility": "FRA-AZ-02",
"upstream_tls_sha256": "5e9a21c07f44b819d2c60e3f8a71b5c94d0e2f6a18c3b7e5d9f04a2c6b8e1d37",
"model": "gpt-4o",
"zdr": true,
"merkle": { "hour": "2026-11-04T09", "leaf": 18842 }
}No. Prompts and completions stream through memory in the regional data plane and are never written to disk or used for training. The receipt keeps a SHA-256 hash of the request so you can prove which request it refers to without the content existing anywhere in our systems.
No, and we do not claim that. YTT SECUNET PRIVATE LIMITED is incorporated in India, which does not place it beyond US legal process if it has enough US contacts, and Indian law has its own access powers. We reduce what any such process could reach: no stored prompts, receipts that hold hashes rather than content, customer-held signing keys and in-VPC deployment on Sovereign Dedicated.
The provider in the selected zone receives the request after masking, so identifiers your policy covers arrive as tokens. Its own retention terms then apply, which is why the endpoint registry only certifies deployments with zero data retention available and records each provider's parent jurisdiction.
Yes. Request them through the Trust Center. The SOC 2 Type II report and penetration test summary are shared under NDA; the DPA, subprocessor list and BAA are published on the legal pages.
Email security@yttsecunet.com with the affected component, steps to reproduce and your contact details. We acknowledge within 24 hours, keep you updated while we fix it, and credit you on request. Please do not access other customers' data or degrade the service while testing.
Sovereign route ready
Send your reviewers the Trust Center, a week of receipts and the verifier. They can check every claim on this page themselves.