1. compliance
prorm
  • prorm documentation
  • Known test gaps
  • Architecture
  • Core concepts
  • Database types & coverage
  • Getting started
  • Going further
  • compliance
    • Compliance
    • The security toolkit: `prorm audit`
    • Checklists by regulation
    • Declaring personal data
    • Evidence bundles
    • Evidence
    • Frameworks: `@Security`
    • Jurisdictions
    • Platform policies
    • Protecting data
    • The regulation dataset
    • Residency and cross-border transfers
    • Retention & integrity
    • Status
    • Subject rights
  • decorators
    • prorm with decorators
    • Models with decorators
    • Querying a decorated model
    • Relations with decorators
  • diagrams
    • Diagram generators
    • Chen diagram
    • Class diagram
    • Dependency diagram
    • ER diagram
    • Flow diagram
    • From your models to a diagram
    • Gantt diagram
    • Index diagram
    • Migration diagram
    • Model diagram
    • Package diagram
    • Crow’s-foot diagram
    • Schema documentation
    • Sequence diagram
    • State diagram
    • Tree diagram
  • dialects
    • SQL dialects
    • AlloyDB Dialect
    • AlloyDB Omni Dialect
    • Amazon Athena Dialect
    • Aurora DSQL Dialect
    • Amazon Aurora MySQL Dialect
    • Amazon Aurora PostgreSQL Dialect
    • Azure Database for MySQL Dialect
    • Azure Database for PostgreSQL Dialect
    • Azure SQL Database Dialect
    • Azure SQL Managed Instance Dialect
    • Google BigQuery Dialect
    • Citus Dialect
    • ClickHouse dialect
    • Cloud Authentication (`cloud-auth`)
    • Cloud SQL for SQL Server Dialect
    • Cloud SQL for MySQL Dialect
    • Cloud SQL for PostgreSQL Dialect
    • CockroachDB Dialect
    • Azure Cosmos DB for PostgreSQL Dialect
    • CrateDB Dialect
    • Cloudflare D1 Dialect
    • Databricks dialect
    • IBM Db2 Dialect
    • Dolt Dialect
    • Apache Doris Dialect
    • Druid Dialect
    • DuckDB Dialect
    • Exasol dialect
    • Microsoft Fabric Data Warehouse Dialect
    • Firebird Dialect
    • Greenplum Dialect
    • SAP HANA Dialect
    • MySQL HeatWave Dialect
    • Azure Data Explorer (Kusto) Dialect — T-SQL
    • MariaDB Dialect
    • Materialize Dialect
    • MonetDB Dialect
    • MotherDuck Dialect
    • Microsoft SQL Server Dialect
    • MySQL Dialect
    • Neon Dialect
    • OceanBase Dialect
    • openGauss Dialect
    • Oracle Dialect
    • Oracle Autonomous Database Dialect
    • ParadeDB Dialect
    • PolarDB Dialect
    • PostgreSQL Dialect
    • Presto Dialect
    • QuestDB Dialect
    • Aurora RDS Data API Dialect (`rdsdata`)
    • Amazon RDS for Db2 Dialect
    • Amazon RDS for MariaDB Dialect
    • Amazon RDS for SQL Server Dialect
    • Amazon RDS for MySQL Dialect
    • Amazon RDS for Oracle Dialect
    • Amazon RDS for PostgreSQL Dialect
    • Amazon Redshift
    • Amazon Redshift Data API Dialect
    • RisingWave Dialect
    • rqlite Dialect
    • SingleStore Dialect
    • Snowflake Dialect
    • Google Cloud Spanner Dialect
    • Spanner (PostgreSQL interface) Dialect
    • SQLite Dialect
    • StarRocks Dialect
    • Supabase Dialect
    • Azure Synapse Analytics (dedicated SQL pool)
    • Teradata Dialect
    • TiDB Dialect
    • TimescaleDB Dialect
    • Trino Dialect
    • Turso / libSQL Dialect
    • Vertica dialect
    • Vitess Dialect
    • Yellowbrick Dialect
    • YugabyteDB Dialect
  • guides
    • Access rules and behaviour profiles
    • ArangoDB (AQL)
    • Associations
    • Audit levels and escalation
    • Audit logging
    • In the browser
    • Bulk operations
    • Caching
    • Capabilities, tiers and team roles
    • CLI
    • Cloudflare
    • Compliance & data protection
    • Connection Pooling & Performance
    • Security in the console
    • Couchbase: structured N1QL queries
    • Data types
    • Decorators
    • Eager loading
    • Enums and constants
    • Error handling & error types
    • Extensions
    • External fields
    • Foreign data wrappers
    • Graph databases
    • Hooks & lifecycle events
    • Indexes & constraints
    • InfluxDB: structured Flux pipelines
    • klock-errors
    • klock — the `.klock` file
    • Local databases (`prorm db up`)
    • Structured log search — Splunk, Graylog, Papertrail, Sumo Logic
    • Logging
    • Grafana Loki: structured LogQL queries
    • MCP server
    • Migrate — the data transfer subsystem
    • Migrations & Schema Sync
    • Models from an existing database
    • Defining models
    • Multiple databases
    • OrientDB, Neptune and TigerGraph
    • Passwords
    • Importing a Prisma schema
    • Structured PromQL and MetricsQL
    • Query firewall
    • QueryInterface
    • Query operators reference
    • Query optimization
    • Composing find options with `pipe()` and `Q`
    • Query safety: the fail-closed WHERE guard
    • Querying
    • Raw Queries & Query Building
    • Read replicas
    • Schema diffing & migration generation
    • Views, triggers & other schema objects
    • Scopes & default scopes
    • Seeders
    • SPARQL / RDF triplestores
    • SQL constants
    • SQL features
    • SQL function builders
    • SQLite advanced features
    • StoreKey — a prod-orm database as the storage
    • Streaming results
    • Terraform
    • Transactions & Isolation Levels
    • Type mapping: legacy and modern
    • TypeScript types
    • Database users, roles & privileges
    • Validation & constraints
    • Virtual & Computed Fields
    • Writing docs
  • javascript
    • prorm in JavaScript
    • Models in JavaScript
    • Querying in JavaScript
    • Relations in JavaScript
  • runbooks
    • Operational runbooks
    • Connection failures
    • Credential rotation
    • Failover
    • Incident checklist
    • Deploying klock v2
    • Migration rollback
  • running-databases
    • Running databases in Docker
    • Running prorm under Bun in Docker
    • Running Cassandra in Docker with prorm
    • Running ClickHouse in Docker with prorm
    • Running CockroachDB in Docker with prorm
    • Running prorm under Deno in Docker
    • Running Elasticsearch in Docker with prorm
    • Running MariaDB in Docker with prorm
    • Running MongoDB in Docker with prorm
  • prorm control plane
    • Introduction
    • Authentication
    • Errors
    • Getting started
      • Service
        • Is it up
        • This description
    • Account
      • Sign-up and verification
        • Create an account
        • Exchange credentials for a token
        • Verify with the emailed code
        • Verify by clicking the emailed link
        • Name the parent or guardian
        • What a consent link is about
        • Give consent for a child's account
        • Ask the parent or guardian again
        • Send a new code and link
      • Family
        • Everyone this account is responsible for
        • One child, in detail
        • Turn a limit on or off
      • Profile
        • Who am I
        • Change the account
        • Every address on the account
        • Add an address
        • Confirm an address with the code mailed to it
        • Mail a fresh code to an unconfirmed address
        • Make an address primary
        • Remove an address
        • What this caller may do
    • Security
      • Sessions
        • Everywhere this account is signed in
        • Sign out everywhere else
        • Sign one out
        • A token for the CLI on a named machine
        • A token for the customer console, from the staff one
        • Park a sign-in for the CLI to collect
        • The CLI collecting its sign-in
        • The team's members' live sessions
        • Sign a member's session out
        • Sign an account out everywhere
        • Everywhere the account is signed in
        • Sign an account's session out
      • Single sign-on
        • Begin a single sign-on
        • The provider's return
        • Link the signed-in account to a team's provider
        • Which team an address signs in to
        • The team's single sign-on, as a member sees it
        • Set the team's OpenID Connect provider up, or change it
        • Remove the provider
        • The team's domain claims and the DNS record each needs
        • Prove a claimed domain
      • MFA and passwords
        • Start enrolling a second factor
        • Prove the app has it
        • Remove the second factor
        • Ask for a reset link
        • Set a new password with the emailed token
      • Klock
        • Open a device-bound klock session
        • Check in, for the next grant
        • Step up the session asking
        • Rotate the device key
        • Freeze a session
        • Unfreeze a session
        • A guest grant
        • The revocation feed
        • The published keyset
        • What this control plane supports
      • Devices
        • Your devices, or a team's
        • Approve a new device's pairing code
        • One device
        • Rename a device
        • Revoke a device
        • Suspend a device
        • Reinstate a suspended device
        • Wipe a device
        • Ask a device to rotate its key
        • The team's members' devices
        • Revoke a member's device
        • An account's devices
        • Revoke an account's device
        • Wipe an account's device
        • The device fleet
      • Access rules and behaviour
        • The access rules that bear on you
        • Add an access rule
        • This request, as the rules see it
        • One access rule
        • Remove an access rule
        • The behaviour profiles that bear on you
        • Add or change a behaviour profile
        • The profile presets
        • Your behaviour findings
        • Acknowledge a finding
        • One behaviour profile
        • Remove a behaviour profile
        • The team's access rules
        • Add a team access rule
        • Remove a team access rule
        • The team's behaviour profiles
        • Add or change a team behaviour profile
        • Remove a team behaviour profile
        • What the team's profiles caught
        • Acknowledge a team finding
      • Recovery and lockdown
        • Ask for a recovery link
        • Recover access with the emailed code
        • Is the account locked down
        • Lock the account down
        • Release a lockdown
        • Lock a member down
        • Release a member's lockdown
      • MCP tokens
        • Make a delegated token for one MCP client
        • The account's delegated tokens
        • Revoke a delegated token
        • What a delegated token may do now
        • Run one MCP tool with a delegated token
        • Run a device-signed MCP tool call relayed by the MCP Worker
      • Kerberos
        • Give the team its own Kerberos realm
        • The team's realm
        • Remove the team's realm
    • Logging and monitoring
      • Audit log
        • What has been done to the account
        • What has happened to this account
        • The account's audit trail
      • Operations
        • Everything that has been asked of this database
        • One, with its steps
        • Stop it
        • Put a failed one back in the queue
        • Every operation, across all accounts
      • Metrics and events
        • Every measurement, for a graph
        • Who did what to it
    • Billing
      • Plans and pricing
        • What the plans allow
        • The rate card
        • What one database would cost
        • What this account is paying for, itemised
      • Subscriptions and invoices
        • What this month's invoice will say
        • What this account is on
        • What it has been charged
        • Start a Stripe Checkout session
        • Open the customer portal
        • Stripe's events
        • Buy more connection pools
      • Team billing
        • The team's billing account
        • What the team has been charged
        • What this month's invoice will say
        • The team's cards
        • Add a card, through a Stripe-hosted setup session
        • Make a card the team's default
        • Remove a card
        • Start the team paying
        • Open the Stripe portal on the team's customer
        • Change the team's plan
        • Who receives the team's bills
        • How the team pays for transfers
    • Support
      • Support chat
        • My conversations
        • Start a conversation
        • Every support conversation, open first
        • A ticket for the socket
        • One conversation, with who is in it and who is connected
        • Rename a group; open or close a support conversation
        • The lines, oldest first
        • Say something
        • Add somebody
        • Mark read
    • Administration
      • Users
        • Every account
        • One account, with everything hanging off it
        • Grant or revoke admin
        • Verify an account by hand
        • Lock or unlock sign-in
        • Allow or hold provisioning
        • Send the verification mail again
        • Set the plan by hand
      • Platform
        • Every database and store, across all accounts
        • The counts worth putting on a dashboard
      • Staff and permissions
        • What kind of admin the caller is, and which scopes they hold
        • The admin presets
        • Every admin, and the scopes each resolves to
        • Make an account an admin of a kind
        • Change an admin's kind, or a custom admin's scopes
        • Revoke admin
      • Team administration
        • Every team, with its owner and size
        • One team in full — members with their accounts, and projects
        • Hand the team to another member
        • Put an account in the team, active at once
        • Change a member's role
        • Remove a member
      • Assumed identities
        • Assume an identity — act as a customer account
        • The identities the caller holds open
        • End an assumed identity
      • Support inbox
        • The platform's addresses
        • Add a platform address
        • One address, with its counts
        • Change an address's label, routing, or whether it accepts mail
        • Remove an address that holds no mail
        • Make, adopt or repair the address's routing rule
        • Every admin's personal address, made where missing
        • File a raw message, as if it had arrived
        • The inbox
        • One message, whole
        • Mark a message
        • Hand a message to an admin, or take it back
        • Leave an internal note
        • Reply, from the address the message came to
        • What is waiting
    • Databases
      • Databases
        • Data stores
          • Every data store on the account
          • Provision a data store
          • Change a data store that is already running
          • One data store
          • Deprovision it
          • Report what it is using
          • How to reach a data store
        • Connections and credentials
          • The api keys on a database
          • Issue a key
          • Revoke a key
          • The engine users we created
          • Create a user inside the database
          • Give a user a new password
          • Drop a user
          • How the database is reached
          • Set how it is reached
          • Revoke every api key on it
          • How to connect to it
          • The ssh keys that open its bastion
          • Add a key, or have one made
          • The private half of a generated key, once
          • Revoke an ssh key
        • Schema and objects
          • The SQL objects we put in it
          • Create one, and apply it
          • What is in the database, as the engine reports it
          • One table
          • What it would run, without running it
          • Redefine an object in place
          • Drop it
          • The extensions installed in it
        • Migrations
          • A plan compiled to statements, recording nothing
          • The migrations recorded for it
          • Record one
          • Apply everything recorded and not yet run
          • Apply everything pending, oldest version first
        • Lifecycle
          • Grow or shrink it
          • Stop it accepting connections
          • Start it again
          • Move it to another region
        • Backups and replicas
          • Take a backup
          • The backups it has
          • Restore one into it
          • What has been restored into it, and from where
          • Its read copies
          • Add one
        • Policies
          • The catalog
          • One policy
          • What this database is held to
          • Switch a policy on, or change its knobs
          • Switch it off
          • Mark the policies reviewed
          • Evaluate the periodic policies now
          • Who is behind a credential
        • Passwordless
          • The database's passwordless sessions
          • Issue a passwordless session (v1)
          • Revoke a passwordless session
          • Bind a session to a device key
          • Issue a v2 session for a host to bind
          • Redeem an enrolment ticket on the host
          • Check a passwordless credential
          • Run one described query under a passwordless credential
        • Database roles
          • The database's roles
          • Define a role
          • One role
          • Change what a role permits
          • Delete a role, and revoke every key granted it
          • Grant a role, which mints a key
          • Who holds a role
          • The api keys bound to a role
        • Pools
          • A database's connection pools, and how busy each is
          • Open another pool
          • Rename a pool or change its size
          • Close a pool
        • Data plane
          • Run a query against a database
          • Several statements, in order, over one connection
          • Is this database answering
          • What the proxy itself is holding
        • Transfers
          • The strategies this account's tier may use
          • Price a transfer without creating it
          • The account's transfer jobs, newest first
          • Create a transfer job
          • One job, and whether its certificate holds
          • Cancel an unfinished job
          • Start a created job, confirming its price
          • Report a job's status (the runner, or the owner's side of a local run)
        • Every database on the account
        • Provision a database
        • Change a database that is already running
        • One database
        • Deprovision it
        • Read or write it
        • Report what it is using
        • The engines this API will provision
        • Where a managed database can be put
    • Teams
      • Teams
        • Members
          • Who is on it
          • Invite somebody
          • Accept an invitation
          • Change somebody's role
          • Remove somebody
        • Projects
          • The projects a team runs
          • Start one
          • Rename a project, or move its environment
          • Delete a project
          • One project, and what is in it
          • Put a database or store in it
          • What is in a project
          • Take one out
        • The teams this account is on
        • Start one
        • The twelve roles, and what each may do
        • Rename a team
        • Close a team
        • One team
        • Hand the team to somebody else
        • Leave a team
    • Schemas
      • Error
      • ValidationErrors
      • Token
      • PolicyCategory
      • PolicySeverity
      • PolicyAction
      • PolicyTrigger
      • PolicyParam
      • Policy
      • PolicyCatalog
      • PolicyAssignment
      • PolicyOutcome
      • PolicyFiring
      • CredentialTrace
      • Relation
      • Restrictions
      • ChildSummary
      • SignupRequest
      • SigninRequest
      • UpdateMeRequest
      • User
      • Address
      • GeoPoint
      • D1Region
      • Usage
      • UsageReport
      • Resource
      • Database
      • DataStore
      • NewDatabase
      • NewDataStore
      • QueryRequest
      • DatabasePrivilege
      • ApiKey
      • DbUser
      • Access
      • AccessRequest
      • DatabaseObject
      • NewDatabaseObject
      • NewMigration
      • SchemaOperation
      • Migration
      • Operation
      • Session
      • AdminPowers
      • Admin
      • AuditEntry
      • TeamRole
      • Conversation
      • ChatMessage
      • TeamSso
      • Team
      • TeamMember
      • SshKey
      • ConnectionInfo
      • InboxAddress
      • InboxMailbox
      • InboxMessageSummary
      • InboxMessage
      • InboxNote
      • Page
      • Quote
      • Plan
      • ApiError
      • CapabilityRefusal
      • KlockErrorCode
      • PageWindow
      • SessionView
      • KlockStepUpRequest
      • KlockOpenRequest
      • KlockOpenedSession
      • UpdateMeResult
      • CapabilitiesView
      • SessionLimits
      • Device
      • DeviceListed
      • DeviceTeamRef
      • DeviceCommand
      • DeviceAuditLine
      • DeviceActionRequest
      • StaffActionRequest
      • ManagedSession
      • SessionRevoked
      • AccessRule
      • AccessRuleRequest
      • BehaviourProfile
      • BehaviourProfileRequest
      • BehaviourProfileSaved
      • BehaviourFinding
      • BehaviourFindingAck
      • StepUpProof
      • Removed
      • MemberLockdownRequest
      • McpClient
      • McpDelegatedView
      • McpToolCall
      • McpForwardRequest
      • PasswordlessScope
      • RoleScope
      • PasswordlessSession
      • PasswordlessTlsMaterial
      • PasswordlessKerberosMaterial
      • ServiceDeviceKeys
      • ServiceSession
      • DatabaseRole
      • TransferEndpoint
      • TransferJobRequest
      • TransferQuote
      • TransferStrategy
      • TransferJob
      • TransferJobAccess
      • Pool
      • PoolAllowance
      • BillingSubscription
      • Invoice
      • BillingContact
      • PaymentMethod
      • UpcomingCharges
      • TeamBilling
      • TeamKerberosRealm
      • TeamSsoDomain
      • TeamSsoResponse
      • StoreConnection
      • BatchFailure
      • ProxyStatus
  1. compliance

