Core Concepts
Five entities make up the model you'll integrate against. This page is the map; each linked page goes deeper.
ConsentNotice (DRAFT → ACTIVE → ARCHIVED; versioned; one per language per group)
└── Purpose (marketing, analytics, ... — what you collect data FOR, and why it's lawful)
DataPrincipal (the person — your end user)
├── ConsentRecord (one per notice they've responded to — what they said yes/no to, and when)
├── DsrRequest (an access/correction/erasure request they've filed)
└── GrievanceRequest (a complaint they've filed)
- Data Principals — who your end users are in this system, and how registration/identification works.
- Consent Notices — what a notice is, why it's versioned, and what
noticeGroupKeyactually means (this trips people up — read it before you hardcode anything). - Consent Records — the actual evidence of what a principal agreed to, and the non-repudiation guarantee behind it.
- DSR & Grievances — the principal-rights side: access/correction/erasure requests and complaint handling.
The one relationship worth internalizing early
A consent notice describes what you're asking for. A consent record is evidence of what a specific
principal actually agreed to, and when. These are deliberately separate: editing a notice's purposes doesn't
retroactively change what already-collected consent records say — that's what makes a consent record's
sha256Checksum meaningful as non-repudiation evidence. If you take away one thing from this page, it's that
your integration should always resolve "the current notice" by noticeGroupKey + language, not by a specific
notice ID — see Consent Notices for why.