# Pryv compliance matrix > Maps 15 regulations and standards (GDPR, HIPAA, Swiss nLPD, CCPA, PIPEDA, DiGA, MDR, HDS, ISO 27001, ISO 27701, ISO 13485, SOC 2 and more) requirement by requirement onto what Pryv, the platform built from open-pryv.io, implements, makes configurable, facilitates or documents, and what stays with the implementer. 439 requirements, each backed by evidence (tests, docs, configuration keys). Use it to answer questions such as "does Pryv support GDPR Art. 17 erasure?" or "what is left for me to do for HIPAA 164.312(b)?". Start from the scope file, then follow its evidence links. This matrix describes the software's contribution to compliance. It is not legal advice and not a certification: implementer organisations remain responsible for their own GDPR, HIPAA, ISO, MDR or HDS posture. Rows marked draft are authored but not yet reviewed. ## Regulations and standards - [California Consumer Privacy Act (as amended by CPRA) (CCPA / CPRA)](https://pryv.github.io/compliance-matrix/regulations/ccpa.md): regulation, US, California (extraterritorial via business-nexus thresholds); 18 requirements (3 implemented, 3 configurable, 9 facilitated, 3 out-of-scope) - [Data Governance (DAMA-DMBOK knowledge areas) (Data Governance)](https://pryv.github.io/compliance-matrix/regulations/data-governance.md): discipline, International (framework); 11 requirements (5 facilitated, 6 out-of-scope) - [Digital Healthcare Act (DVG) + DiGA Ordinance (DiGAV) (DiGA)](https://pryv.github.io/compliance-matrix/regulations/diga.md): regulation, Germany; 24 requirements (4 implemented, 1 configurable, 13 facilitated, 6 out-of-scope) - [General Data Protection Regulation (GDPR)](https://pryv.github.io/compliance-matrix/regulations/gdpr.md): regulation, EU + EEA (extraterritorial via Art. 3); 47 requirements (6 implemented, 3 configurable, 31 facilitated, 7 out-of-scope) - [Hébergement de Données de Santé (Health Data Hosting Certification) (HDS)](https://pryv.github.io/compliance-matrix/regulations/hds.md): hosting-cert, France; 13 requirements (2 implemented, 2 configurable, 5 facilitated, 4 out-of-scope) - [HIPAA Breach Notification Rule (HIPAA-Breach)](https://pryv.github.io/compliance-matrix/regulations/hipaa-breach.md): regulation, US; 13 requirements (9 facilitated, 4 out-of-scope) - [HIPAA Privacy Rule (HIPAA-Privacy)](https://pryv.github.io/compliance-matrix/regulations/hipaa-privacy.md): regulation, US; 35 requirements (7 implemented, 2 configurable, 21 facilitated, 5 out-of-scope) - [HIPAA Security Rule (HIPAA-Security)](https://pryv.github.io/compliance-matrix/regulations/hipaa-security.md): regulation, US; 41 requirements (9 implemented, 8 configurable, 16 facilitated, 8 out-of-scope) - [ISO 13485, Medical devices, Quality Management Systems, Requirements for regulatory purposes (ISO 13485)](https://pryv.github.io/compliance-matrix/regulations/iso-13485.md): standard, International (ISO); 10 requirements (1 implemented, 9 facilitated) - [ISO/IEC 27001, Information Security Management Systems, Requirements (ISO 27001)](https://pryv.github.io/compliance-matrix/regulations/iso-27001.md): standard, International (ISO/IEC); 74 requirements (7 implemented, 3 configurable, 45 facilitated, 19 out-of-scope) - [ISO/IEC 27701, Extension to ISO/IEC 27001 for Privacy Information Management (ISO 27701)](https://pryv.github.io/compliance-matrix/regulations/iso-27701.md): standard, International (ISO/IEC); 26 requirements (11 implemented, 2 configurable, 10 facilitated, 3 out-of-scope) - [Medical Device Regulation (MDR)](https://pryv.github.io/compliance-matrix/regulations/mdr.md): regulation, EU + EEA; 23 requirements (11 facilitated, 12 out-of-scope) - [Personal Information Protection and Electronic Documents Act (Canada) (PIPEDA)](https://pryv.github.io/compliance-matrix/regulations/pipeda.md): regulation, Canada (federal, private sector); 13 requirements (4 implemented, 1 configurable, 7 facilitated, 1 out-of-scope) - [SOC 2, AICPA Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy) (SOC 2)](https://pryv.github.io/compliance-matrix/regulations/soc2.md): standard, United States (AICPA); 61 requirements (8 implemented, 5 configurable, 38 facilitated, 10 out-of-scope) - [Swiss Federal Act on Data Protection (revised FADP / nLPD) (Swiss nLPD)](https://pryv.github.io/compliance-matrix/regulations/swiss-nlpd.md): regulation, Switzerland (extraterritorial via Art. 3 for processing affecting CH); 30 requirements (5 implemented, 1 configurable, 18 facilitated, 6 out-of-scope) ## Context notes Cross-cutting explanations the requirements refer to (for example `context/event-history.md`). - [Pryv access versioning: implementation findings](https://pryv.github.io/compliance-matrix/context/access-versioning.md): Source-of-truth for the matrix's claims about access immutability + consent-contract preservation. Findings from reading the `open-pryv.io` master branch implementation directly. - [pryv-account-backup: DSAR coverage matrix](https://pryv.github.io/compliance-matrix/context/account-backup-coverage.md): **Status:** implementer reference + audit of `pryv-account-backup` **v0.7.0** (`@pryv/account-backup`) against GDPR Art.15 / Art.20, CCPA §1798.110 / §1798.115, PIPEDA Principle 4.9, and Swiss nLPD Art.25. Originally recorded from the gap-probing session (Q10, 2026-05-20) against v0.2.3; refreshed 2026-05-27 (v0.4.0 DSAR-completeness), 2026-06-13 (v0.5.0 chunked-events + accesses-completeness), 2026-06-15 (v0.6.0 library + CLI split + incremental backup + audit-as-events + browser-isomorphic core + sample webapp), and 2026-06-15 (v0.7.0 attachments / HFS / webhooks browser-isomorphic + portable `sync-state.json` for browser cross-session incremental). - [Audit archival + tiering via custom `@pryv/datastore`](https://pryv.github.io/compliance-matrix/context/audit-archival-via-custom-datastore.md): **Status:** architectural pattern, Pryv's answer to "audit grows unboundedly over a 5-10 year deployment". No Pryv-shipped pruning primitive; the answer is "use the `@pryv/datastore` extension hook + write a custom audit storage tier". Recorded from the gap-probing session (Q16, 2026-05-20). - [Breach notification delivery: voluntarily missing at the platform, operator-owned](https://pryv.github.io/compliance-matrix/context/breach-notification-delivery-operator-owned.md): GDPR Art.34 requires the controller to **communicate a personal data breach to the data subject without undue delay** when the breach is likely to result in a high risk to their rights and freedoms. Equivalent obligations: HIPAA-Breach §164.404 (notification to individuals, ≤60 calendar days), PIPEDA s.10.1 (notification to affected individuals + records for 24 months), Swiss nLPD Art.24 (conditional subject notification, only when necessary for the subject's protection or upon FDPIC request), Cal Civ Code §1798.82 (California breach-notification law, separate from CCPA proper). - [`access.clientData` conventions: consolidated reference](https://pryv.github.io/compliance-matrix/context/client-data-conventions.md): Pryv's `access.clientData` field accepts arbitrary operator-owned JSON. Across the gap-probing session multiple GDPR / privacy conventions have crystallised that re-use this single primitive as the durable, audit-traceable, version-chained metadata store for compliance-relevant claims attached to an access. - [CMC + `consent/*` event types: what the primary consent record is](https://pryv.github.io/compliance-matrix/context/cmc-consent-primitives.md): Source-of-truth for matrix claims about how Pryv carries consent across accounts. Findings from reading `open-pryv.io/components/cmc/` and `data-types/src/consent.json` directly. - [Code-level security review of open-pryv.io (2026-06 to 2026-10)](https://pryv.github.io/compliance-matrix/context/code-security-review-2026.md): Source-of-truth for every matrix claim that cites the 2026 security review of the open-pryv.io source as periodic-evaluation, security-testing or vulnerability-management evidence. Everything said here about individual fixes comes from the public release notes (`open-pryv.io/CHANGELOG-v2.md`, sections `2.0.0-rc.40` to `2.0.0-rc.51`) and from the public report. - [Content-query values in the audit log](https://pryv.github.io/compliance-matrix/context/content-query-audit-semantics.md): Status: design-rationale note, referenced by `gdpr.Art.30`, `hipaa-security.164.312(b)`, `iso-27001.A.8.15` and the `audit` primitive entry in `docs/pryv-primitives.md`. - [Core-affinity architecture (data plane vs PlatformDB)](https://pryv.github.io/compliance-matrix/context/core-affinity-architecture.md): **Status:** architectural fact, recorded from the gap-probing session (Q11, 2026-05-20) after the implementer-perspective question on cross-core time-sync exposed a mental-model gap. This note exists so future matrix authors don't repeat the same miscalibration. - [PlatformDB cross-border implications: the two-tier residency model](https://pryv.github.io/compliance-matrix/context/cross-border-platformdb-implications.md): Pryv's residency story (`context/core-affinity-architecture.md`, `context/account-backup-coverage.md`) is **two-tiered**, not single-tiered. The simplified narrative "Pryv is core-affine" is true for the data mass but incomplete for the identification + routing layer. This note carries the verified picture. - [Custom event-type catalogues: the extension model](https://pryv.github.io/compliance-matrix/context/custom-event-type-catalogues.md): **Status:** Pryv's documented extension surface for implementers needing event types beyond the upstream `pryv/data-types` catalogue. Recorded from the gap-probing session (Q14, 2026-05-20) after the implementer-perspective question on custom event-type support. - [Data accuracy at ingest: structural vs. semantic](https://pryv.github.io/compliance-matrix/context/data-accuracy-structural-vs-semantic.md): GDPR Art.5(1)(d) requires personal data to be **accurate and, where necessary, kept up to date**, with reasonable steps to ensure inaccurate data is **erased or rectified without delay**. For a health-data platform, this is a natural regulator-priority question: "how does the platform prevent garbage data from polluting the record?" - [Data masking: projection vs transformation (Pryv's deliberate scope)](https://pryv.github.io/compliance-matrix/context/data-masking-projection-vs-transformation.md): **Status:** Pryv's design boundary. Recorded from the implementer-perspective gap-probing session (Q9, 2026-05-20). - [Data retention: voluntarily missing at the platform, operator-owned](https://pryv.github.io/compliance-matrix/context/data-retention-operator-owned.md): > **Account-level auto-deletion shipped in open-pryv.io 2.0.0-rc.66 > (2026-10-30):** an account is deleted at a date its holder picks, > or after a period without use, with reminders. It changes the > account level of this note only; the event and stream levels stay > operator-owned. See "Account-level auto-deletion" below, the > operator page `customer-resources/account-auto-deletion` and > `proposals/account-auto-deletion.md`. Transfer to a beneficiary > is implemented and merged, not released yet (last section). - [Account delegation: owner-equivalent control with an authoritative, genuine-login-gated teardown](https://pryv.github.io/compliance-matrix/context/delegation-model.md): Pryv lets one account be controlled by one or more **delegate accounts**. A delegate holds an **owner-equivalent personal token** over the controlled account — it can do everything the account owner can do through the standard API — with a single, deliberate exception: **a delegate can never remove a delegation**, not its own and not a co-delegate's. Removing a delegation (detach) requires a **genuine interactive login on the controlled account itself**. This note describes the model the matrix rows cite; the implementation is the `delegation` plugin at `open-pryv.io/components/delegation/` (shipped on the account-delegation feature line; skeleton `46ae0c23`, handshake `1a797815`, delegate token + audit/accessInfo `6f220187`, authoritative detach `6c618f24`, create-from- delegate `42c4b7d8`, internal-read hardening + same-core audit parity `e75f2155`, wildcard-read exclusion `00edf2a1`). - [Event history is opt-in; what the audit log records without it](https://pryv.github.io/compliance-matrix/context/event-history.md): Source-of-truth for every matrix claim about the prior values of an event (rectification trails, amendment trails, document-control history, "compare against the history"). Findings from reading open-pryv.io master after 2.0.0-rc.38 directly: `config/default-config.yml`, `storages/engines/postgresql/src/dataStore/localUserEventsPG.ts`, `storages/engines/sqlite/src/dataStore/localUserEventsSQLite.ts`, `storages/shared/DeletionModesFields.ts`, `components/api-server/src/methods/events.ts`, `components/audit/src/Audit.ts`. - [Operator backup vs subject DSAR backup: symmetry audit](https://pryv.github.io/compliance-matrix/context/operator-backup-coverage.md): **Status:** implementer reference + audit of the two backup paths Pryv ships, the operator-side `bin/backup.js` (server-side, raw-row disaster-recovery snapshot) and the subject-facing `@pryv/account-backup` (public-API DSAR / portability tool, currently v0.5.0). Companion to `account-backup-coverage.md`, which covers the subject side per-data-type. Last updated 2026-06-13 against `@pryv/account-backup` v0.5.0; operator-side series coverage re-checked against open-pryv.io 2.0.0-rc.34 (2026-10-03); operator incremental backups re-checked against open-pryv.io 2.0.0-rc.51 (2026-10-14); operator backup integrity and authenticity re-checked against open-pryv.io 2.0.0-rc.86 (2026-11-17). - [Per-engine user-data isolation semantics](https://pryv.github.io/compliance-matrix/context/per-engine-isolation.md): Several matrix rows describe Pryv's "per-user storage isolation" as the substrate for compliance obligations like GDPR Art. 25 (data-protection by design), GDPR Art. 32 (security of processing), ISO 27001 A.5.34, HIPAA-Security §164.312(a)(1), PIPEDA Principle 4.7 safeguards, etc. - [Privacy by design + by default: the Pryv-architectural reference](https://pryv.github.io/compliance-matrix/context/privacy-by-design-and-default.md): GDPR Art.25 (and Swiss FADP Art.7, same principle, broader Swiss catalogue) requires controllers to **integrate data-protection principles by design** at architecture time and to **enforce them by default at runtime**. Auditors love this article because it's both meta (gives them a reason to question any architectural choice) AND concrete (the §2 "by default" test has teeth). - [Rate limiting / API throttling / DoS protection](https://pryv.github.io/compliance-matrix/context/rate-limiting-and-dos-protection.md): **Traffic shaping stays at the edge; Pryv enforces targeted in-code budgets.** General rate limiting and DoS protection (volumetric traffic, per-token request rates, WAF rules, DDoS scrubbing) are handled at the reverse-proxy / WAF / API-gateway layer, not inside open-pryv.io. Since open-pryv.io 2.0.0-rc.47 (updated 2026-10-13), Pryv does enforce **targeted budgets on the abuse paths it can count correctly**: failed passwords per account and per client address (counted across all cores), pending access requests per address, pending MFA sessions per account, batch, paging, upload and socket.io message sizes; 2.0.0-rc.50 added an invitation-check budget, a `webhooks.test` interval, a preview pixel cap and render concurrency, an SMS cost cap per core and a restart backoff for crashing workers; 2.0.0-rc.87 bounds password checks per API worker and, on PostgreSQL, the database time of an API request; the release after it caps the calls running at once per account, per access and per socket.io connection, socket.io connections per access and per account, the nesting and size of call parameters, the depth and size of an account's stream tree, the stream ids of one event, idle connections, streamed audit reads per access and the mail a caller can make a core send. The rc.47 and rc.50 budgets came out of the 2026 code-level security review (`code-security-review-2026.md`). Before 2.0.0-rc.47 the only in-process throttle was the per-account MFA backoff (2.0.0-rc.27). See "What is in Pryv-side scope today" below; the edge recipes remain the recommended front. - [`serviceInfo` conventions: operator metadata propagation to client apps](https://pryv.github.io/compliance-matrix/context/service-info-conventions.md): `GET /service/info` is the platform's **operator-controlled metadata surface** for client apps + SDKs + the auth UI. The fields are declared by the operator in their core config and served unchanged to any caller; the values propagate to every `app-web-auth3` consent screen, every SDK that fetches service info, every audit log entry that cites the URL. - [Special-category data: voluntarily missing at platform layer, highly facilitated for vertically-integrated operators](https://pryv.github.io/compliance-matrix/context/special-categories-operator-facilitated.md): GDPR Art.9 (and Swiss nLPD Art.5's broader "sensitive personal data" definition, and HIPAA's "PHI" notion) requires enhanced protection for health data, biometric data for ID, genetic data, etc. A natural regulator question for a Pryv-based health deployment: "how does the platform enforce Art.9 protection?" - [Subprocessor posture + data-flow guarantees](https://pryv.github.io/compliance-matrix/context/subprocessor-posture-and-data-flow.md): For an operator running Pryv as a processor (or as a controller's own software, where "subprocessor" still applies to the third parties their deployment talks to), the Art.28 / Art.30(1)(f) question is: **which external services does my Pryv deployment touch, and what data flows to each?** - [`access.clientData.transfer_basis`: convention for GDPR Art.46 / cross-border transfer recording](https://pryv.github.io/compliance-matrix/context/transfer-basis-convention.md): GDPR Art.46 requires "appropriate safeguards" for transfers outside the EEA absent an adequacy decision (Art.45). The §2 catalogue, SCCs, BCRs, approved codes / certifications, ad-hoc supervisory- authority-approved clauses, defines six mechanisms. Implementers must record which mechanism applies to each cross-border flow they operate. - [Webhooks: signal-only by design](https://pryv.github.io/compliance-matrix/context/webhooks-signal-only.md): A note on Pryv's webhook semantics, recorded during the implementer-perspective gap-probing session (Q7, 2026-05-19) because the design choice is non-obvious + has substantive security implications worth surfacing. - [Workforce access patterns: group access + sub-access derivation](https://pryv.github.io/compliance-matrix/context/workforce-access-patterns.md): Several matrix rows describe Pryv's access-control surface as "per-stream permissions; access is the unit of authorization": ## Other formats - [Everything in one file](https://pryv.github.io/compliance-matrix/llms-full.txt) - [JSON](https://pryv.github.io/compliance-matrix/compliance.json): every scope, requirement, evidence link and planned change - [SQLite](https://pryv.github.io/compliance-matrix/compliance.sqlite): the database the web app reads - [Web app](https://pryv.github.io/compliance-matrix/): the same data, browsable - [Source](https://github.com/pryv/compliance-matrix): YAML per scope, BSD-3-Clause - [Pryv developer documentation](https://pryv.github.io/llms.txt) ## How to read a requirement Coverage (what Pryv does for the implementer): - `implemented`: Pryv ships the control out of the box; it works with no configuration. - `configurable`: Pryv provides the control once the operator sets the configuration keys cited on the requirement. - `facilitated`: Pryv reduces the work; the implementer still does part of it (see the facilitation mode). - `documented`: Guidance only: the implementer does the work, following the cited documentation. - `out-of-scope`: No software contribution from Pryv; the obligation, if any, stays with the implementer. Effort saved (how much of the work Pryv carries): - `high`: Pryv carries most of the engineering and operational work. - `medium`: The work is roughly shared between Pryv and the implementer. - `low`: Pryv contributes a small technical substrate; most of the work is the implementer's. Facilitation mode (the kind of help, mostly on `facilitated` rows): - `primitive`: Pryv's permissions, access versioning or system streams technically enforce the obligation; the implementer chooses the stream layout and permission scope. - `evidence`: Pryv generates structured data (audit log, access version chain, event history) that the implementer uses as proof in an artefact they produce. - `storage`: Pryv durably stores artefacts the implementer creates (notice text, consent records, policies) and makes them recoverable per subject and per time. - `infrastructure`: Pryv runs the technical layer the obligation depends on (TLS, encryption at rest, high availability, data residency, backup and restore). - `awareness`: Pryv has minimal direct contribution; the row reminds the implementer of the obligation. Evidence: test codes resolve at https://pryv.github.io/tests/#, functional specs at https://pryv.github.io/functional-specifications/ and docs paths at https://pryv.github.io//. Generated 2026-11-20T16:02:36.930Z.