Jurisdictions

A jurisdiction, here, is a record of what one data-protection regime says
about the questions a schema can answer: from what age a person may consent
for themselves, whether every personal field needs a declared lawful basis,
which categories are special, which are forbidden, how long a subject
request may take, how fast a breach must be reported, and whether the data has
to stay in the country. The registry holds 71 of them; a model names the ones
it is held to and the ORM works out the rest.
import { JURISDICTIONS, jurisdiction, resolve, knownJurisdictions, AS_OF } from 'ts-prorm-orm';

knownJurisdictions();          // ['EU', 'EU-AT', …, 'US-CA', …, 'TW']
jurisdiction('EU-FR');         // France: GDPR, consent age 15, …
resolve(['EU', 'UK', 'IN']);   // the strictest combination of the three
AS_OF;                         // the month the table was last checked against its sources
[!IMPORTANT]
The registry is a reference table, not legal advice. It records what each
regime's instruments say about the questions a schema can answer, as of
AS_OF; your counsel decides which regimes you are held to.
An unknown code throws rather than resolving to nothing, because a model
held to a regime the table does not have is not being held to anything:
Unknown jurisdiction "EU-XX". Known: AE, AR, AU, BR, CA, CH, CN, EU, HK, …
Member states and provinces are written as EU-FR, CA-QC.

