This document maps each Oshun data-plane residency region to the privacy / data-protection regulatory regimes that apply to user data stored or processed in that region, and to the education-data regimes that apply to school-tenant data regardless of residency.
It is owned by the Oshun privacy team; the libs/oshun/privacy substrate (§22 in V1/TODOS.md) is the runtime that enforces these regimes. This file is the source of truth for "what does Oshun answer when an auditor asks 'what laws does region X comply with'".
Region → regime matrix#
| Residency region | Primary regimes | Education-data overlays | Cross-border transfer constraints |
|---|---|---|---|
us (US-East / US-West) |
CCPA + CPRA (California), VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), UCPA (Utah), MyHCDPA (Montana), TIPA (Texas), DPDPA (Delaware), OCPA (Oregon), TDPSA (Tennessee), ICDPA (Iowa), NHDPSA (New Hampshire), MDPDA (Maryland), MPDPA (Minnesota), RIDPA (Rhode Island), NJDPL (New Jersey) | FERPA (federal, for K-12 + higher ed); state student-data laws (NY 2-d, CA SOPIPA, Illinois SOPPA, CT 1054, Tennessee SDPA); COPPA when processing data of minors under 13 | Data flows freely within us; export to eu / uk requires SCCs + adequacy review; export to apac requires explicit cross-region transfer approval per §22.4 |
eu (Frankfurt) |
GDPR (EU-wide, Regulation 2016/679); national implementations (BDSG Germany, RGPD France, GDPR Italy etc.); ePrivacy Directive 2002/58/EC; DSA + DMA where applicable | EU member-state education laws (e.g., German Schulgesetze, French Code de l'éducation); KMK rulings on cloud usage in schools | Transfers outside the EU/EEA require either an adequacy decision (UK, Switzerland, Japan, Korea, …) or appropriate safeguards (SCCs, BCRs); the DPF (Data Privacy Framework) covers US transfers to certified organisations. Cross-region moves out of eu need a documented Transfer Impact Assessment (TIA) |
uk (London) |
UK GDPR + Data Protection Act 2018; PECR (Privacy and Electronic Communications); upcoming DUA Act (Data (Use and Access) Act 2025) | Education Act 1996, Children's Code (Age-Appropriate Design Code 2020); Keeping Children Safe in Education 2024 guidance for K-12 vendors | UK-EU adequacy decision currently in force (under review); transfers to other regions require either adequacy or appropriate safeguards (UK IDTA / UK-IDTA Addendum to SCCs) |
ca (Canada) |
PIPEDA (federal); provincial laws (Quebec Law 25, Alberta PIPA, BC PIPA); CPPA (proposed federal successor to PIPEDA) | Provincial education acts (e.g., Ontario MFIPPA / FIPPA, Quebec Education Act); School-board-specific privacy policies | Transfers governed by Quebec Law 25 cross-border assessment for any data leaving Quebec; PIPEDA "comparable level of protection" requirement for transfers globally |
apac (Singapore) |
Singapore PDPA; Japan APPI; Korea PIPA; Australia Privacy Act 1988 (incl. APPs); India DPDPA 2023; Hong Kong PDPO; Thailand PDPA; Indonesia PDP Law; Philippines DPA | Country-specific education ministry guidelines (e.g., MOE Singapore EdTech standards, MEXT Japan); FERPA-equivalents are largely absent — sector contracts govern | Cross-border transfer subject to per-country rules: APPI/PIPA require subject consent or contract clauses; India DPDPA introduces a "blacklist" approach where transfer is allowed unless prohibited; HK has no explicit cross-border restriction |
latam (São Paulo, when active) |
LGPD (Brazil, Lei 13.709/2018); Argentina Law 25.326; Mexico LFPDPPP; Chile Law 19.628 (under reform); Colombia Law 1581; Uruguay Law 18.331 (adequacy with EU) | National education ministry guidelines (varies); MEC Brazil for K-12 SaaS; not all countries have FERPA-equivalent | LGPD permits transfer to "adequate" countries (Brazil's ANPD maintains a list incl. EU + UK); other transfers require SCCs / specific consent |
me (Middle East, future region) |
UAE PDPL (Federal Decree-Law 45/2021); Saudi Arabia PDPL; Israel Privacy Protection Law 5781; Qatar Law 13/2016 | Country-specific MOE guidelines; UAE Federal MOE Cybersecurity Framework | UAE PDPL requires DIFC-style "adequate" destination or explicit consent; Saudi PDPL allows transfer only where the destination provides "adequate level of protection" or with NDPC approval |
Sector overlays (regardless of residency)#
These apply whenever the corresponding data type is present, regardless of residency region:
- Education: FERPA (US), Children's Code (UK), state student-data laws, COPPA (children under 13 globally, with US-specific enforcement). Oshun treats every K-12 tenant as in scope and applies the strictest applicable regime to the entire tenant's user data.
- Health (where present): HIPAA when a US covered entity is the tenant
controller; UK NHS Information Standards; GDPR Article 9 special-category
controls in
eu. Oshun does not act as a HIPAA covered entity by default — health features are gated behind a BAA-required entitlement. - Children under 13 (COPPA): Verifiable parental consent required for data collection. Oshun treats this as a per-user attribute that propagates into consent state and gates every category in §22.1.
- Children under 18 (Children's Code UK): AADC age-appropriate defaults apply. Oshun applies the strictest UK profile when any UK minor is detected in a tenant.
- Financial / payments: PCI DSS (where card data flows). Oshun routes payment data through Aje + the bridge so no PCI scope lands in the core data plane.
Enforcement points in the Oshun data plane#
These are the canonical attachment points where the §22 substrate enforces the regimes documented above. Read this as "auditor asks 'how do you enforce GDPR right of erasure', the answer is the path below":
- Consent transitions:
libs/oshun/privacy/src/consent/consent.tsrecords every grant / withdrawal / regrant with the regime cited as the legal basis. Lookup:getConsentTransitionsForUser(userId). - Right of erasure / DSAR:
libs/oshun/privacy/src/dsar/dsar.tsmodels the deletion / export / rectification request lifecycle, with per-regime SLA clocks (GDPR 30 days, CCPA 45 days, LGPD 15 days, UAE 30 days, …). Cascades to integrations via the §22.4 fanout. - Residency routing:
libs/oshun/privacy/src/residency/residency.tsenforces that user data lives in the residency region recorded at signup unless a documented cross-region transfer approval is in place. - Mandatory disclosures: Surfaced in
apps/oshun/weblegal pages under/legal/*; the registry and active-locale resolver live inlibs/oshun/privacy/src/compliance/compliance.ts. - Breach runbook:
libs/oshun/privacy/src/compliance/compliance.tshouses the state machine that enforces the per-regime notification clock (GDPR 72h, UK DPA 72h, CCPA without unreasonable delay, LGPD without unreasonable delay, etc.). - Audit completeness: Every consent transition, operator access, deletion,
export, and cross-region move is logged immutably via the §21 trust-and-safety
audit log; queryable in the admin audit-log explorer
(
apps/oshun/admin/src/components/AdminAuditLogExplorerPanel.tsx).
Ownership and review cadence#
- Owner: Oshun privacy team (point of contact:
privacy@oshun.app). - Review cadence: This document is reviewed quarterly, and immediately when
a new region is added or a new regulation takes effect. Legal team signs the
review note into
docs/compliance/governance-reviews/. - Last reviewed: 2026-05-11 (initial publication; subject to ongoing review).
Related runbooks#
docs/compliance/eu-ai-act-mapping.md— EU AI Act risk-tier mapping for the agentic-studio and Lilith persona surfaces.docs/compliance/nist-ai-rmf-mapping.md— NIST AI Risk Management Framework mapping for the studio + creator workflows.docs/compliance/uncitral-odr-mapping.md— UN ODR mapping for §21 trust-and-safety appeals.
Changelog#
| Date | Change | Author |
|---|---|---|
| 2026-05-11 | Initial publication: per-region regime matrix, sector overlays, data-plane enforcement points. | privacy team |