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

Subject rights

Every regime in the registry grants the people whose
data you hold some set of rights over it — to see it, correct it, have it
deleted, take it away in a usable format, object to how it is used — and gives
you a clock to answer within (30 days under GDPR, 45 under the US state acts,
10 in Korea and Argentina). The declaration says which rights are owed;
these modules do the work of honouring them.
RightModuleKeyed on
access, portabilityDataPortabilityExporterthe subject: true field
erasureRightToErasurethe same
all of them, as a tracked requestDSARWorkflowa request id
the basis you rely onConsentRecord / ConsentVersioningsubject + purpose
the assessment before you startPrivacyImpactAssessmentan assessment id

A request, start to finish#

DSARWorkflow is the state machine around a request — created, in progress,
fulfilled, delivered, completed, or rejected / expired — and it dispatches the
work to the exporter or the eraser by request type.
import { DSARWorkflow } from 'ts-prorm-orm';

const request = DSARWorkflow.createRequest('user-42', 'access');   // 'access' | 'rectification' | 'erasure' | 'portability' | 'restriction' | 'objection' | 'withdrawal'

DSARWorkflow.startProcessing(request.id);
const fulfilled = await DSARWorkflow.fulfillRequest(request.id, {
  models: [{ model: User }, { model: Order, where: { userId: 'user-42' } }],
  format: 'json',
});
DSARWorkflow.markDelivered(request.id);
DSARWorkflow.completeRequest(request.id);

DSARWorkflow.getRequestsForDataSubject('user-42');
DSARWorkflow.getRequestsByStatus('pending');
DSARWorkflow.getExpiredRequests();          // open and past their deadline — the ones a regulator asks about
DSARWorkflow.expireOverdue();               // move those to 'expired' (run it on a schedule)
DSARWorkflow.rejectRequest(request.id, 'identity not verified');
The line: the request register is an in-memory Map. It is the shape of
the workflow, not its storage — persist requests in a table you own, and use
the workflow to drive the state transitions and the fulfilment. The deadline
is the shortest of the request's regimes (below); the regime's deadline is
also on the sheet as requestDeadlineDays.
The transitions are a fixed table (canTransition() in
src/compliance/dsar-workflow.ts); a call that does not match one throws
Cannot … request in status: …:
fulfillRequest() only runs from in_progress, so call startProcessing()
first. A fulfilment that throws — an erasure that hits a foreign key, say —
moves the request to rejected with the error as rejectionReason, and a
rejected request cannot be reopened: create a new one.
DSARWorkflow.expireOverdue() moves every open request (pending,
in_progress, pending_fulfillment) whose deadline has passed to expired
and returns them; getRequestsByStatus('expired') runs it first. A request
that was fulfilled or delivered is not expired: it was answered.
getExpiredRequests() still lists the overdue requests without changing them.
The deadline is the shortest clock of the regimes the request is made
under: GDPR, UK GDPR, HIPAA and PIPEDA 30 days, CCPA/CPRA and the other US
state laws 45, LGPD 15, PIPA 10, and 30 for a regime not in the table
(DSAR_DEADLINE_DAYS). The regimes default by request type (an erasure is
GDPR, CCPA and LGPD, so 15 days); pass your own, the date it was received, or
a fixed number of days:
DSARWorkflow.createRequest('user-42', 'access', { frameworks: ['GDPR', 'CCPA'] });  // 30 days
DSARWorkflow.createRequest('user-42', 'access', { receivedAt: new Date('2026-09-01'), deadlineDays: 30 });
[!NOTE]
Before 4.9.2, createRequest() set every deadline to 60 days, and nothing
ever moved a request to expired. Requests created by an older release keep
their 60-day deadline.

An erasure request, end to end#

A handler that takes a verified erasure request for a user held to EU and
US-CA, answers inside the regimes' deadline, and keeps what the workflow
does not:
import { DSARWorkflow, RightToErasure, complianceOf } from 'ts-prorm-orm';

declare const User: any, Order: any, Comment: any;
declare const dsarStore: { save(row: Record<string, unknown>): Promise<void> };

