Skip to main content
DPDP-AID Readiness Checkby

Rights of data principals

People can ask for a summary of their data, ask for correction or erasure, nominate someone to act for them, and complain. Each right needs a working process behind it, not just a policy.

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

Requirements
7
Must-do
4
Penalty ceiling
Up to ₹50 crore

Breach of any other provision. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 2 of these requirements are in the quick check.

What we assess in this area

  1. MustIn the quick checkRTS-01

    A working process for access requests

    People can ask you for a summary of their personal data that you process and the processing you do on it. They can also ask which other fiduciaries and processors you shared it with, and what was shared.

    What good looks like

    Anyone can raise an access request through a clear, published channel. A trained team finds the data across your systems, prepares a plain summary, and replies within your published time. Every reply is recorded.

    How to get there

    Publish one channel for access requests. List the systems that hold personal data. Write a short procedure and a reply template. Name an owner and test the process with a sample request.

  2. MustRTS-02

    A working process for correction, completion, updating and erasure

    People can ask you to correct inaccurate data, complete missing data and update old data. They can also ask you to erase data you no longer need for the purpose, unless the law requires you to keep it.

    What good looks like

    Requests to correct, complete, update or erase are handled through one process. Changes reach every system and processor that holds the data. Where you must keep data by law, you tell the person why.

    How to get there

    Map where each type of personal data is stored and copied. Write steps for each kind of request. Agree with processors how they will apply changes. Keep a record of each request and the action taken.

  3. MustIn the quick checkRTS-03

    Grievance redressal with a published response time within the prescribed limit

    You must give people a readily available way to raise complaints about how you handle their data. You must respond within the period set in the Rules. People should use this route before going to the Board.

    What good looks like

    A grievance channel is published on your website and app. Each complaint gets an acknowledgement, an owner and a reply within the published time, which is inside the period set in the Rules.

    How to get there

    Set up a grievance email or form. Publish it with your response time. Assign a grievance owner and a backup. Track each complaint from receipt to closure and review delays every month.

  4. ShouldRTS-04

    People can nominate someone to act for them

    People can nominate another person to exercise their rights if they die or become unable to act because of illness or incapacity. You should let them record a nominee and honour requests from that nominee.

    What good looks like

    People can add or change a nominee through a simple form. Your team can check a nominee's claim with suitable proof and then handle their requests like any other rights request.

    How to get there

    Add a nomination option to your account or request form. Decide what proof a nominee must show. Train the rights team on nominee requests. Record every nomination and change.

  5. MustRTS-05

    Requesters' identity is verified before acting

    Before you share, change or erase data on request, you should confirm that the requester is the person concerned or someone allowed to act for them. A careless reply can expose data to the wrong person.

    What good looks like

    Every rights request passes an identity check that fits the risk. Checks use data you already hold where possible. Failed or doubtful checks are escalated and recorded before any data is released.

    How to get there

    Define identity checks for low and high risk requests. Use existing login or a one-time code where possible. Avoid collecting extra documents unless needed. Log the check result with each request.

  6. ShouldRTS-06

    Every request is tracked with an owner and timestamps

    To answer rights requests and grievances on time, you need to know when each one arrived, who is handling it and when it closed. This record also helps you show the Board how you respond.

    What good looks like

    Every request and grievance sits in one tracker with a reference number, owner, received date, due date and closure date. Managers can see overdue items and trends at a glance.

    How to get there

    Choose one tracker, even a shared sheet to start. Give each request a reference number. Record owner, dates and outcome. Review open and overdue items every week.

  7. ShouldRTS-07

    Requests from persons with disability and lawful guardians are supported

    Where a person with a disability has a lawful guardian, you need the guardian's verifiable consent. Guardians and people with disabilities should also be able to use your consent and rights processes without barriers.

    What good looks like

    Your forms and channels are accessible. Staff know how to confirm that a guardian is lawfully appointed. Guardian consent and requests are recorded and handled like any other request.

    How to get there

    Check your request forms for accessibility. Decide what proof of guardianship you accept. Write a short guardian procedure. Train the team and record guardian requests separately.

Other areas we assess

All 13 areas

Check this area against your own business

The free assessment scores this area with the rest and shows you where it ranks against your other gaps.

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.