Skip to main content
DPDP-AID Readiness Checkby

Data principal rights, and how to serve them

Rights are the part of the DPDP regime a business will feel operationally, because each one is a request that arrives with a clock attached. The Act creates four. None of them can be served by a policy document alone.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

The four rights

Each right needs a route people can find, an owner who answers, and a record of what was done.

  • Access: a summary of the personal data being processed and of the processing activities, plus the other information prescribed.
  • Correction and erasure: correction, completion, updating, and erasure where the law does not require retention.
  • Grievance redressal: a readily available means of complaining to the fiduciary, answered within a published period.
  • Nomination: the ability to nominate someone to exercise the rights in the event of death or incapacity.

What we assess: Rights of data principals

  • A working process for access requests
  • A working process for correction, completion, updating and erasure
  • Grievance redressal with a published response time within the prescribed limit
  • People can nominate someone to act for them
  • Requesters' identity is verified before acting
  • Every request is tracked with an owner and timestamps
  • Requests from persons with disability and lawful guardians are supported

More on rights of data principals

What serving them actually takes

A right to erasure is a data discovery problem before it is a legal one. If personal data sits in a warehouse, a CRM, three spreadsheets and a vendor's system, then an erasure request touches all five, and the answer has to be true for all five.

The Rules also expect you to publish how to make a request, including the identifiers a person should give so you can find their records, and to publish the period within which you answer grievances. A published period you regularly miss is worse than no published period, so choose one you can meet.

  • Publish the request route and the identifiers needed, on the website and in the app.
  • Verify the requester without collecting more personal data than verification needs.
  • Fan the request out to processors, and get confirmation back from them.
  • Log the request, the decision, the date and the outcome. That log is your evidence.
  • Track your own response times against the period you published.

Nomination, the one people forget

Nomination lets a data principal name someone to exercise their rights if they die or become incapable. It is easy to miss because no one asks for it until they need it, and then it arrives as a distressing request handled by whoever picks up the phone. Decide now how a nominee proves their status and who approves it.

DPDP data principal rights, one by one

Each right is short in the statute and long in the building. Here is what each one asks of a business in practice, and the failure mode we see most often.

  • Access: a person can ask for a summary of the personal data you hold about them and of what you are doing with it. The failure mode is answering only from your main database and forgetting the warehouse, the CRM and the support tool.
  • Correction and erasure: they can ask you to correct, complete, update or erase. The right to erasure under DPDP is a data discovery problem first, because the answer has to be true everywhere, including at your processors.
  • Grievance redressal: they can complain to you, and you must answer within a period you publish. The failure mode is publishing an ambitious period and missing it, which is worse than publishing a realistic one.
  • Nomination: they can nominate someone to exercise their rights if they die or become incapable. The failure mode is having no process at all, so a distressing request is handled by whoever picks up the phone.

Turning a DPDP access request into a repeatable process

The first request is a project. The fiftieth should be a process. What makes the difference is deciding in advance where you will look, how you will verify the person, and who signs off the answer.

Publish how to make a request, including the identifiers a person should give so you can find their records without collecting more personal data than verification needs. Then log every request, the decision, the date and the outcome. That log is the only evidence you will have later that you answered in time.

  • Decide the list of systems a request must reach, and keep it with your data inventory.
  • Verify identity proportionately, without demanding documents you would not otherwise hold.
  • Fan requests out to processors, and require confirmation back within your own deadline.
  • Measure your response times against the period you published, and review them quarterly.

Designing for volume, not for the exceptional case

Teams bracing for abuse tend to over-engineer verification and under-engineer the ordinary path. In practice almost every request is genuine, arrives through the route you published, and needs a fast, unremarkable answer.

Build for that. Assume good faith, make the common case cheap to serve, and keep the genuinely exceptional case for your legal adviser rather than designing the whole process around it.

Frequently asked questions

What rights does a data principal have under the DPDP Act?

The right to access a summary of their personal data and the processing activities, the right to correction, completion, updating and erasure, the right to grievance redressal, and the right to nominate another person to exercise their rights in the event of death or incapacity.

How long does a business have to answer a DPDP rights request?

The Rules require a data fiduciary to publish the period within which it responds to grievances and to meet it. Publish a period you can consistently achieve, and measure yourself against it.

Does the right to erasure override record keeping laws?

No. Personal data that must be kept for a legal purpose can be retained, but the rest should be erased, including at processors. Record the legal basis for anything you keep.

Do I have to honour a rights request from someone outside India?

The Act creates rights for data principals in relation to personal data processed under it. Where other laws also apply to the same person, honour the stricter requirement, and take advice on cross-border cases.

What are the data principal rights under the DPDP Act?

Four: access to a summary of your personal data and its processing, correction and erasure, grievance redressal, and the right to nominate someone to exercise your rights if you die or become incapable.

How quickly must a business answer a DPDP access request?

The Rules require a data fiduciary to publish the period within which it responds to grievances and to meet it. Publish a period you can consistently achieve and measure yourself against it.

Can a person ask me to delete data I am required by law to keep?

They can ask. Where another law requires retention, you keep it and say so. The rest should be erased, including at processors. Record which legal basis covers anything you retain.

See your readiness in five minutes.

Start with the quick check. You can move to the full assessment at any time without losing your answers.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.