Consent Architecture
Capturing, versioning and propagating consent to every system that acts on the data.
5 to work through
-
intermediate
A customer withdrew marketing consent three weeks ago and is still receiving emails. The consent record is correct. Where is the failure?
2 min answer -
advanced
A regulator asks how you ensure marketing consent withdrawal is honoured everywhere. What does the architecture need to show?
2 min answer -
advanced
An insurance platform must record and honour consent across many purposes and channels. What must the architecture provide?
2 min answer -
advanced
Consent must be captured, honoured across every system, and proven to a regulator. How should this be architected, and why do consent implementations usually fail?
2 min answer -
advanced
Design consent management for a publisher with advertising, analytics and personalisation across web and apps.
1 min answer
3 terms in this topic
Consent Architecture
Capturing, storing and enforcing a person's permissions for specific processing purposes, across every system that acts on their data.
practiceConsent Propagation
Carrying a consent decision - and especially a withdrawal - to every system and third party that processes on the basis of it, which is where most co…
conceptUse-Time Enforcement
Checking permission at the moment data is used rather than at the moment it is collected, because a copied permission flag is stale the moment it is made.
Neighbouring topics
Regulatory & Data Protection Architecture
General material on designing under legal and regulatory obligation.
Privacy by Design
Data minimisation, default protection and purpose binding as structural decisions.
Lawful Basis & Purpose Limitation
Why you may hold the data, and why that forbids the second use somebody proposed.
Data Subject Rights
Access, correction, portability and erasure across systems that never planned for them.
Data Residency
Keeping data within a jurisdiction, including backups, logs and support access.
Digital Sovereignty
Control over data, operations and the operator, beyond where the bytes physically sit.
Cross-Border Transfer
The legal mechanism that permits data to leave, and the architecture that respects it.
PCI-DSS Scoping
Segmentation and tokenisation to shrink what is in scope, because scope is the cost.
Healthcare Data Protection
PHI handling, minimum necessary access, and audit expectations in clinical systems.
Financial Services Regulation
Operational resilience, payment rules and supervisory expectations as design inputs.
Records Retention & Legal Hold
Keeping what must be kept, deleting what must go, and freezing both on demand.
Erasure vs Immutability
Deletion obligations against event logs, backups and ledgers designed never to forget.
Pseudonymisation
Separating identity from record, and the re-identification risk that remains.
Privacy-Enhancing Technologies
Differential privacy, secure enclaves and federated computation, and what each buys.
Regulatory Reporting Pipelines
Submissions with fixed deadlines, fixed formats, and a regulator who audits the lineage.
Sector Cloud Rules
Regulator expectations for cloud use, exit plans and material outsourcing notification.
Exit & Concentration Risk
Being able to leave a provider, and what the regulator asks when you cannot.
Third-Party Risk
Assessing, contracting and monitoring the vendors your architecture now depends on.
Geo-Restriction & Sanctions
Blocking access by jurisdiction, and the accuracy and evasion problems that come with it.