On 13 May 2027, any customer of your organisation can make a request under Section 11 of the Digital Personal Data Protection Act, 2023. She can ask what personal data you process about her. She can also ask for the identity of every other Data Fiduciary and Data Processor you have shared it with. Your team then has to answer completely, for every system and every vendor.

The document that makes such an answer possible has a familiar name in Europe. Article 30 of the GDPR calls it a record of processing activities, usually shortened to RoPA. It must be kept in writing. The DPDP Act never uses the term, and some legal teams read that silence as permission to skip it.

That reading fails in practice. At least five duties in the Act and the DPDP Rules, 2025 depend on one thing. You must already know, purpose by purpose, what you hold, where it sits and who receives it. This article walks through those duties, what an Indian register needs to contain, and how to keep it accurate once it exists.

Where the law stands, and why the word is missing

The Rules were notified on 13 November 2025 as G.S.R. 846(E). Most duties on Data Fiduciaries apply eighteen months later, from 13 May 2027. That leaves a little over six months from today. Our earlier piece on working back from 13 May 2027 sets out the sequence.

The Act describes duties rather than documents. It tells you to give notice, prove consent, answer access requests and erase on time. It rarely says which record to keep while doing so. Section 8(4) comes closest. It requires a Data Fiduciary to "implement appropriate technical and organisational measures" for effective observance of the Act and the Rules.

A register of processing is the most basic of those organisational measures. Call it a RoPA, a data inventory or a processing register. The name matters far less than whether it is complete and current. The belief that it is optional belongs with other common DPDP claims that turn out to be wrong.

Five duties that fail without a register

Each of the duties below sounds manageable on its own. Each also assumes a list that most organisations have never written down. Read together, they describe the register the Act takes for granted.

Answering an access request

Section 11(1)(a) gives the Data Principal a right to a summary of the personal data being processed and the processing activities. Section 11(1)(b) goes further. It requires "the identities of all other Data Fiduciaries and Data Processors with whom the personal data has been shared". It also asks for a description of what each one received.

Consider a stockbroker. A complete answer names the KYC agency, the exchange, the depository, the SMS gateway, the analytics tool and the cloud host. "We share with trusted partners" does not meet the text. Without a list of recipients per purpose, someone rebuilds the answer by email, one request at a time. A data principal rights portal can only show what the register already knows.

Section 6(10) places the burden on the Data Fiduciary. If consent is questioned in a proceeding, you must prove that notice was given and consent was obtained under the Act and the Rules. The SCC Online Blog puts the shift well. Consent has become a matter of evidence. A yes or no flag in a CRM proves neither the notice nor the consent.

This is a register question at heart. Each consent record has to point at a purpose defined somewhere stable, with its data elements listed. If purposes live only in screen copy, they drift. Two years later, nobody can say what "updates" meant on a 2027 sign-up form. Consent management holds up best when it reads its purposes from the register.

Erasing purpose by purpose

Section 8(7)(a) requires erasure when the Data Principal withdraws consent. It also requires erasure "as soon as it is reasonable to assume that the specified purpose is no longer being served", whichever is earlier. The only exception is retention "necessary for compliance with any law for the time being in force".

The Act's own illustration shows how narrow that exception is. A bank must keep identity records for ten years after an account closes, because banking law requires it. That reason covers identity records. It does not reach marketing preferences, device data or app analytics about the same customer.

Erasure therefore happens field by field and purpose by purpose. A closed loan keeps its KYC and transaction records for the statutory period. The lead source, the cross-sell flags and the campaign history go. You can only make that cut if the register says which data serves which purpose, and which law keeps what.

Making processors erase

Section 8(7)(b) requires you to "cause its Data Processor to erase" any data you made available to it. Section 8(1) keeps you responsible for processing done on your behalf, "irrespective of any agreement to the contrary". A contract clause does not move the duty to the vendor.

The register is where you learn that one customer's data went to four vendors. Without it, the erase instruction reaches only the vendors someone remembers. The rest keep the data, and you remain answerable for it.

Keeping decision data accurate

Section 8(3) applies when personal data is likely to be used for a decision about the person. It also applies when the data is likely to be disclosed to another Data Fiduciary. In both cases you must ensure its "completeness, accuracy and consistency".

A lender reporting repayment history to a credit bureau is doing both at once. A wrong overdue flag that is fixed in the loan system but not in the bureau file breaks this duty. The register should mark these purposes, so a correction reaches every downstream copy.

Why a GDPR template is not enough for India

Many Indian teams already hold an Article 30 spreadsheet from a European client or parent company. It is a useful start. Article 30 asks controllers to record purposes, categories of data and recipients, among other things. Three Indian requirements need columns that template rarely has.

The legal ground. DPDP allows processing on consent or on one of the "certain legitimate uses" in Section 7. The Act has no legitimate interests ground. Each purpose in the register should carry either consent or the exact Section 7 clause relied on.

The one-year floor. Rule 8(3) requires a Data Fiduciary to retain personal data, associated traffic data and processing logs for at least one year. The rule's text counts that year from the date of processing, for the purposes in the Seventh Schedule. After that, the data and logs must be erased unless another law requires longer. Rule 6(1)(e) separately requires logs and personal data to be kept for one year, as DSCI's FAQ notes.