What an entry holds#

interface JurisdictionRule {
  code: string;                    // 'EU', 'US-CA', 'CA-QC'
  name: string;
  law: string[];                   // the instruments it is drawn from

  digitalConsentAge: number;       // below this a parent consents
  minimumAge?: number;             // below this the processing is not permitted at all (rare)

  requiresBasis: 'always' | 'special-only' | 'never';
  lawfulBases: LawfulBasis[];      // the bases this regime recognises
  specialCategories: PersonalCategory[];   // need a basis AND a purpose regardless
  prohibited: PersonalCategory[];  // may not be held without a statutory exemption

  retention: Partial<Record<PersonalCategory | 'default', Duration>>;   // ceilings, where the law states one
  rights: SubjectRight[];
  requestDeadlineDays?: number;
  breachNotificationHours?: number;

  residency: {
    localize: 'none' | 'copy' | 'primary';
    regions: string[];             // 'eu', 'us', … — the vocabulary @Database({ region }) uses
    transferRequires: 'nothing' | 'adequacy' | 'safeguards' | 'consent' | 'approval';
  };

  variants?: Record<string, Partial<Pick<JurisdictionRule, 'name' | 'law' | 'digitalConsentAge' | 'breachNotificationHours'>>>;   // member states, provinces: 'FR', 'QC'
}
Duration is an ISO 8601 period string — 'P5Y', 'P18M', 'P30D' — and
durationMs() turns one into milliseconds. Most regimes state no numeric
ceiling ("no longer than necessary"), so retention is usually empty; you
give the number in @Personal(…, { retention }) and the regime's ceiling,
where there is one, wins if it is shorter.

