Skip to content

Trust Center / reports, legal terms, status

Evidence on request, not on faith.

Audit reports, certificates, legal terms and live control status in one place. Public documents open directly; reports with control detail are shared under NDA, usually within one business day.

Assurance summary
SOC 2 Type II
Report issued Feb 2026Security, availability, confidentiality
ISO/IEC 27001
Certified Apr 2026Chennai and Frankfurt sites
ISO/IEC 27701
Certified Apr 2026Privacy information management
Pen test
Annual, independentGateway, console, public APIs

Document library

  • SOC 2 Type II reportNDAAssurance / PDF

    Independent auditor's report on security, availability and confidentiality controls over a six-month observation window.

    Request access
  • ISO/IEC 27001 certificateOn requestAssurance / PDF

    Information security management system certificate covering the Chennai and Frankfurt sites, with the statement of applicability.

    Request a copy
  • ISO/IEC 27701 certificateOn requestAssurance / PDF

    Privacy information management system extension, covering YTT Secunet's roles as controller and as processor.

    Request a copy
  • Penetration test summaryNDAAssurance / PDF

    Executive summary of the latest independent test of the gateway, console and public APIs, with remediation status by severity.

    Request access
  • Data Processing AgreementPublicLegal / Web

    Article 28 GDPR terms, the 2021 SCCs (Modules 2 and 3) for support access from outside the EEA, and our technical and organisational measures.

    Read the DPA
  • Subprocessor listPublicLegal / Web

    Every subprocessor by purpose, location and data category, and how we give notice before adding one.

    View the list
  • Business Associate AgreementPublicLegal / Web

    HIPAA BAA for US customers routing protected health information through the US zone.

    Read the BAA
  • Transfer impact assessmentNDALegal / PDF

    Our own TIA for support access to the EU control plane from outside the EEA, with the supplementary measures applied.

    Request access
  • Receipt format and verifierPublicTechnical / Web

    The JWS receipt fields, Merkle tree construction and how ytt-verify checks inclusion proofs offline.

    Read the spec
  • Security architecture overviewPublicTechnical / Web

    Data plane and control plane separation, what is stored and what is streamed, and the controls by plan.

    Open

Control status

12 of 12 operating
  • Encryption in transit

    Operating

    TLS 1.3 on client and upstream connections

    ISO A.8.24SOC 2 CC6.7

  • Encryption at rest

    Operating

    AES-256 for receipts, policy and tenant config

    ISO A.8.24SOC 2 CC6.1

  • Zero data retention

    Operating

    Prompts and completions held in memory only

    ISO A.8.10SOC 2 C1.2

  • Access control

    Operating

    SSO with MFA, just-in-time production access

    ISO A.5.15SOC 2 CC6.1

  • Change management

    Operating

    Signed policy bundles, reviewed releases

    ISO A.8.32SOC 2 CC8.1

  • Logging and monitoring

    Operating

    Content-free audit logs, 24/7 alerting

    ISO A.8.15SOC 2 CC7.2

  • Vulnerability management

    Operating

    Annual third-party pen test, continuous scanning

    ISO A.8.8SOC 2 CC7.1

  • Incident response

    Operating

    On-call rotation, runbooks, customer notification

    ISO A.5.24SOC 2 CC7.4

  • Business continuity

    Operating

    Paris standby control plane, in-zone failover

    ISO A.5.30SOC 2 A1.2

  • Supplier management

    Operating

    Subprocessor reviews before onboarding and yearly

    ISO A.5.19SOC 2 CC9.2

  • Privacy management

    Operating

    ISO/IEC 27701 PIMS, records of processing

    ISO A.5.34ISO/IEC 27701

  • Key management

    Operating

    Hardware-backed signing keys; customer HSM on Dedicated

    ISO A.8.24SOC 2 CC6.1

Subprocessors summary

CategoryPurposeLocationData involved
Control plane hostingRuns the console, policy store and Merkle root publicationGermany (Frankfurt), France (Paris standby)Tenant config, policy packs, receipts metadata
Regional data plane hostingRuns the gateway in each zone you enableInside each enabled zoneRequests in memory only; encrypted receipts
Customer support toolingTicketing and support conversationsEuropean UnionWhat you send in a ticket
Transactional emailAccount, billing and incident noticesEuropean UnionContact names and email addresses
PaymentsCard and invoice billingEuropean Union and United StatesBilling contact and payment details, no request data

Named entities, legal addresses and change notices are on the subprocessor page. None of these subprocessors receives prompt or completion content.

View subprocessors

How document access works

  1. 01

    Ask for the document

    Use the contact form and choose Security, or write to security@yttsecunet.com, naming the documents your review needs.

  2. 02

    Sign the NDA

    A click-through NDA, or your own mutual NDA if your procurement team prefers it. Public documents need neither.

  3. 03

    Receive an expiring link

    Reports are shared through a watermarked, time-limited link, usually within one business day.

  4. 04

    Walk through it with us

    Deepa Nair's security and compliance team can take your reviewers through scope, exceptions and remediation.

  5. 05

    Verify independently

    Pair the reports with a week of receipts and run ytt-verify, so the routing claims are checked without trusting us.

  6. 06

    Keep it current

    We send updated reports and certificates when they are reissued for as long as you are evaluating or a customer.

Security contacts

Support, toll-free: 1800-266-4343 Main: +91-44-4123-4343

Trust Center questions

Why are some documents behind an NDA?

The SOC 2 Type II report, the penetration test summary and our transfer impact assessment describe internal controls in detail, so auditors and our own policy restrict them to customers and prospects under confidentiality. A click-through NDA or your own mutual NDA both work.

Are model providers on the subprocessor list?

Model endpoints are chosen by you in policy and appear in your endpoint inventory with region, facility and parent jurisdiction. Where YTT Secunet contracts capacity on your behalf, that provider is listed on the subprocessor page with its location.

How will we hear about a new subprocessor?

Through the notification process set out in the DPA, before the change takes effect, with an opportunity to object. Notices go by email to the privacy and security contacts named in your account.

Can our auditors test controls directly?

Enterprise Sovereign and Sovereign Dedicated customers can grant auditors a read-only audit role in the console and give them receipts to verify with the open-source ytt-verify tool, without any help from us.

Sovereign route ready

Hand your reviewers the evidence on day one.

Request the reports, send a week of receipts, and let them verify every routing claim offline.