Skip to content

Reference / transfer law for AI inference

Regulatory transfer guides

One guide per regime, written for the DPO and the platform engineer at the same time: what the law requires of a prompt in flight, and the routing rule that enforces it.

Coverage by jurisdiction

  • EU9
  • UK1
  • CH1
  • GCC2
  • APAC4
  • US3

last revised 2026-11-06

20
transfer guides across 6 jurisdictions, each with routing rules, Rego and an audit checklist
EUR 20M or 4%
of worldwide annual turnover, whichever is higher: GDPR Article 83(5) ceiling for unlawful international transfers
Regulation (EU) 2016/679, Art. 83(5)(c)
EUR 15M or 3%
of worldwide annual turnover: EU AI Act ceiling for breaching high-risk and other operator obligations
Regulation (EU) 2024/1689, Art. 99(4)
16 July 2020
CJEU invalidates the EU-US Privacy Shield and requires supplementary measures for SCC transfers
Case C-311/18, Data Protection Commissioner v Facebook Ireland and Maximillian Schrems

Guides by jurisdiction

20 guides shown

EU

European Union

9 guidesJurisdiction overview
UK

United Kingdom

1 guideJurisdiction overview
CH

Switzerland

1 guideJurisdiction overview
GCC

Middle East (GCC)

2 guidesJurisdiction overview
APAC

Asia-Pacific

4 guidesJurisdiction overview
US

United States

3 guidesJurisdiction overview

Anatomy of a guide

  1. 01SummaryWhat the regime asks of an inference path, in three sentences.
  2. 02Key factsCitation, regulator, in-force date and the maximum penalty as written in the law.
  3. 03Statutory textThe articles that bite, summarised section by section with the exact references.
  4. 04Technical requirementsWhat the law means for the data plane, failover, logging and keys.
  5. 05Routing rulesThe rules a YTT Secunet policy pack applies, each with its legal rationale.
  6. 06Rego excerptThe OPA v1 policy fragment that enforces those rules, ready to review.
  7. 07Audit checklistItems an auditor or DPO can verify against receipts and configuration.
  8. 08FAQ and relatedThe questions procurement and counsel ask, and the neighbouring regimes.

From guide to enforced policy

Every guide ends in a policy pack id. Once your DPO has agreed which regime governs a tenant, the application names that pack in the X-YTT-Policy header and the gateway evaluates it on each request, before a byte leaves the region.

The pack version that made the decision is written into the signed receipt on the response, so the rule you read in the guide, the Rego that ran, and the evidence your auditor samples all point at the same artefact.

  • EU tenants: eu-gdpr-strict, plus eu-ai-act-high-risk for Annex III systems
  • UK and Swiss tenants: uk-gdpr-idta, swiss-fadp-compliant
  • GCC and US: saudi-pdpl-sovereign, uae-pdpl-local, us-hipaa-only, us-itar-fedramp
httprequest with a pinned policy pack
POST /v1/chat/completions HTTP/1.1
Host: eu.yttsecunet.com
Authorization: Bearer jr_live_...
X-YTT-Policy: eu-gdpr-strict@4.2.0
X-YTT-Tenant: claims-de

HTTP/1.1 200 OK
X-YTT-Proof-Signature: eyJhbGciOiJFZERTQSIsImtpZCI6Imp...

Sovereign route ready

Stop risking 4% global turnover GDPR fines on AI inference.

Deploy sovereign, cryptographically proven AI routing in 15 minutes.