Self-assessment
Score yourself
Answer each question honestly. Yes = 2, Partly = 1, No = 0. Keep a running total.
Your score
0/ 24
0 of 12 answered
Not scored yet
The notice
0 / 601 Before any consent-based collection, does the person get a clear notice: the data, the purpose, their rights, how to withdraw, how to complain?
02 Is there one notice per purpose, not one bundled privacy policy?
03 Can the person choose to read it in English or in any of the 22 languages in the Eighth Schedule of the Constitution?
The yes
0 / 604 Is every optional purpose, marketing, cross-sell, sharing with partners, genuinely optional: a "no" does not cost the customer the core service?
05 Is every consent recorded as an explicit action, never a pre-ticked box, silence or inactivity?
06 For every processing activity, is the legal basis written down: consent, or one of the permitted non-consent grounds?
The withdrawal
0 / 607 Can a person withdraw as easily as they consented, on the same channel they used to consent?
08 When consent is withdrawn, does the stop signal reach every system and every partner, with confirmation and a retry path?
09 Have you tested withdrawal end to end: withdraw in one channel, verify the stop in every other channel and at every partner?
The proof
0 / 610 Do consents from every channel, website, app, call centre, branch, WhatsApp, SMS, email, merge into one consent record per person?
11 For one customer and one date, could you produce the exact notice version and language they saw and the choice they made?
12 Could your systems receive, validate and honour a consent instruction arriving through a registered Consent Manager?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | Consent on your estate may not be valid consent. Fix notices first; everything rests on them. |
| 9 to 16 | Halfway | The banner works but the machinery behind it leaks. Withdrawal propagation and the single consent record are the usual holes. |
| 17 to 21 | Strong base | Prove it: run the one-customer test at the end of this page, and a full withdrawal trace. |
| 22 to 24 | Leading | Watch drift: new campaigns and new channels quietly bypassing the hierarchy. Keep the maker-checker gate honest. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What valid consent requires
Before collecting personal data on the basis of consent, you owe the person a notice: a clear description of the data you want, the purpose, how they can exercise their rights, how to withdraw consent, and how to complain to the Data Protection Board. Consent given without a proper notice is not valid consent, and every downstream use of that data then rests on nothing.
Under the Act, consent is valid only when it is free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action. A pre-ticked box, a bundled "agree to everything", or consent forced as a condition for an unrelated service can all fail the test, taking the legal basis for the processing with them. Withdrawal must be as easy as giving, and when consent dies, your processors must stop too.
The framework: four moves
Move 1: Write the notice suite. One notice per purpose, each class of data and each purpose described separately. Offer the choice of English or any of the 22 Eighth Schedule languages; the choice is the person's under the law, and large organisations are preparing all 22 as practice. Keep every published version on file with its dates: the notice that matters in a complaint is the one shown on that day. Put publishing behind a maker-checker workflow so one person cannot silently change what customers see.
Move 2: Design the yes. Separate purposes so each can be accepted or refused on its own. Record every choice as an explicit action. For each processing activity, write down the legal basis: consent, or a permitted non-consent ground such as voluntary provision for a purpose the person asked for, certain state functions, employment purposes or medical emergencies. Never manufacture a consent record for an activity that properly runs on another basis.
Move 3: Build withdrawal that propagates. Map every system and partner that receives data under each purpose. Build the withdrawal signal to reach all of them, with confirmation and retries. Test end to end. For anyone under 18, and for a person with disability who has a lawful guardian, consent comes from the parent or guardian and you must verify that relationship; collect the minimum data needed for the check. Behavioural monitoring of children and targeted advertising at them are prohibited.
Move 4: Keep the artefact. The consent artefact is the stored proof of a consent event: the exact notice version and language shown, the data categories and purposes, the choice, the time, the channel, the identity it belongs to. Make records tamper-evident, aligned with the Government's published electronic consent framework, exportable in readable form, kept for the life of the relationship and the required period after. "Our system shows a tick" is not enough if nobody can reconstruct what the tick referred to.
One more layer: Consent Managers, registered platforms through which a person manages consent across enterprises from one place, are in force now. If your sector will interact with them, finance already has account-aggregator-style sharing, your systems must honour external consent instructions exactly like ones captured on your own screens.
Template: the notice and consent register
One row per purpose per channel. Copy this and fill it in.
| Purpose | Legal basis | Notice version | Languages | Channels | Systems and partners fed | Withdrawal route | Artefact stored where |
|---|---|---|---|---|---|---|---|
| Example: account opening | Consent | v3.2 | English, Hindi, +6 | App, branch | Core banking app, KYC agency | App settings, branch form | Consent store, exportable |
The downloadable file adds the consent artefact field list: the exact proof each consent event must leave behind.
What good looks like at the end
You should have: an approved notice set with version history, consent journeys on every channel including offline, a working artefact store, tested withdrawal propagation, and the records to prove all of it.
The live test: pick one customer and one date. Produce the notice they saw, in the language they saw it, and the choice they made. Then withdraw a consent in one channel and watch every other channel and partner stop. If either takes weeks, the machinery is not there.
Where enterprises go wrong
- One bundled privacy policy treated as the notice.
- Silent edits to notices with no version history, and translations that drift from the approved text.
- One yes covering everything, or dark patterns that make "no" hard to find.
- Withdrawal handled only in the app while the CRM and marketing platform keep processing.
- Consent evidence dying inside a vendor's subscription with no exit export.
The decisions to make
- Cookie and tracker consent: in scope or not, on which properties.
- Offline and branch capture: required or not, and how it is digitised to the same evidence value as online.
- Language coverage depth: the two you need, or all 22.
- The artefact standard to align to.
- Build, buy or extend existing tooling for consent management, decided after your systems are mapped, not before.
- How and when to prepare for Consent Manager interactions.
Next step
Answering people, the requests and grievances your consent records will have to support. If you need help with any of this, write to us and we will help.