← All news and guides
Data protection

DPDP Consent Logs: What to Store, for How Long and in What Shape

The fields, versions and retention a DPDP consent log needs to prove notice and consent under Section 6(10), plus how withdrawal events should work in code.

Mono Team ·

A tall wooden card-catalogue cabinet with rows of small labelled drawers, one pulled open, in a quiet records room with afternoon light.

Short answer: a DPDP consent log is an append-only record of events, backed by versioned tables for purposes and notices, and it must let you prove notice and consent person by person. Section 6(10) of the Act puts that burden on the Data Fiduciary. So each event should say who acted, for which purpose version, against which exact notice text, in what language, through which channel, with what evidence, and at what time. Withdrawal is a new event, never an edit. The Act sets no fixed retention period for a fiduciary's consent records, so keep them long enough to prove consent and at least the one-year minimum in Rule 8(3). The core duties start on 13 May 2027.

This post stays at schema level: fields, versions, retention and withdrawal events. For the service-level view of the whole consent service, read DPDP for engineering teams and our consent management page. It is engineering guidance, not legal advice. What your notice must say, and how long your sector requires records to stay, goes to counsel.

The Act does not tell you to keep a "consent log". It tells you to prove things, and a log is how you do it. Read each duty as a question the log must answer for any one person.

DutySourceWhat the log must be able to show
Notice came with or before the consent requestSource: Section 5(1)What the log must be able to show: Which notice the person saw, and that it was shown before the consent control
Notice itemises the data and the purposesSource: Rule 3(b)What the log must be able to show: The exact list of data items and purposes in that notice version
Notice offered in English or an Eighth Schedule languageSource: Section 5(3)What the log must be able to show: The language the person was shown
Consent is free, specific, informed, unconditional and unambiguous, by clear affirmative actionSource: Section 6(1)What the log must be able to show: One decision per purpose, and what the person actually did (the control, and its state before and after)
Consent is limited to the data necessary for the purposeSource: Section 6(1)What the log must be able to show: The data items attached to that purpose version
Withdrawing is as easy as consentingSource: Section 6(4), Rule 3(c)(i)What the log must be able to show: The withdrawal channel, and a record that it matches the channel used to give consent
Processing stops after withdrawal, including at processorsSource: Section 6(6)What the log must be able to show: Withdrawal time, plus a stop confirmation from each system and processor
The fiduciary can prove notice and consent in a proceedingSource: Section 6(10)What the log must be able to show: All of the above, retrievable for one person in one export

Nothing here asks for an IP address, device fingerprint or screen recording. Collect only what answers these questions.

Treat the log as one table of events. Each row is a fact that happened. Rows are inserted and never updated. These are the fields to start with.

FieldWhat it holdsWhy it is there
event_idWhat it holds: A unique ID, created by the system that captured the eventWhy it is there: Lets you de-duplicate retries and cite one event
person_keyWhat it holds: Your internal pseudonymous ID, not an email address or phone numberWhy it is there: Contact details change. The key must stay stable and should not itself identify the person
consenting_partyWhat it holds: The person, or a parent or guardian acting for a childWhy it is there: A child's consent needs a verified parent or guardian first (see below)
purpose_id and purpose_versionWhat it holds: One purpose per row, with its version numberWhy it is there: Consent is for a specified purpose, so one row per purpose, never one tick for everything
actionWhat it holds: granted, denied or withdrawnWhy it is there: A denial is evidence too. It shows the choice was real
notice_id, notice_hash and languageWhat it holds: The notice version shown, a SHA-256 hash of its exact text, and the languageWhy it is there: You can show what the person saw even after the live page has changed
occurred_at and recorded_atWhat it holds: When the person acted, and when your system stored it, both in UTCWhy it is there: Offline apps and call centres record late. Keep both times
channelWhat it holds: web, android, ios, call_centre, paper_form, whatsapp, consent_manager or legacy_importWhy it is there: Withdrawal must be possible through a comparable channel
capture_contextWhat it holds: The screen or flow ID, app build, the default state of the control and its final stateWhy it is there: Shows the action was affirmative, for example that the box started unticked
actorWhat it holds: The person themselves, or the ID of an agent who captured it on their behalfWhy it is there: Assisted capture in branches and call centres needs an accountable agent
evidence_refWhat it holds: A pointer to a stored artefact such as a call recording ID or a scanned formWhy it is there: Keeps bulky or sensitive proof outside the log, with its own retention
source_refWhat it holds: For events from a Consent Manager, its Registration ID and its own event IDWhy it is there: Lets you verify and trace events that did not start in your system
prev_hash and row_hashWhat it holds: A hash of the previous row and of this rowWhy it is there: Makes silent edits detectable

Log the notice display as its own event type. A person who sees the notice and declines has produced no consent, but you still want to show that the notice came first. A Consent Manager must keep notices alongside consents given, denied and withdrawn (First Schedule, Part B), and the same shape suits you.

Which reference tables does the log depend on?

