ANCHORED PURPOSE RECEIPTS

Anchored Purpose Receipts

Records the binding between a processing event and a declared purpose. Provides the cryptographic substrate for purpose-limitation enforcement and Art. 6(4) compatibility analysis — the backbone of a defensible Record of Processing Activities.

APuR · Shipped3 wire typesApache-2.0 · CC0 spec
← All familiesVerify a receipt →

WIRE TYPES

ar.purpose.v1 (purpose.binding)

Records the initial binding of a processing activity to one or more declared purposes. Carries the purpose taxonomy, lawful basis, and data categories — the cryptographic counterpart to a RoPA entry.

ar.purpose.v1 (purpose.repurpose)

Records a secondary use — the original purpose is extended to cover additional processing. Carries an Art. 6(4) compatibility assessment reference.

ar.purpose.v1 (purpose.unbinding)

Records the termination of a purpose binding. The processing activity is no longer conducted for this purpose. Terminal for this binding chain.

WHAT IT PROVES

  • — A processing activity was bound to a specific purpose before processing began (Merkle inclusion proof).
  • — An Art. 6(4) compatibility assessment was conducted before repurposing (chain walk confirms ordering).
  • — A purpose binding was terminated at a specific date (unbinding event).
  • — The purpose binding event was signed by a registered issuer key (Ed25519 signature check).

WHAT IT DOESN'T PROVE

  • — The purpose description was specific enough to satisfy Art. 5(1)(b).
  • — The controller actually limited processing to the declared purpose.
  • — The Art. 6(4) compatibility analysis was substantively correct.
  • — The lawful basis declared in the binding was valid.

COMPOSES WITH

APuR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.

ASRAnchored Subject-Rights Receipts

An Art. 21 objection may terminate a purpose binding — the ASR objection event triggers an APuR unbinding.

AIRAnchored Impact Receipts

DPIA receipts cite APuR purpose-binding receipts being assessed.

ATokRAnchored Tokenization Receipts

ATokR scope declarations reference APuR purpose bindings as the durable purpose record.

Verify any
APuR receipt.

verify.dekimu.com ↗

Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.

REFERENCES

GDPR Art. 5(1)(b) — Purpose limitation principle (EUR-Lex) ↗
GDPR Art. 6(4) — Compatibility of further processing (EUR-Lex) ↗
GDPR Art. 30 — Records of processing activities (EUR-Lex) ↗

Anchored Purpose Receipts are cryptographic provenance and privacy-lifecycle protocols. verify.dekimu.com is a reference implementation, not a qualified trust service under Regulation (EU) No 910/2014 (eIDAS) or successor.