[Analysis] ROPA (Record of Processing Activities) under the DPDP Act – Data Mapping | Controller and Processor Records | Is It Mandatory?

  • Blog|Company Law|
  • 9 Min Read

ROPA, the record of processing activities: how data mapping feeds it, the fields in controller and processor records, how often to review it, and why India has no ROPA duty but still needs the record.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
ROPA stands for Record of Processing Activities: a structured record of each processing activity, showing what personal data an organisation handles, why, on what legal ground, who receives it, where it goes, how long it is kept and how it is secured. The EU General Data Protection Regulation (GDPR), Brazil’s LGPD and Saudi Arabia’s PDPL require one. The Digital Personal Data Protection Act, 2023 (DPDP Act) does not, for any organisation of any size. In India the record is a practical necessity rather than a legal requirement.

Table of Contents

  1. What is a ROPA?
  2. Is a record of processing activities mandatory under the DPDP Act?
  3. How does data mapping feed the record?
  4. What should a controller’s record contain?
  5. How is a processor’s record different?
  6. How often should a ROPA be reviewed?
  7. Is there relief for smaller organisations?
  8. Quick answers

1. What is a ROPA?

A ROPA is a structured document in which an organisation records, activity by activity, the essential facts about how it handles personal data: the purpose, the legal ground, the categories of individuals and data involved, the third parties and processors who receive the data, the countries it is transferred to, how long it is kept and how it is secured. Abha Tiwari and Aditya Singhania describe it as the organisation’s formal account of its data processing, in a form that can be produced to a supervisory authority and that shows the organisation knows what it is doing with personal data and why.

A ROPA does not write itself. It depends on data mapping, the discovery phase in which the organisation asks what personal data it holds, where it came from, what it does with it, who else touches it and for how long. Every data flow found during mapping becomes an entry in the ROPA. Each field of the record, such as the lawful basis, the categories of data subjects, the retention period, the processors and the transfer mechanisms, can be completed accurately only if the mapping went deep enough.

The record also disciplines the mapping. Its format forces the organisation to ask whether each processing activity has a documented purpose, a legitimate legal ground and a defined end-point.

2. Is a record of processing activities mandatory under the DPDP Act?

No. The DPDP Act contains no equivalent of Article 30 of the GDPR, and there is no record of processing activities obligation for any organisation of any size.

The record is still a practical necessity. Section 8(1) of the DPDP Act makes the Data Fiduciary responsible for compliance irrespective of any agreement to the contrary. Rule 6 of the Digital Personal Data Protection Rules, 2025 (DPDP Rules) requires logs to be maintained and reviewed, and both apply from 13 May 2027. An organisation that cannot show what it holds and why will struggle to demonstrate compliance with anything else.

Elsewhere the obligation is express:

  • Article 30 of the GDPR, read with the accountability principle in Article 5(2) and Article 24(1), requires controllers and processors to keep their own records independently.
  • Article 37 of Brazil’s LGPD requires controllers and operators (processors) to keep records of their processing operations, with particular weight on processing based on legitimate interest.
  • In Saudi Arabia, Article 31 of the Personal Data Protection Law requires a controller to keep records, and Article 33 of the Implementing Regulation prescribes their contents. The records must be kept for the duration of the processing and for five years after it is completed, and produced to the competent authority on request.

In those frameworks, a supervisory authority opening an investigation typically asks for the ROPA as one of its first steps, and an absent, incomplete or out-of-date record signals a systemic compliance failure.

3. How does data mapping feed the record?

The data map comes first, and the record is built from it. In the book’s staged approach to a privacy programme, building the data map is stage three, after appointing someone accountable for privacy and working out which laws apply.

The map is an inventory of every category of personal data the organisation touches. It identifies the sources of the data, whether the individual, third parties, digital interfaces, or passive collection through cookies and tracking technologies; the departments that receive and use it; the systems in which it resides; and the third parties to whom it flows. The authors advise building it through structured interviews with process owners rather than desk research, because the gap between documented practice and actual practice is where most compliance failures live.