A wooden card-catalogue cabinet with rows of small drawers, one drawer pulled halfway out showing plain blank index cards, warm light from the side, the background softly blurred.

An event is only as good as the thing it points at. If `purpose_id` 12 means one thing in March and another in June, the log proves nothing. So keep two small tables next to the log, and make every entry in them immutable once published.

  • Purpose register. One row per purpose and version: a stable ID, the plain-language description, the lawful basis (consent, or one of the Section 7 legitimate uses), the data items it needs, the systems and processors that serve it, and the dates it was live. It comes from your data map.
  • Notice register. One row per notice version: the full text, its hash, the language, the purposes it covers, the itemised data list required by Rule 3, the withdrawal and complaint links, and the dates it was live. Store the text in the register, not a link to the live page.

Not every purpose rests on consent. Section 7 lists legitimate uses, such as processing for the purpose a person voluntarily provided their data for. Mark the basis in the purpose register.

When does a purpose or notice need a new version?

Create a new version when anything a person relied on to decide has changed. Even a minor wording fix gets a new notice hash. These cases need a deliberate decision:

ChangeVersion actionConsent action
New data item added to a purposeVersion action: New purpose version and new notice versionConsent action: Ask again for the new scope. Old consent covers only the old scope
Purpose widened, for example from service emails to marketingVersion action: A new purpose, with its own IDConsent action: Fresh consent. Do not stretch the old purpose
New processor or recipient for the same purposeVersion action: New notice version if the notice names recipientsConsent action: Counsel decides whether consent needs refreshing

Whether a particular change needs fresh consent is a legal call. The engineering job is to make the question answerable: the consent event names the exact versions, so you can list every person whose consent predates a change.

Systems that send an email or run a model need a fast answer to one question: may I process this person for this purpose right now? Do not scan the log for that. Build a second table, `consent_state`, with one row per person and purpose, rebuilt from events. It holds the latest action, the purpose and notice versions, and the time of the last change.

  • The log is the source of truth. If the state table is lost or wrong, rebuild it by replaying events in order.
  • Corrections are new events. If an agent recorded the wrong channel, add a correcting event that points at the original. Never edit or delete the original row.
  • Make rows tamper-evident. Restrict the application role to inserts, and chain hashes as in the field list. For stronger protection, copy daily hash checkpoints to write-once storage owned by another team.
  • Check at the point of use. Email, WhatsApp, analytics and model pipelines should read `consent_state` at send time, not once at list-build time. Record any block, so you can show the check ran. For app SDKs, see our mobile SDK audit.
A row of plain white wall light switches on a pale painted wall, one switch pushed down while the others are up, soft daylight from the left, shallow depth of field.

The Act gives the person the right to withdraw at any time, with ease comparable to giving consent (Section 6(4)). Rule 3(c)(i) repeats this in the notice: it must describe how to withdraw, with comparable ease. After withdrawal the fiduciary must, within a reasonable time, stop processing and cause its processors to stop (Section 6(6)). The Act gives no number for "reasonable". Pick an internal target you can meet and measure, and write it down.

What does comparable ease mean in practice?

Compare the effort, channel by channel. If a person gave consent with one tap in the app, withdrawal should also be one place in the app, not an email to a data protection officer.

Where consent was givenMinimum comparable withdrawal
Web form or app screenMinimum comparable withdrawal: A preference page or toggle in the same account, reachable without contacting support
WhatsApp or SMS opt-inMinimum comparable withdrawal: A reply keyword, plus the preference page
Call centre or branchMinimum comparable withdrawal: The same channel, with an agent who can log the event, plus a self-service option
Consent ManagerMinimum comparable withdrawal: Withdrawal through the Consent Manager arrives as an event with a `source_ref`, and your own channels still work

What does a withdrawal event trigger?

A `withdrawn` row is the start of work, not the end. It should create these things:

  • A state change. `consent_state` for that person and purpose moves to withdrawn, at the `occurred_at` time. Section 6(5) says earlier processing stays lawful, so the exact time matters.
  • Delivery records. One row per system and processor that serves the purpose: `withdrawal_event_id`, target, instruction sent time, acknowledgement time, status and evidence. A row with no acknowledgement after your target is an open gap.
  • A scope check. Withdrawal is per purpose. If someone withdraws marketing consent, their account should keep working. If they withdraw consent for the core service, Section 6(5) lets you stop providing it, but not the processing needed to finish an order already paid for.
  • An erasure decision. Section 8(7) asks you to erase personal data on withdrawal unless a law requires you to keep it. Hand the event to your deletion jobs, as described in our erasure automation post. Record which data was kept and under which law.

The delivery table turns "we stopped" into evidence. Processors need an instruction and a written confirmation. Section 8(1) keeps you responsible for what they do for you.

Children. Under the Act a child is anyone under 18, and verifiable consent from a parent or guardian is needed before any processing (Section 9(1)). Rule 10 requires you to check, with due diligence, that the parent is an identifiable adult. Log `consenting_party` as the parent, link the child's `person_key`, and store only a reference to how the check was done and its outcome, not the ID document. The full flow is in our verifiable parental consent guide.