The vocabularies#

Categories of personal data, used by @Personal:
CategoryCoversSpecial under
identifiername, username, account or customer id—
contactemail, phone, postal address—
government-idSSN, passport, national insurance, tax idUS states, AU, JP, KR, CN, SG, PH, HK
financialcard or account numbers, income, creditUS, CA, CN, SG, IL, AE, SA, ID, VN
healthmedical, mental health, disabilityeverywhere that has a special list
biometricfingerprints, face geometry, voiceprintsmost
geneticmost
protectedrace, ethnicity, religion, politics, union, sex life or orientationmost
locationprecise geolocationUS states, CN, SA, VN
behaviouralbrowsing, usage, inferred interests—
demographicage, gender, nationality—
employment—
educationPH
communicationsmessage content—
credentialpasswords, tokens, keys — must be declared protected (hashed or encrypted)—
childany data about a known minorUS, CA, IN, CN, SG, ZA, ID
Lawful bases — GDPR Art. 6 names six; most regimes recognise a subset:
consent, contract, legal-obligation, vital-interests, public-task,
legitimate-interests. India does not recognise contract or legitimate
interests; Canada, Argentina and the US recognise no public-task basis.
Subject rights: access, rectification, erasure, restriction,
portability, objection, automated-decisions, and the US-state family
opt-out-sale, opt-out-profiling, limit-sensitive, non-discrimination.