export async function eraseSubject(userId: string) {
  // resolve(['EU', 'US-CA']).requestDeadlineDays is 30: the shortest clock wins.
  const days = complianceOf(User)?.resolved.requestDeadlineDays ?? 30;
  const request = DSARWorkflow.createRequest(userId, 'erasure', { deadlineDays: days });
  const dueBy = request.deadline!;
  await dsarStore.save({ id: request.id, userId, type: 'erasure', dueBy });   // the durable copy

  if (!(await RightToErasure.exists(User, { where: { id: userId } }))) {
    DSARWorkflow.rejectRequest(request.id, 'no data held for this subject');
    return DSARWorkflow.getRequestStatus(request.id);
  }

  DSARWorkflow.startProcessing(request.id);
  await DSARWorkflow.fulfillRequest(request.id, {
    models: [{ model: User, where: { id: userId } }],
    erasureOptions: {
      mode: 'anonymize',                              // orders must still add up
      piiFields: ['name', 'email', 'phone'],
      cascade: [
        { model: Order, foreignKey: 'userId', piiFields: ['shippingName', 'shippingAddress'] },
        { model: Comment, foreignKey: 'userId', piiFields: ['body'] },
      ],
    },
    notes: `due ${dueBy.toISOString().slice(0, 10)}`,
  });

  return DSARWorkflow.completeRequest(request.id);    // fulfilled → delivered → completed
}
For erasure, fulfillRequest() calls RightToErasure.erase() once per
entry in models, with the where you give; without a mode in
erasureOptions it hard-deletes. An access or portability request with
the same models list produces request.exportData instead, as
{ content, format, recordCount }.

Access and portability#

Export what you hold about one person, as JSON, CSV or NDJSON, walking
associations and respecting field-level view permissions.
import { DataPortabilityExporter } from 'ts-prorm-orm';

const result = await DataPortabilityExporter.export(User, {
  where: { id: subjectId },
  include: [Order, Address],
  format: 'json',                 // 'json' | 'csv' | 'ndjson'
  excludeForRole: 'export',       // fields hidden from this role are left out
});

// Every model that holds something about the subject, in one response:
const bundle = await DataPortabilityExporter.createDSARResponse(subjectId, [
  { model: User },
  { model: Order, where: { userId: subjectId } },
  { model: SupportTicket, where: { requesterId: subjectId } },
], { format: 'json' });

// Large sets: stream to a writer rather than build in memory.
await DataPortabilityExporter.exportStream(Event, {
  where: { userId: subjectId },
  format: 'ndjson',
  onChunk: (chunk) => res.write(chunk),
});
createDSARResponse keys each model on id — pass a where for models where
the subject is a foreign key.

Erasure#

import { RightToErasure } from 'ts-prorm-orm';

await RightToErasure.exists(User, { where: { id: subjectId } });    // before promising an outcome

const result = await RightToErasure.erase(User, { where: { id: subjectId } }, {
  mode: 'anonymize',                     // or 'delete'
  piiFields: ['name', 'email', 'phone'], // what 'anonymize' overwrites
  redactedValue: '[REDACTED]',
  cascade: [
    { model: Post,    foreignKey: 'userId', piiFields: ['authorName'] },
    { model: Comment, foreignKey: 'userId' },
  ],
});
'delete' hard-destroys the rows; 'anonymize' overwrites the PII fields in
place, which is usually what you want when other records must keep referring
to the row (an order still happened; the customer's name on it need not
survive). cascade walks associated models recursively.
In 'delete' mode the eraser reads the subject's keys first and erases the
cascade's children before the parent rows, so the children are found and
removed and a foreign key does not block the parent's delete. 'anonymize'
without piiFields overwrites the model's classified PII fields, or, when
none are classified, its text columns other than the key, the timestamps and
foreign keys (association keys, references columns and the cascade's
foreignKey). Naming piiFields on every target is still the clearest.
[!NOTE]
Before 4.9.2 a 'delete' cascade looked up the subject's ids after deleting
them, found nothing, and left the child rows in place; and 'anonymize'
without piiFields overwrote every column except id, createdAt and
updatedAt, foreign keys and numbers included.
Two things erasure does not know about, and you must: backups (a purge
today is a restore tomorrow — see Retention & integrity)
and the audit trail, which under some regimes you are obliged to keep even
after erasing the row it describes. Anonymise the trail's payload rather than
deleting it.

