THE DESIGN BEHIND THE DEMONSTRATION
A choice should survive a change of mind.
Consent design starts before a button and continues after it. The playground makes three decisions visible: what a person is being asked, what they choose, and what happens when that choice changes.
Say what the data is for.
The example separates product news, research invitations and personal recommendations. Each has its own data description and consequence. These are design examples for optional activities, not a claim that every processing activity requires consent.
Do not bundle unrelated decisions.
Allowing product news changes only that purpose. Research and recommendations remain untouched. The buttons have equal prominence, nothing is preselected, and declining takes the same number of steps as allowing.
Keep the way back in view.
After an Allow choice, a Withdraw button appears in the same place as Decline. The page shows the new state and retains the earlier step in its temporary history. Allowing again records another decision rather than rewriting the previous one.
Make the consequence understandable.
Declining optional news means no news in the fictional service. Declining recommendations means general suggestions. A real service must explain its own consequences accurately; they cannot be copied from this example without understanding the actual processing.
A real system needs more than this switch.
Our history is an illustration. It does not establish identity, prove consent, or tell any external service to stop. An operational design would need to address the following questions, with engineering and legal review.
Which notice and purpose did the person see?
A record needs context: the relevant purpose, notice version and decision. Our fixed “Example notice 1.0” merely demonstrates that relationship. It is not a real notice issued by a data fiduciary.
Which systems need to act on a change?
A real withdrawal can involve several processors and copies of data. Teams need a reliable way to apply changes, handle failed actions and inspect unresolved work. The playground neither connects to nor simulates successful delivery to those systems.
What still needs to be retained, and why?
Withdrawal and deletion are different questions. Other lawful requirements may affect processing or retention. The example does not decide a retention period or promise deletion. See the Act and commencement sources before applying these ideas.
Can the person understand and use the interface?
Review the language, keyboard order, focus, screen-reader output and touch targets. Test whether a person can find a withdrawal path without instructions. This example offers a clear reset, which clears only this page’s temporary demonstration state.
Design explanation checked 30 September 2026. Legal provisions and commencement dates are separated on the sources page.
Read the official source context ↗