4

Collection Simulator

SL-03

What consent collection actually looks like on each channel, with the same notice and the same purposes behind all of them. The simulator exists because a notice that reads well in the studio can be unusable on a kiosk, and the only way to know is to look at it there.

DischargesS.5S.6R.3
Web preview

The reference implementation. Everything else is a constrained version of it.

Privacy Notice

How we will use your information

We will process your personal data for the purposes set out below. You may withdraw your consent at any time, and doing so will be as easy as giving it.

DPDP Act · 3.2
What the artefact records

Identical across every channel. The channel changes the interface, never the evidence.

The exact notice version displayed
The language it was displayed in
Which purposes were agreed, individually
Channel, timestamp and a masked identifier
The withdrawal route offered at the time
A hash chaining this event to the previous one
Obligations exercised here
Cookies are the other half of this

This simulator covers consent to a stated purpose — the notice, the itemised purposes, the artefact. The cookie banner is the same obligation reaching the same citizen through a different door, and it fires before they have read anything. Both need checking, and the cookie one is the one anybody can audit from outside with a browser inspector.

Channel comparison

Web

The reference implementation. Everything else is a constrained version of it.

Mobile app

Same content, one purpose per screen. Scrolling is not reading.

Kiosk

Touch targets sized for a shared terminal, with a session that clears itself.

SMS

160 characters cannot carry a notice. It carries a link and a reference.

IVRHardest

The hardest channel — the notice must be heard, not skimmed.