Consent#

The basis you rely on when it is consent, recorded so that you can show it.
import { ConsentRecord, LegalBasisEnum } from 'ts-prorm-orm';

await ConsentRecord.initialize(prorm);          // creates consent_records

await ConsentRecord.grant({
  subjectId: 'user-42',
  purpose: 'marketing_email',
  legalBasis: LegalBasisEnum.Consent,           // Consent | Contract | LegalObligation | VitalInterests | PublicTask | LegitimateInterests
  version: '2026-09',                           // the wording they agreed to
  ipAddress: req.ip,
});

await ConsentRecord.isActive('user-42', 'marketing_email');    // boolean
await ConsentRecord.withdraw('user-42', 'marketing_email');
await ConsentRecord.getHistory('user-42');
await ConsentRecord.getActiveConsents('user-42');
await ConsentRecord.getConsented('marketing_email');            // subject ids, for a send
The log is append-only: a withdrawal adds a row rather than editing the
grant, so the history is intact — which is what an auditor asks to see.
ConsentVersioning is a second implementation of an overlapping idea, with
its own table (consent_versions) and an emphasis on the version of the
terms agreed to:
import { ConsentVersioning } from 'ts-prorm-orm';

await ConsentVersioning.initialize(prorm);
await ConsentVersioning.recordConsent('user-42', 'analytics', true, '1.0');
await ConsentVersioning.reGrantConsent('user-42', 'analytics', '2.0');   // supersedes 1.0
await ConsentVersioning.validateConsent('user-42', 'analytics');         // true
await ConsentVersioning.revokeConsent('user-42', 'analytics');
await ConsentVersioning.getConsentHistory('user-42', 'analytics');
Pick one and use it consistently. The two tables are not coordinated, and
a subject who withdrew in one is still consenting in the other.
Consent is one basis of six. The jurisdiction check
refuses a basis a named regime does not recognise, and India accepts neither
contract nor legitimate interests — a model held to IN that is not on
consent, legal obligation, vital interests or public task will not load.

Children#

Below the age of digital consent a parent consents. The
age gate enforces
that at write time on models with @DataSubjectAge() and @ParentalConsent();
the consent record for the parent's act belongs in ConsentRecord like any
other, with the parent as the subject and the child's purpose. On the
managed platform the whole flow — a child's signup, the parent's invitation,
their consent, and emancipation at 18 — is built in; see the
family features.

Privacy impact assessments#

GDPR Art. 35 and its cousins want an assessment before high-risk
processing starts. This is the record-keeping for one:
import { PrivacyImpactAssessment } from 'ts-prorm-orm';

await PrivacyImpactAssessment.initialize(prorm);

const pia = await PrivacyImpactAssessment.createAssessment(
  'Behavioural analytics',
  ['email', 'ip_address', 'page_views'],
  'improve product recommendations',
);
await PrivacyImpactAssessment.recordRisk(pia.id, 'Re-identification from page views', 'high', 'Aggregate to daily counts; drop IPs after 24h');
await PrivacyImpactAssessment.linkToModel(pia.id, PageView);

await PrivacyImpactAssessment.submitForReview(pia.id);
await PrivacyImpactAssessment.hasUnresolvedHighRisks(pia.id);    // gate the approval on this
await PrivacyImpactAssessment.approveAssessment(pia.id, 'dpo@example.com');
// or PrivacyImpactAssessment.rejectAssessment(pia.id, 'mitigation insufficient')

await PrivacyImpactAssessment.getByStatus('approved');          // 'draft' | 'in_review' | 'approved' | 'rejected'
await PrivacyImpactAssessment.getRisksBySeverity(pia.id);       // { low, medium, high, critical }
Severity is whatever the person recording the risk says it is; there is no
scoring model. The value is the record — linked to the models it covers, with
who approved it and when — which is exactly what is asked for.
Next: Retention & integrity.
Modified at 2026-10-04 00:40:16
Previous
Status
Next
prorm with decorators
Built with