> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/platform/platform-services/consent-management/design/standards-and-best-practices.md). # Standards & best practices How the Consent Manager aligns with Kantara / ISO 27560, GDPR, DEPA / Account Aggregator and DCI / OIDC, and what is built against each. The design is measured against four reference frameworks. | Framework | Why it applies | | -------------------------------------------------------- | ------------------------------------------------------------------------------------ | | **Kantara Consent Receipt v1.1 / ISO/IEC 29184 & 27560** | A portable consent record and receipt. | | **GDPR** | Lawful basis, purpose limitation, minimisation, data-subject rights. | | **DEPA / Account Aggregator** | Granular, revocable, time-bound consent artefacts with fetch semantics. | | **DCI + OAuth2 / OIDC** | Interoperable consent payloads; an authentication context from a validated ID token. | ## Kantara / ISO 27560: consent receipts * **Best practice:** a receipt is a complete consent record (controller and contact, DPO, purposes with legal basis, data categories, retention, third parties, withdrawal method, jurisdiction, version) with a cryptographic proof. * **Built:** every consent has a [receipt](/platform/platform-services/consent-management/design/data-model.md#consent-receipt-kantara-iso-27560) signed with the CM's asymmetric key: controllers, purposes with legal basis, data categories, third parties, withdrawal method, version, and the artefact hash. * **Not yet:** the controller's name, contact and DPO, retention and jurisdiction. * **Not to be confused with the consent token**, a short-lived JWS for one registry and query ([Exchange consent tokens](/platform/platform-services/consent-management/design/exchange-receipts.md)), closer to an OAuth 2.0 token-exchange token (RFC 8693) than to a receipt. ## GDPR: data-subject rights * **Best practice:** subjects can access their consents, withdraw at any time, and be informed; every consent records a lawful basis and a purpose. * **Built:** access ([`GET /my/consents`](/platform/platform-services/consent-management/api/subject-api.md), `GET /my/receipts/{id}`) and withdrawal (`POST /my/consents/{id}/revoke`), on the beneficiary API (off by default); purpose, recipients and lawful basis on every receipt; purpose limitation and minimisation at every decision. * **Not yet:** notifying the subject of grants, revocations and expiry. ## DEPA / Account Aggregator: artefact semantics * **Best practice:** consent is granular, time-bound and revocable, with fetch semantics (one-shot or periodic, frequency, data life). * **Built:** a grant per data controller; validity bounded by policy; revocation per artefact with a status endpoint; `fetch_type`, `max_fetch_frequency` and `data_life` on the partner's [access policy](/platform/platform-services/partner-management/functional-specifications.md#access-policies), `fetch_type` also on the artefact; purpose codes capped by policy. * **Not yet:** enforcing fetch frequency and data life; notifying all parties of a revocation. ## DCI / OIDC: interoperability and authentication context * **Best practice:** accept interoperable, signed consent payloads; build an authentication context from a validated ID token, with JWKS-based key rotation. * **Built:** a partner-signed consent as a compact JWS in the DCI `authorize` block, verified against Partner Management keys (from partners whose policy allows it); consents collected through the CM used by ID or found by lookup; ID tokens checked against the provider's JWKS ([Security & trust](/platform/platform-services/consent-management/design/security-and-trust.md#id-token-validation-origination)). ## Cross-cutting | Concern | How it is met | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Signing | Asymmetric only: partner consents verified with keys from Partner Management; receipts and tokens signed with the CM's `.p12` key (EdDSA / ES256 / RS256) and published at `/.well-known/jwks.json` | | Partner agreement | Versioned access policies in Partner Management, changed by approval there, applied on every decision; decisions record the policy version | | Separation of duties | PDP/PEP: the CM decides, the registry enforces | | Non-repudiation | Signed receipts and an append-only decision log | | Replay | `jti` + freshness window | | History | Status changes only add; timestamps are never overwritten | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.openg2p.org/platform/platform-services/consent-management/design/standards-and-best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.