Your Challenge Our Progress

Jamtech Logo ×

How to Keep DPDP Consent Records That Hold Up in a Dispute

A DPDP consent record shows who agreed, to what, under which notice and when, with any withdrawal, because Section 6(10) makes the business prove it.

Ajay Shukla
By Ajay Shukla
Sample DPDP consent record showing person, purpose, notice version, timestamp and withdrawal status

What does a DPDP consent record need to prove?

It needs to prove two things: that a notice was given, and that the person agreed in the way the Act requires. Every other field in the record exists to support one of those two claims.

What does Section 6(10) of the DPDP Act say about proof?

Section 6(10) of the Digital Personal Data Protection Act, 2023 (the DPDP Act) says that when consent is the basis for processing and a question arises in a proceeding, the Data Fiduciary must prove that a notice was given and that consent was given in line with the Act and the Rules. A Data Fiduciary is the organisation that decides why and how personal data is processed. The burden sits with that organisation, not with the person who clicked.

Section 6(10) is part of the main duties that start on 13 May 2027, the date the Ministry of Electronics and Information Technology (MeitY) gave on 14 November 2026, reported by ANI. The Act does not prescribe a schema or a file format. That leaves the design to you, which also means you have to be able to justify it.

What does Rule 3 add to the notice?

The Digital Personal Data Protection Rules, 2025 (the DPDP Rules) fill in the notice. Rule 3 asks for a notice that can be understood on its own, with an itemised description of the personal data, the specific purpose, and the goods, services or uses the processing enables. It must also say how to withdraw consent, exercise rights and complain to the Data Protection Board of India. A line such as "we may collect details about you" will not pass as an itemised description.

The practical result is that a consent record has to point to the exact notice text. If you edit the notice and keep only the current version, you can no longer show what an earlier user saw.

What fields should a DPDP consent record store?

Seven fields cover the two claims. Store them as one row per event, not one row per user.

Field

What it holds

Why it matters

Person

A stable pseudonymous ID for the Data Principal

Ties the record to one individual without copying their name or phone number

Purpose

One specific purpose, such as order updates or product emails

The Act asks for specific consent, so a bundled purpose breaks the record

Notice version

The ID of the exact notice text shown

Proves what the person was told

Action

Granted, declined or withdrawn

Shows the clear affirmative action, or its reversal

Time

A server timestamp in one time zone

Puts events in order and supports a timeline

Channel

Web form, app, call centre, paper form later digitised, or a consent manager

Shows where and how the choice was made

Evidence

The form or screen version and a reference to the request that carried it

Lets you reproduce what was on screen

A Data Principal is the individual the personal data is about. That person may also give a choice through a registered consent manager. The Board began accepting registrations on 13 November 2026, so add it as an allowed channel value now and avoid changing the schema later.

Why store the notice version and not just the notice text?

Copying the full text into every row wastes space and invites drift. Give each notice an ID, store the text once in a notice table, and put only the ID in the consent row. Changing a notice then means adding a new version with its own ID, never overwriting an old one.

The cost is a second table and a rule that nobody edits a published version. The benefit is that a row from last year still points to the exact words the person saw.

How should you log a withdrawal of consent?

Add a new row with the action set to withdrawn, for the same person and purpose, with a new timestamp. Do not edit the original grant. Section 6(4) requires withdrawal to be as easy as giving consent, so the log has to capture withdrawals from every channel where consent could be given.

Then act on it. Under Section 6(6), once consent is withdrawn the Data Fiduciary must stop processing within a reasonable time and make its Data Processors stop too, unless a law requires or allows the processing. A Data Processor is a company that handles data on your behalf, such as an email service or a cloud host. Use workflow automation to send the stop instruction to each processor, and log when each one received it. That is the part a dispute is most likely to test.

What should happen to the record after withdrawal?

Keep it. The grant and the withdrawal together are the evidence that processing between them was allowed, and Section 6(5) says withdrawal does not affect the lawfulness of processing done before it. Deleting the record deletes your proof.

The personal data itself is a separate matter and follows its own erasure rules. Keep the consent history apart from the profile data it describes, and store a pseudonymous ID in the log, so that the log holds as little personal data as possible.

Can you keep consent as a single true or false flag?

No, because a single flag cannot answer the questions a dispute will ask. It says what the answer is today. It cannot say what the person saw, when they agreed or whether they changed their mind in between. A withdrawal that overwrites the flag also destroys the grant.

You can keep the flag if your application needs a fast lookup. Treat it as a cache that is rebuilt from the event log, never as the source of truth. Here is what one person's history looks like as events (illustrative values):

Time

Person

Purpose

Notice

Action

Channel

2027-06-02 10:14

u_8841

Product emails

v3

Granted

Web form

2027-08-19 16:40

u_8841

Product emails

v3

Withdrawn

App settings

The flag for this person now reads false. The log still shows that the grant existed, which notice it rested on and when it ended.

What should you do with consent collected before the DPDP Act?

Do not invent history for it. Mark it as legacy with a lower evidence grade, then close the gap going forward.

Section 5(2) of the Act covers consent given before the Act commenced. The Data Fiduciary must give the person a notice as soon as reasonably practicable, covering the data and purpose, how to exercise rights and how to complain to the Board. It may keep processing until the person withdraws. The Act gives no fixed date for that notice.

For old records, sorting them into three groups works well:

Group

What you still have

How to import it

A

A real timestamp and the notice text

A granted event with the true timestamp and a legacy marker

B

A real timestamp but no notice text

A granted event with the date and the notice set to "unknown, before the Act"

C

Only a true or false flag

A legacy entry with no date and the evidence field marked "none"

Never backfill a timestamp or a notice ID you do not have. A made-up value is worse than a gap, because it looks like proof and fails the first time someone asks where it came from.

Send the Section 5(2) notice to groups B and C first, and log the sending as an event with its notice version. From then on, new records carry their own evidence. Whether a given set of old data can still be used depends on the lawful ground it was collected under, so ask counsel before relying on any of it.

How long should DPDP consent records be kept?

We did not find a fixed retention period for consent records in Section 6 or in Rules 3 and 6, so agree a period with counsel and write it down. Some vendor guides quote seven years. Treat a figure like that as the vendor's own policy until you can point to the legal source.

Rule 6 does give one number for a different record. It asks for logs of access to personal data, and for those logs and the related personal data to be kept for one year, unless another law requires otherwise. Access logs and consent records are different things. The first show who touched the data. The second show why you were allowed to hold it. Keep both, and make sure one retention job cannot delete the other.

How do you test that your consent records hold up?

Run a dispute drill. Pick one person and one purpose at random. Ask a colleague who did not build the system to play the complainant: "I never agreed to product emails." Then see how long it takes to produce five things:

  1. The notice text that person saw, by version.

  2. The action they took and the time.

  3. The channel it came through.

  4. Any withdrawal that followed.

  5. The date each Data Processor was told to stop.

Anything you cannot produce is a gap to fix. Typical gaps are a missing notice version and a withdrawal that never reached the email tool. A first drill will probably find at least one of them, and finding it now costs far less than finding it in front of the Data Protection Board.

What should an Indian business do before 13 May 2027?

Work through the steps in this order:

  1. Write one itemised notice per purpose and give each a version ID.

  2. Create the notice table and the event log with the seven fields above.

  3. Import old consent into groups A, B and C, without inventing evidence.

  4. Send the Section 5(2) notice to everyone whose record is weak.

  5. Build the withdrawal path so it reaches every processor and logs the time.

  6. Run the dispute drill and fix what it finds.

  7. Ask a lawyer to review the notices, the retention periods and the legal grounds for old data.

Teams without in-house capacity for the event log and the processor notifications often bring in back-end developers. The legal review in the last step stays with counsel either way.

Rules and technical specifications can change, so check dpbi.gov.in before you act. This article is general information and not legal advice.

Frequently asked questions

Q1. What is a DPDP consent record?

A DPDP consent record is the stored evidence that a specific person agreed to a specific use of their data. It shows the purpose, the notice version they saw, their action, the time, the channel and any later withdrawal. It exists because Section 6(10) makes the Data Fiduciary prove notice and consent if either is questioned.

Q2. What fields should a consent record have under the DPDP Act?

Store the person's pseudonymous ID, the purpose, the notice version, the action, a timestamp, the channel and a reference to the evidence. The Act does not list required fields, so these seven are a design choice that covers the two things you must prove: that a notice was given and that valid consent followed.

Q3. Does the DPDP Act require me to keep consent records?

The Act does not use the phrase, but Section 6(10) obliges the Data Fiduciary to prove notice and consent when questioned. In practice that means keeping records that can show both. Without them, you carry the burden of proof with nothing to produce. The main duties start on 13 May 2027.

Q4. Who has the burden of proving consent under the DPDP Act?

The Data Fiduciary does. Section 6(10) says that where a question arises in a proceeding, the organisation must prove that a notice was given and that consent was given in line with the Act and the Rules. The person who clicked the checkbox does not have to prove anything.

Q5. How long do I need to keep consent records under the DPDP Act?

We did not find a fixed period for consent records in Section 6 or Rules 3 and 6, so agree one with counsel and document it. Rule 6 separately asks for access logs and related personal data to be kept for one year, unless another law requires otherwise. Treat vendor claims of seven years as policy, not law.

Q6. Should I delete the consent record when a user withdraws consent?

No, keep it. The grant and the withdrawal together show that processing in between was allowed, and Section 6(5) says withdrawal does not affect the lawfulness of earlier processing. Delete or erase the personal data as the rules require, but keep the consent history, with only a pseudonymous ID in it.

Q7. Can I store DPDP consent as a true or false value?

A true or false value alone is not enough. It shows today's answer but not the notice version, the time or the earlier history, and a withdrawal that overwrites it destroys the grant. Keep an event log as the source of truth and use the flag only as a fast-lookup copy built from that log.

Q8. What is a notice version and why does it matter?

A notice version is an ID attached to one exact piece of notice text. It matters because Rule 3 requires an itemised notice and Section 6(10) requires you to prove it was given. If you edit a notice in place, you lose the ability to show what earlier users saw, so add a new version instead.

Q9. How do I record consent given by phone or on a paper form?

Record it as an event with the channel set to call centre or paper form, the time, the purpose and the notice version used. Add a reference to the call record or the scanned form as evidence. The Act covers data collected offline and digitised later, so these channels need the same fields as a web form.

Q10. What should I do with consent collected before the DPDP Act?

Import it as legacy, without inventing details. Section 5(2) requires a notice as soon as reasonably practicable and allows processing to continue until the person withdraws. Record real timestamps where you have them, mark missing evidence as none, and log the date you send the notice. Ask counsel about the legal ground for the old data.

Q11. When do the consent record requirements start?

The main duties, including Section 6(10), start on 13 May 2027, according to MeitY's statement of 14 November 2026. Consent manager registration began earlier, on 13 November 2026. Building the log now leaves time to import old data, send the legacy notice and run a dispute drill before the date.

Q12. Do I have to tell my data processors when a user withdraws consent?

Yes. Section 6(6) says that after withdrawal the Data Fiduciary must stop processing within a reasonable time and cause its Data Processors to stop too, unless a law requires or allows the processing. Log the date each processor received the instruction, because that is where disputes tend to focus.

Q13. Is an append-only consent log required by law?

No, the Act does not prescribe a schema or a storage method. An append-only log is a design choice that makes Section 6(10) easier to meet, because each change is a new row and nothing is overwritten. Whatever you choose, you must be able to show the notice and the consent when asked.

Q14. Can a consent manager keep my consent records for me?

A registered consent manager can pass a person's choices to you, but Section 6(10) still places the burden of proof on the Data Fiduciary. Keep your own copy of every choice that arrives, with the channel set to consent manager, so you can answer a complaint without depending on a third party.

Ready to grow your business with Jamtech?

Talk to our experts about your next digital project.

Get Free Consultation
Published on Nov 17, 2026 Updated on Nov 17, 2026
Chat on WhatsApp