Stage five traces the data in both directions:

  • Inward flows include every point of ingestion: employee onboarding, customer acquisition, vendor onboarding, digital form submissions, behavioural tracking, and data received from group entities or data brokers.
  • Outward flows include every disclosure to a processor, every transfer to an independent or joint controller and every cross-border transmission, each of which must be identified and legally grounded.
  • The exercise extends to cloud providers, payroll processors, analytics vendors, legal advisers and any sub-processors engaged by primary vendors, for whom the organisation remains accountable even without a direct contract.

Later work rests on this foundation. A retention schedule built on a partial map will have gaps, and a privacy notice drafted before the processing record exists will describe activities the organisation has not yet verified.

Taxmann’s Advisory & Research | Use our Legacy for your Advantage

4. What should a controller’s record contain?

The book’s template for a controller, Table A, has 28 fields. It combines fields drawn from the GDPR, the LGPD and the Saudi PDPL, so that an organisation operating under all three can keep one record instead of three, and a final column shows where each field comes from, since a field prescribed in one regime may be no more than good practice in another. The authors present the template as drafting guidance, not legal advice. An organisation subject to only one of these laws may not need every field, but the authors suggest taking advice before removing any.

Grouped by theme, the 28 fields cover the following.

Theme Fields in Table A
The record and the organisation Record reference with review dates; organisation; role as controller, noting any joint controller; local representative; data protection officer
The activity Business function; activity name; a plain description from start to finish; purpose, with one row per purpose; lawful basis; legitimate interest assessment
The people and the data Categories of data subject; categories of personal data; sensitive data; children’s data; source
Who receives the data Recipients; processors engaged, with contract reference and date; cross-border transfers with the mechanism or safeguard relied on
Keeping and protecting it Retention period, or the criteria used to set it, and the event that starts the clock; disposal by deletion or anonymisation; security measures
Risk and ownership Automated decisions; impact assessment; systems and location; approximate volume; risk rating; accountable owner

Where the record is required, it becomes the reference point for deciding which activities need a data protection impact assessment or a legitimate interest assessment, for responding to data subject rights requests, for managing breach notifications within the prescribed time, and for auditing processor and vendor relationships.

5. How is a processor’s record different?

A processor’s record is shorter because the processor decides less. It need not record the purposes of the processing, the categories of data subject or the retention period, because it determines none of them: it records what it does, while the controller records why. Both records carry cross-border transfers and a general description of security measures.

The processor template, Table B, has 12 fields: record reference; organisation; local representative; data protection officer; each controller served; categories of processing for each controller; the contract reference for each engagement; sub-processors, with whether the controller has authorised each appointment; cross-border transfers; security measures; systems and location; and an accountable owner. A security description may be common across clients, but the entries for each controller served and the processing done for it must be specific to each engagement.

Two practical points follow:

  • One organisation can act in both capacities. A SaaS company is a processor for its customers’ data and a controller for its own employees, prospects and marketing contacts, so it needs two records, and the most common failure is keeping only the controller record. Working out which role applies to each activity under the DPDP Act is covered in Data Fiduciary, Data Processor or both.
  • Because the processor’s record lists every controller it serves, it works as a client register. If no controller can be identified for a dataset the processor holds, the processor is very likely acting as a controller for it.

6. How often should a ROPA be reviewed?

At least once a year, and whenever a new system, vendor, purpose or transfer is introduced. The record is worth keeping only if it is kept current.

The template comes with a few working rules:

  • Complete one row per processing activity, not one per system and not one per department.
  • Treat a processing activity as a coherent set of operations carried out for a common purpose, such as payroll administration or customer complaint handling.
  • Where one activity serves several purposes resting on different grounds, split it into separate rows, and resist recording at too high a level.
  • Assign a named owner to every activity, and record the review dates on the face of the document, because being able to show when the record was last checked is itself evidence of accountability.

An effective ROPA is complete, accurate, granular and treated as a living document, reviewed whenever a processing activity is introduced or changed, a processor relationship is added or ended, or a legal basis changes.

7. Is there relief for smaller organisations?