The registry#

Every top-level regime, as of 2026-09. Member states and provinces follow.
CodeRegimeLawConsent ageBasis neededRequest deadlineBreach clockResidencyTransfer needs
EUEuropean UnionRegulation (EU) 2016/679 (GDPR)16always30 days72 h—adequacy
UKUnited KingdomUK GDPR; Data Protection Act 201813always30 days72 h—adequacy
USUnited States (federal)COPPA (15 U.S.C. §§ 6501–6506); HIPAA (where health data); GLBA (where financial data)13never———nothing
US-CACaliforniaCCPA as amended by CPRA (Cal. Civ. Code § 1798.100 et seq.); COPPA (15 U.S.C. §§ 6501–6506)16special-only45 days720 h—nothing
US-VAVirginiaVCDPA (Va. Code § 59.1-575 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-COColoradoCPA (C.R.S. § 6-1-1301 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-CTConnecticutCTDPA (Conn. Gen. Stat. § 42-515 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-UTUtahUCPA (Utah Code § 13-61-101 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-TXTexasTDPSA (Tex. Bus. & Com. Code ch. 541); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-OROregonOCPA (ORS 646A.570 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-MTMontanaMCDPA (Mont. Code § 30-14-2801 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-IAIowaICDPA (Iowa Code ch. 715D); COPPA (15 U.S.C. §§ 6501–6506)13special-only90 days720 h—nothing
US-INIndianaICDPA (Ind. Code § 24-15); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-TNTennesseeTIPA (Tenn. Code § 47-18-3201 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-DEDelawareDPDPA (6 Del. C. ch. 12D); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-NJNew JerseyNJDPA (N.J.S.A. 56:8-166.4 et seq.); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
US-NHNew HampshireNHPA (RSA 507-H); COPPA (15 U.S.C. §§ 6501–6506)13special-only45 days720 h—nothing
CACanadaPIPEDA13always30 days——nothing
CA-QCQuebec (Canada)Law 25 (Act respecting the protection of personal information in the private sector)14always30 days——nothing
BRBrazilLGPD (Lei nº 13.709/2018)12always15 days72 h—adequacy
AUAustraliaPrivacy Act 1988 (Cth); Notifiable Data Breaches scheme15special-only30 days720 h—safeguards
NZNew ZealandPrivacy Act 202016special-only20 days72 h—safeguards
JPJapanAct on the Protection of Personal Information (APPI)15special-only———adequacy
KRSouth KoreaPersonal Information Protection Act (PIPA)14always10 days72 h—consent
INIndiaDigital Personal Data Protection Act 202318always—72 h—nothing
CNChinaPersonal Information Protection Law (PIPL); Data Security Law; Cybersecurity Law14always——primaryapproval
SGSingaporePersonal Data Protection Act 201213always30 days72 h—safeguards
ZASouth AfricaProtection of Personal Information Act (POPIA)18always———adequacy
CHSwitzerlandFederal Act on Data Protection (revised, 2023)16special-only30 days——adequacy
ILIsraelProtection of Privacy Law, 5741-1981 (Amendment 13)14always———adequacy
AEUnited Arab EmiratesFederal Decree-Law No. 45 of 2021 (PDPL)18always———adequacy
SASaudi ArabiaPersonal Data Protection Law (Royal Decree M/19)18always—72 h—adequacy
RURussiaFederal Law No. 152-FZ on Personal Data14always—24 hprimaryapproval
TRTurkeyLaw No. 6698 on the Protection of Personal Data (KVKK)18always30 days72 h—adequacy
MXMexicoLey Federal de Protección de Datos Personales en Posesión de los Particulares18always20 days——consent
ARArgentinaLey 25.326 de Protección de los Datos Personales13always10 days——adequacy
NGNigeriaNigeria Data Protection Act 202318always—72 h—adequacy
KEKenyaData Protection Act 201918always—72 hcopysafeguards
THThailandPersonal Data Protection Act B.E. 2562 (2019)10always30 days72 h—adequacy
IDIndonesiaLaw No. 27 of 2022 on Personal Data Protection18always—72 h—adequacy
PHPhilippinesData Privacy Act of 2012 (RA 10173)18always—72 h—safeguards
VNVietnamDecree 13/2023/ND-CP on Personal Data Protection16always—72 hcopyapproval
HKHong KongPersonal Data (Privacy) Ordinance (Cap. 486)18special-only40 days——nothing
TWTaiwanPersonal Data Protection Act18always———nothing

Member states and provinces#

Sub-national codes are written PARENT-CODE and inherit everything from the
parent except what they override — for the EU, the age of digital consent,
which GDPR Art. 8 lets each member state set between 13 and 16:
Consent ageMember states
13Belgium (EU-BE), Denmark (EU-DK), Estonia (EU-EE), Finland (EU-FI), Latvia (EU-LV), Malta (EU-MT), Portugal (EU-PT), Sweden (EU-SE)
14Austria (EU-AT), Bulgaria (EU-BG), Cyprus (EU-CY), Italy (EU-IT), Lithuania (EU-LT), Spain (EU-ES)
15Czechia (EU-CZ), France (EU-FR), Greece (EU-GR), Slovenia (EU-SI)
16Croatia (EU-HR), Germany (EU-DE), Hungary (EU-HU), Ireland (EU-IE), Luxembourg (EU-LU), Netherlands (EU-NL), Poland (EU-PL), Romania (EU-RO), Slovakia (EU-SK)
Quebec (CA-QC) overrides Canada with Law 25 and a consent age of 14. The
fifteen US states with comprehensive privacy acts are entries in their own
right, layered over federal COPPA; California (US-CA) is the strict one,
with a consent age of 16 (13 elsewhere) and the widest set of special
categories and rights.

Special categories and rights, by regime#

CodeSpecial categoriesRights
EUhealth, biometric, genetic, protectedaccess, rectification, erasure, restriction, portability, objection, automated-decisions
UKhealth, biometric, genetic, protectedaccess, rectification, erasure, restriction, portability, objection, automated-decisions
UShealth, financial, childaccess, erasure
US-CAhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination, limit-sensitive
US-VAhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-COhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-CThealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-UThealth, biometric, genetic, protected, location, government-id, childaccess, erasure, portability, opt-out-sale, non-discrimination
US-TXhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-ORhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-MThealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-IAhealth, biometric, genetic, protected, location, government-id, childaccess, erasure, portability, opt-out-sale, non-discrimination
US-INhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-TNhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-DEhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-NJhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
US-NHhealth, biometric, genetic, protected, location, government-id, childaccess, rectification, erasure, portability, opt-out-sale, opt-out-profiling, non-discrimination
CAhealth, financial, biometric, genetic, protected, childaccess, rectification, erasure
CA-QChealth, financial, biometric, genetic, protected, childaccess, rectification, erasure
BRhealth, biometric, genetic, protectedaccess, rectification, erasure, portability, objection, automated-decisions
AUhealth, biometric, genetic, protected, government-idaccess, rectification
NZhealth, biometric, genetic, protectedaccess, rectification
JPhealth, protected, government-idaccess, rectification, erasure, restriction
KRhealth, biometric, genetic, protected, government-idaccess, rectification, erasure, restriction, portability
INchildaccess, rectification, erasure
CNhealth, biometric, genetic, protected, financial, location, child, government-idaccess, rectification, erasure, portability, restriction
SGhealth, financial, government-id, childaccess, rectification, portability
ZAhealth, biometric, protected, childaccess, rectification, erasure, objection
CHhealth, biometric, genetic, protectedaccess, rectification, erasure, portability, objection
ILhealth, biometric, genetic, protected, financialaccess, rectification, erasure
AEhealth, biometric, genetic, protected, financialaccess, rectification, erasure, restriction, portability, objection
SAhealth, biometric, genetic, protected, financial, locationaccess, rectification, erasure, portability
RUhealth, biometric, protectedaccess, rectification, erasure
TRhealth, biometric, genetic, protectedaccess, rectification, erasure, objection
MXhealth, biometric, genetic, protectedaccess, rectification, erasure, objection
ARhealth, biometric, genetic, protectedaccess, rectification, erasure
NGhealth, biometric, genetic, protectedaccess, rectification, erasure, portability, objection
KEhealth, biometric, genetic, protectedaccess, rectification, erasure, portability, objection
THhealth, biometric, genetic, protectedaccess, rectification, erasure, restriction, portability, objection
IDhealth, biometric, genetic, protected, financial, childaccess, rectification, erasure, portability, objection
PHhealth, biometric, genetic, protected, government-id, educationaccess, rectification, erasure, portability, objection
VNhealth, biometric, genetic, protected, financial, locationaccess, rectification, erasure, restriction, objection
HKhealth, biometric, government-idaccess, rectification
TWhealth, genetic, protectedaccess, rectification, erasure, restriction

Resolution: strictest wins#

A model names several regimes because its rows describe people in several
places. There is no schema-level meaning for "the EU rule for Europeans and
the Indian rule for Indians" — a column exists or it does not, a ceiling is
one number — so resolve() produces the one combination that satisfies
everyone:
DimensionRule
Consent agethe highest
Minimum agethe highest that is set
Basis requiredalways > special-only > never
Lawful basesthe intersection — a basis every named regime recognises
Special categoriesthe union
Prohibited categoriesthe union
Retention ceilingsper category, the shortest
Rightsthe union — every right any regime grants is owed
Request deadline, breach clockthe shortest
Residencylocalizes if any regime does; then only that regime's regions count; the strictest transfer requirement
So @Jurisdiction('EU', 'UK', 'IN') gates at 18 (India), cannot rely on
legitimate interests (India does not recognise it), and owes portability (EU
and UK grant it). @Jurisdiction('EU-FR', 'EU-DE') gates at 16, not 15.

Planning a launch#

Before a new market goes live, ask the resolver what the models will be held
to, and compare it with what they are held to now:
import { resolve, durationMs } from 'ts-prorm-orm';

const today = resolve(['EU', 'UK']);
const withIndia = resolve(['EU', 'UK', 'IN']);

withIndia.digitalConsentAge;              // 18: the age gate moves up from 16
withIndia.lawfulBases;                    // ['consent', 'legal-obligation', 'vital-interests', 'public-task']
withIndia.specialCategories;              // ['health', 'biometric', 'genetic', 'protected', 'child']
withIndia.requestDeadlineDays;            // 30: India states none, so the others' stands
withIndia.residency;                      // { localize: 'none', regions: ['eu', 'eea', 'uk', 'gb', 'in'], transferRequires: 'adequacy' }

// Bases that stop working: every field declared on one of these fails to load.
const lost = today.lawfulBases.filter((b) => !withIndia.lawfulBases.includes(b));
// ['contract', 'legitimate-interests']

durationMs('P18M') / 86_400_000;          // 540: months are 30 days, years 365
Every field on contract or legitimate-interests is a
basis-not-recognised refusal the day 'IN' is added, so moving them onto
another basis, or advisory: true while you do, comes first. A regime that
localizes changes more:
import { resolve } from 'ts-prorm-orm';

resolve(['EU', 'RU']).residency;           // { localize: 'primary', regions: ['ru'], transferRequires: 'approval' }
resolve(['EU', 'RU']).breachNotificationHours;   // 24
const r = resolve(['EU', 'US-CA']);
r.digitalConsentAge;       // 16
r.requiresBasis;           // 'always'
r.lawfulBases;             // ['consent', 'contract', 'legal-obligation', 'legitimate-interests']
r.rights;                  // GDPR's seven plus CPRA's opt-outs
r.requestDeadlineDays;     // 30
r.breachNotificationHours; // 72

Keeping it current#

The table is data in one file, dated, with every entry naming its instruments.
When a regulator moves a number, the change is one line and a test. If you
maintain a fork with a regime we do not list, add it to JURISDICTIONS in the
same shape; resolve() and the decorators need nothing else.
Next: Declaring personal data — how a model is held to
these.
Modified at 2026-10-04 00:40:16
Previous
Frameworks: `@Security`
Next
Platform policies
Built with