Consent Managers. The Act lets a person give, manage, review or withdraw consent through a Consent Manager (Section 6(7)). Nothing requires you to use one. As of 20 November 2026 the Board's register page showed "Total registered: 0", so no events can arrive yet. Build the `source_ref` field now and verify any Registration ID against the Board's register before trusting events. See our tracker.

The Act and Rules set no fixed period for a Data Fiduciary's consent records. The seven-year figure you may have seen belongs to Consent Managers, who must keep their records for at least seven years (First Schedule, Part B). It is a useful benchmark, not your rule. Your own period should cover as long as you might need to prove consent under Section 6(10). It should be no shorter than the one year in Rule 8(3), which applies to personal data, traffic data and logs of processing. Counsel can then add any longer period that sector law or your risk view needs.

RecordSuggested retention approach
Consent events, withdrawal events and delivery recordsSuggested retention approach: Keep while the processing continues, and for a defined proof period after it ends. Set the period with counsel. Never less than one year
Purpose and notice registersSuggested retention approach: Keep for as long as any consent event points at a version
Evidence artefacts (call recordings, scanned forms)Suggested retention approach: Shorter than events. They are personal data in their own right. Keep a hash and an ID in the event
Consent service access logsSuggested retention approach: At least one year for security monitoring (Rule 6(1)(e)), then erase

Plan for the conflict between erasure and proof. When a person's data is erased, you still may need to prove that you held a valid consent. A workable pattern is to erase contact details and profile data, and keep the event rows under the pseudonymous `person_key`. The Rules do not spell out this case, so agree the pattern with counsel and write it into your retention schedule. If you fall in a Third Schedule class and erase after inactivity, apply the same pattern.

Section 5(2) covers consent given before the Act's commencement. You must give the person a notice as soon as reasonably practicable, with the data, the purpose, how to exercise rights and how to complain. You may continue processing until she withdraws. Counsel confirms which of your records fall under it.

In the log, import these as `legacy_import` events. Record what you do know: the person, the purpose, the date if known, and the source system. Leave `notice_id` empty and mark the evidence quality as unknown. Then log the Section 5(2) notice as its own event when you send it. Do not backfill invented evidence. For marketing consent in particular, see our post on WhatsApp and retargeting consent.

Before 13 May 2027, and then each quarter, pick ten people at random and produce one export for each that answers the questions in the first table.

  • Which notice version did they see, and what did its text say, in which language?
  • Which purposes did they grant or deny, and what exactly did they do on screen or on the call?
  • Does the hash chain verify end to end?
  • For anyone who withdrew, can you show the time, each system's stop confirmation and the erasure outcome?
  • How long did it take from export request to export? If the answer is days, the log is not ready.

If you want an outside check of your consent service against this schema, a DPDP gap assessment covers consent records among the other duties. Mono does not certify compliance. We show you what the log does and does not prove.

Sources: Digital Personal Data Protection Act, 2023, Sections 5, 6, 7, 8 and 9 (meity.gov.in). Digital Personal Data Protection Rules, 2025, Rules 3, 6, 8 and 10, and First Schedule Part B (dpbi.gov.in). Data Protection Board of India, Registered Consent Managers page (dpbi.gov.in/registered-consent-managers), checked 20 November 2026. Last reviewed 20 November 2026.

FAQ

What should a DPDP consent log contain?

Each event should hold a pseudonymous person key, the purpose and its version, the action (granted, denied or withdrawn), the notice version with a hash of its exact text and the language shown, the time the person acted, the channel, the capture context, and a reference to any evidence. Section 6(10) of the DPDP Act makes the Data Fiduciary prove notice and consent, so the log must show both for one person.

How long must a Data Fiduciary keep consent records under the DPDP Act?

The Act and Rules set no fixed period for a Data Fiduciary's consent records. Keep them long enough to prove consent under Section 6(10), and at least the one-year minimum for personal data and processing logs in Rule 8(3). The seven-year minimum in the Rules applies to registered Consent Managers, not to ordinary fiduciaries. Counsel sets the final period.

Should a consent log be editable?

No. Treat it as append-only. A withdrawal or a correction is a new event that points at the earlier one. Restrict the application role to inserts, chain row hashes so edits are detectable, and rebuild the current-state table from the events if it is ever wrong. This protects the log as evidence.

How do you record consent withdrawal under the DPDP Act?

Write a withdrawn event for the person and purpose with the exact time, then update the current-state table and create a delivery record for every system and processor that serves the purpose. Each one must confirm it has stopped. Section 6(4) requires withdrawal to be about as easy as giving consent, and Section 6(6) requires processing to stop within a reasonable time.

Do you need a consent log if you rely on legitimate uses under Section 7?

You do not need a consent event for processing that rests on a Section 7 legitimate use, but you should record that basis in your purpose register. Where you use consent for some purposes and a legitimate use for others, keep them apart so the log shows exactly which processing depends on consent.

Check whether your consent log could prove notice and consent.