Under the GDPR there is, though it is narrow; under the DPDP Act the question does not arise in the same form, because there is no record-keeping duty to relieve.

Article 30(5) of the GDPR relieves an organisation employing fewer than 250 persons of the record-keeping duty. The relief falls away if any one of three conditions is met: the processing is likely to result in a risk to the rights and freedoms of data subjects; the processing is not occasional; or it includes special categories of data or data relating to criminal convictions and offences. Routine processing is by definition not occasional, so the practical result is that a small organisation keeps records covering less than the whole of its processing, not none.

What the DPDP Act offers instead is section 17(3). It allows the Central Government, having regard to the volume and nature of personal data processed, to notify Data Fiduciaries or classes of Data Fiduciaries, including startups, to whom section 5, sub-sections (3) and (7) of section 8, and sections 10 and 11 shall not apply. That would remove the notice obligation, the duty to make reasonable efforts to keep personal data complete, accurate and consistent, the erasure obligation, the additional obligations of Significant Data Fiduciaries and the Data Principal’s right of access. A startup for this purpose is a private limited company, partnership firm or limited liability partnership incorporated in India and recognised as such, in practice by the DPIIT.

The European model relieves organisations of an internal documentation duty; the Indian model would relieve them of substantive obligations owed to individuals. The authors add that the relief is discretionary and prospective: it depends on a notification that had not, so far as was publicly known, been made, so no organisation could rely on it when the book stated the law.

8. Quick answers

What is the full form of ROPA?

ROPA stands for Record of Processing Activities. It is a structured record, kept activity by activity, of what personal data an organisation processes, why, on what legal ground, who receives it, where it is transferred, how long it is kept and how it is secured.

Is a ROPA mandatory under the DPDP Act?

No. The DPDP Act contains no equivalent of Article 30 of the GDPR and no record of processing activities obligation for any organisation of any size. Records remain a practical necessity, because section 8(1) makes the Data Fiduciary responsible for compliance and Rule 6 of the DPDP Rules requires logs to be maintained and reviewed.

What is the difference between data mapping and a ROPA?

Data mapping is the discovery phase that finds what personal data an organisation holds, where it came from, what is done with it, who else touches it and for how long. The ROPA is the structured record built from that map, with each data flow becoming an entry.

What does a processor’s ROPA leave out?

A processor need not record the purposes of the processing, the categories of data subject or the retention period, because it determines none of them. It must still record each controller it serves, what it does for each, and its transfers and security measures.

How often should a ROPA be reviewed?

At least once a year, and whenever a new system, vendor, purpose or transfer is introduced. Recording the review dates on the document is itself evidence of accountability.

Does the GDPR exempt small organisations from keeping a ROPA?

Article 30(5) relieves organisations with fewer than 250 employees, but the relief falls away if the processing is likely to result in a risk to individuals, is not occasional, or includes special category or criminal conviction data. Since routine processing is not occasional, most organisations still keep records for part of their processing.

Can a startup be exempted from DPDP obligations?

Section 17(3) of the DPDP Act allows the Central Government to notify Data Fiduciaries, including startups, to whom section 5, sections 8(3) and 8(7), and sections 10 and 11 shall not apply. The exemption depends on such a notification being made.


Paragraph 2.12 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania explains the record of processing activities through the GDPR, Brazil’s LGPD and Saudi Arabia’s PDPL, gives a 28-field template for controllers (Table A) and a 12-field template for processors (Table B), and sets the Indian position against the GDPR’s relief for smaller organisations. Paragraph 2.11 places the data map and the tracing of data flows within a staged privacy programme.
Taxmann Advisory offers research support from a team of researchers who find the material a question needs, and implementation support that includes putting compliance SOPs in place.
Taxmann.com | Research carries the Digital Personal Data Protection Act, 2023 section by section under Indian Acts & Rules, and Taxmann.com | Store has the Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes.
Related reading: obligations of Data Fiduciaries · the DPDP Act compliance checklist · the DPDP Act and startups and SMEs · the DPDP Act and the GDPR compared.
More in this series: the SPDI Rules and the DPDP Act · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.
Law stated as updated till October 2026.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied