Consent Records That Survive an Inspection

The inspection was a rehearsal. The DPO asked the vendor to show consent for the campus helpdesk agent. The vendor opened a dashboard: 18,442 agrees. The DPO asked to replay what student 2019/EE/044 saw on 3 February. The dashboard offered a percentage. The notice text had been edited in March. The old text was gone. The withdrawal button mailed a shared inbox that no one owned. The rehearsal was kinder than 2027 will be.

The Digital Personal Data Protection Act, 2023 cares about purpose and basis. Consent, where used, is informed, specific, unconditional, and withdrawable. Agents make this harder because the purpose can drift at the speed of a prompt edit. Purpose tags on the register and on the log are how you keep consent honest. Screenshots of a banner are how you keep a scrapbook.

Guide for DPOs. 16 August 2026. Not legal advice. The Board has existed since 13 November 2025. Operational duties largely wait until 13 May 2027. History you do not record now will be unrecoverable then.

Basis before banner

Do not put a consent banner on a workflow whose real basis is a legitimate use under Section 7, or a statutory function you already perform. Fake consent is worse than an honest Section 7 note: it teaches the citizen they had a choice they did not have, and it will collapse when they withdraw and the function continues.

Where consent is real — optional campus concierge, optional alumni bot, optional survey agent — build a record the inspector can replay. Where it is not, write the Section 7 or other basis on the register and on the notice, and still purpose-limit the agent.

The replayable record

If you cannot replay the notice, you do not have consent. You have a counter.

Field	Why	Failure mode
Principal identifier	Whose consent	Anonymous agree-count
Time and clock source	When	Container time, no TZ
Notice version	What they saw	Live wiki page with no history
Language of the notice	Informed	English-only on a vernacular desk
Purpose tags	Specific	'AI services'
Act (not pre-ticked)	Free and affirmative	Continue implies agree
Withdrawal channel and time	Withdrawable	Mailto nobody
Effect on the agent	Withdrawal is real	Banner changes, retrieval continues

Version the notice the way you version prompts. A March rewrite without the February text is how you fail a February principal. Store the notice body or its hash with the record. Store the purpose tags that the runtime will actually enforce. If the agent can grow a new purpose without a new consent, the record is a story about the past.

Children and employees

Children's data is a refusal by default in this cluster. If a statute forces a workflow, consent is usually the wrong basis and a parent-verifiable process is a specialist design. Do not hide that design inside the adult FAQ bot.

Employee and student 'consent' given to the only helpdesk that can reset a password is rarely free. Prefer an honest legitimate-use or employment-basis note, tight purpose, and a real grievance path. A forced agree is an inspection exhibit.

Two rehearsals

Objections

Product says replay storage is heavy. Answer: the notice body is small. The 18,442 counter is not a record.

Legal says wait until May 2027. Answer: you are already processing. The Board already exists. Design now.

A vendor offers a consent manager in another country. Answer: read the 13 November 2026 consent-manager commencement and the transfer rules. Do not outsource the replay to a tenant you cannot dark-export.

A CIO says we will use consent for everything so we are safe. Answer: you will be unsafe the first time a statutory function continues after withdrawal.

A four-week playbook

• Week 1: split workflows into consent-basis and other-basis. Remove fake banners from the latter.
• Week 2: implement the replayable record and notice versioning for the former.
• Week 3: wire withdrawal to a hard runtime refuse. Test it.
• Week 4: rehearse the inspector query on a named principal and a named date. Fix whatever returns a percentage.

File note you can paste

Subject: Consent and purpose records for agent workflows — design ahead of 13 May 2027.

The Data Protection Board has existed since 13 November 2025. Operational DPDP duties largely apply from 13 May 2027. This department will, from this date, record for each consent-basis workflow a replayable object: principal, time, notice version and language, purpose tags, affirmative act, withdrawal and its effect on the runtime. Section 7 or statutory workflows will not wear a fake consent banner.

Purpose tags will match the AI register and the tool allow-list. This note is not legal advice.

Withdrawal that actually stops the machine

The inspector's second question, after replay, is withdrawal. Show a principal who withdrew yesterday. Show the runtime refuse today with CONSENT_WITHDRAWN. Show that retrieval of their old tickets has stopped, or show the lawful residual you still hold and why. If withdrawal only hides the banner, you have a marketing preference centre, not a DPDP record.

Consent managers, when those provisions apply from 13 November 2026, will add another actor. Design so that a manager's signal can be stored and enforced on your rack, not only in their portal. You remain the fiduciary. Their dashboard is not your replay store unless you can dark-export it.

Purpose tags must be few enough to explain at a counter. 'CAMPUS-FAQ' is a purpose. 'Improve services and partners' is a fishing net. If you need a new purpose, you need a new notice and, on a consent-basis workflow, a new act. Prompt edits that add a purpose are a silent re-collection. Version control should block them without a DPO ticket.

Keep the rehearsal on a calendar, not as a one-off before a Board. Quarterly is enough. Name a principal, a date, a withdrawal. If the store has drifted, you want to know while the Board is still only a rehearsal.

• Never pre-tick. Never 'continue means agree' on a real consent-basis flow.
• Never use employee-password-reset as a consent harvest.
• Never store only the agree-count. Counts are not records.

Informational field guidance, not a Board circular. Confirm the live Act, Rules, commencement notifications and counsel before you file a basis.

How this survives CAG, RTI or the Board

“Consent Records That Survive an Inspection” is not a workshop slide. A P6 Compliance/DPO will have to reconstruct a decision after the officer who clicked approve has been transferred. Write the artefact that lets a stranger replay the case: the log fields, the approval, the override, the register row.

A screenshot of a pre-ticked box will not survive the Board. If consent is your basis, record who, when, what purpose, what notice, what language, and how withdrawal works. If Section 7 is your basis, do not dress it up as consent. India AI Governance Guidelines (November 2025) are guidelines, not a statute. DPDP still allocates fiduciary duty. Delegation of Financial Powers still allocates who may spend. Do not hide those instruments behind the word governance.

If you cannot show who acted, on which purpose, with which data class, and who could have refused, you do not have accountability. You have a chatbot with a charter PDF.

• Name the owner of “consent record DPDP audit” inside the department, not the vendor.
• Keep CERT-In-relevant logs in India for the required period.
• Store overrides with a reason an auditor can read.
• Put the workflow on the AI register before it touches a citizen.

Close this loop before the next CAB

Put “Consent Records That Survive an Inspection” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P6 Compliance/DPO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “consent record DPDP audit” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.