For product managers

Consent UX that holds up

Consent is a product surface. Each pattern below is a way to meet s.6 and Rule 3.

• One purpose per choice. Bundled consent is not specific.
• Store the notice version with each consent, so legal can prove it later (s.6(10)).
• No pre-ticked boxes. They are hard to square with a clear affirmative action.
• Reject as visible as accept, and no repeated prompts after a no.
• The notice next to the choice, itemised, not only a link to a long policy (Rule 3).
• Withdrawal in the same place, with the same number of steps, as giving consent (s.6(4)).
• Do not make a service depend on consent to data it does not need (s.6).

Keep a purpose register

Every feature that touches personal data should map to a row. When a roadmap item adds a purpose, the register changes before the code ships. A sample for a fictional app, Example Lending:

Children's flows

If under-18s can use the product, design for it. Ask age at sign-up, route minors to a parental consent step that checks the parent is an identifiable adult (Rule 10), and switch off tracking and targeted ads for them (s.9(3)).

For a child, the Data Principal includes the parent (s.2), so build parent access to requests and withdrawal. Rule 12 exemptions apply only to listed classes and purposes, within conditions; do not design around one without counsel.

Instrumentation is personal data

Event streams, session recordings and crash logs that carry a user ID, device ID or phone number relate to an identifiable person. Treat each event as data with a purpose, a retention period and a row in the register. Session replay needs extra care because it can capture whatever users type.

What to do this quarter

1. 01Audit the event schema

   List analytics events tied to user IDs, and drop the ones no purpose needs.

2. 02Inventory SDKs

   List third-party SDKs per build, and what each collects and sends.

3. 03Fix withdrawal

   Put consent settings where users gave consent, and test that withdrawal reaches every downstream tool.

4. 04Ask legal and security

   Get notice text from legal, and confirm with security which new stores will hold personal data.

How TruePrivacy helps

• Consent management holds purposes, a record per person and purpose, a preference page and an event log, with SDKs for iOS, Android and React Native and a web banner script.
• Cookie consent scans your site for trackers so they become consent purposes; banner text ships in English and all 22 Eighth Schedule languages.
• Parental consent handles the guardian request by email, verification with a code, the recorded decision and revocation.
• Records of processing hold your processing activities, synced from discovery and exportable, as the system version of your purpose register.