Guide
Building a personal data inventory that stays current
The Act does not ask for an inventory by name, yet most of its duties depend on one. A method for building it and keeping it honest about what is still unknown.
Nothing in the Act says “keep an inventory of personal data”. Yet an organisation that does not have one will struggle with almost every duty the Act does set. This guide explains why, and describes a method for building an inventory and keeping it honest.
Why the Act's duties depend on one
- A notice has to give an itemised description of the personal data and the specified purpose (Rule 3). You cannot itemise what you have not listed.
- A Data Principal can ask for a summary of her personal data and the identities of the Data Fiduciaries and Data Processors it has been shared with (Section 11).
- Personal data has to be erased when the purpose is no longer served, and processors have to be caused to erase it (Section 8(7)).
- After a breach, each affected Data Principal has to be told (Section 8(6)). That requires knowing whose data was in the affected system.
- Security safeguards have to cover personal data in your possession or under your control, including at processors (Section 8(5)).
What to record for each dataset
The Act does not prescribe these fields. They are the ones we have found a record needs if it is to answer the questions above:
| Field | Why it is needed |
|---|---|
| Dataset and system | Where the data is, in terms someone can act on. |
| Data category and personal data types | What a notice has to itemise. |
| Owner | Who answers for it and reviews it. |
| Purpose and processing basis | Whether it rests on consent or a certain legitimate use. |
| Storage location and country | Whether a transfer outside India is involved. |
| Processor | Who else holds it and has to be instructed. |
| Retention period | When it should be erased. |
| Classification | Whether it includes children's data or other data needing more care. |
| Review date | When the entry was last confirmed. |
A method that finds most of it
No single route finds everything. Use three and compare the results:
- From systems. List the applications, databases and file stores you run or subscribe to, and ask what personal data each holds.
- From processes. Walk through how a customer is acquired, served and billed, and how an employee is hired and paid. Note every point where data is collected or passed on.
- From suppliers. Go through contracts and invoices. Any supplier that handles personal data for you is a processor that belongs in the record.
Be honest about what is unknown
An inventory that looks complete is more dangerous than one that admits its gaps. Record the systems you know exist and have not yet examined. Count the entries that have no owner, no purpose or no retention period. Those counts are the most useful measure of progress, and they tell management how far the picture can be trusted.
Keeping it current
An inventory decays from the day it is finished. Tie its upkeep to events that already happen:
- a new system or supplier is approved;
- a new purpose for existing data is proposed;
- a system is retired or a contract ends;
- the review date on an entry is reached.
In ControlMap
The Data Inventory module holds this register, and Data Discovery reports how much of it is still incomplete. Flows between systems and to processors are recorded in Data Mapping.
Related reading
DPDP readiness: a starter checklist
Thirty questions, grouped by theme, to establish where an organisation stands before detailed assessment begins.
Data Fiduciary or Data Processor: who carries which duty
The Act places its obligations on the Data Fiduciary, including for work done by its processors. A practical look at what that means on each side of the contract.
Notice and consent under Sections 5 and 6
What a notice has to contain under Rule 3, what makes consent valid under Section 6, and the records that let you show both.