This floor does not license keeping everything for a year. Analysis on Mondaq cautions against a blanket one-year policy. It advises mapping retention to each data set, purpose and legal requirement. Your register therefore needs two dates per system: when use stops, and when erasure happens.

The silence period. Section 8(8) treats a purpose as no longer served when the person neither approaches you nor exercises any rights for a prescribed period. Rule 8 prescribes that period only for three large classes in the Third Schedule. Every other Data Fiduciary must set its own period per purpose, and be able to defend it. The register is where that period and its reasoning belong.

What one entry should hold

Keep the register at purpose level. Individual records live in your systems and consent store. The register tells those systems what each purpose covers and where its data goes. One entry, in our practice, looks like this.

FieldWhat it recordsDuty it serves
PurposeA plain name the customer would recognises.5, s.6
Data elementsEach field collected for that purposes.11(1)(a)
Legal groundConsent, or the Section 7 clauses.4, s.7
SystemsEvery system and store holding the datas.8(5), s.8(7)
RecipientsEach processor and fiduciary, and what it receivess.11(1)(b), s.8(7)(b)
Decision or disclosureWhether the accuracy duty appliess.8(3)
RetentionStop date, erase date, and any law keeping it longers.8(7), Rule 8(3)
OwnerA named person who approves changess.8(4)

Write purposes the way a customer would read them. "Responding to your demo request" and "sending you product updates" are two purposes with two retention periods. "Communications" is one vague purpose that nobody can erase cleanly.

Building the first version

Most first registers start with interviews. Business owners describe their processes, and someone types them into a spreadsheet. This captures purposes well. It captures locations badly, because people describe the systems they know.

Personal data also sits where nobody planned it. Think of KYC scans in shared folders, customer exports on laptops, and statements in relationship managers' mailboxes. Test databases copied from production belong on the same list. Section 8(5) covers personal data "in its possession or under its control", wherever it sits.

Run data discovery and classification across databases, file shares, mailboxes, cloud buckets and endpoints before you sign off. Then use data mapping to trace how each data set moves between systems and out to vendors.

Our practice is to build from both directions. Interviews give you purposes. Scans give you locations. Where the two disagree, the scan usually wins, and the gap between them is the finding worth fixing first.

Who owns the register

A register with no owner decays fastest. The Act does not assign one, so this is practice rather than rule. The DPO or privacy lead should own the register as a whole and approve every change.

Each column still needs its own keeper. IT owns the systems column. Procurement owns the vendor list and its contracts. Legal owns the laws cited for longer retention. Business heads own their purposes. The privacy lead's job is to make sure all of them update the same register.

Keeping it true after go-live

A register built once and filed away is out of date within a quarter. New vendors arrive, forms gain fields, and marketing adds a campaign tool. Tie updates to change control. No new system, vendor contract or data field should go live without its register entry.

The second rule matters more. Your workflows should read from the register rather than keep their own copies. The consent screen, the rights portal and the erasure job should all draw on the same purposes. When a purpose changes, each workflow sees the change at once. Separate copies drift apart and give different answers to the same question.

Rescan on a schedule as well. Regular scans of shared drives and mailboxes catch the copies that change control misses. Assessment and compliance reporting can track each open finding until someone closes it.

A one-week test for your register

Run these checks before you trust the register you have. Each takes less than a day.

TestWhat good looks like
Pick one customer and list every system and vendor holding their dataDone within a day, by purpose
Read out your purposesEach names its data elements and when it ends
Pick one purpose and name its legal groundConsent, or a specific Section 7 clause
Check your top five vendorsEach appears with the data it receives
Pick one data set you keep after exitA named law and period, or an erase date
Scan one shared driveWhat you find already appears in the register

If two or more checks fail, fix the register before you build new workflows on top of it. A DPDP gap assessment is a sensible place to start.

The record is your defence

The DPDP Act puts the burden of proof on the organisation. When a customer says "I never agreed" or "you still have my data", a policy document proves nothing. Records do. Almost every record you will need traces back to one list of purposes, data, systems and recipients.

The Act never names that list. Every duty in this article assumes you have it.

Sources

  1. MYND Integrated Solutions (DPDP Wiki), "Section 8: General obligations of Data Fiduciary" (official text reproduced), updated 9 September 2026. Link
  2. MYND Integrated Solutions (DPDP Wiki), "Section 11: Right to access information about personal data" (official text reproduced), updated 9 September 2026. Link
  3. MYND Integrated Solutions (DPDP Wiki), "Data Fiduciary obligations: a plain-English checklist", 2026. Link
  4. S.S. Rana & Co., "MeitY Notifies Final Digital Personal Data Protection Rules 2025", 14 November 2025. Link
  5. SCC Online Blog, "Consent as Governance: Understanding DPDP's Most Misread Obligation", 10 April 2026. Link
  6. Aparajitha, "Recommendations regarding Rule 8(3) of the Digital Personal Data Protection Rules, 2025", accessed 29 October 2026. Link
  7. Mondaq, "Data Retention And Deletion Under The DPDP Act: How Long Can Businesses Retain Personal Data In India", accessed 29 October 2026. Link
  8. Data Security Council of India, "FAQs on Reasonable Security Safeguards", 2025. Link
  9. GDPR-Text, "Article 30 GDPR. Records of processing activities". Link