Which rights does the Act give people?
The Act calls the person the data is about the Data Principal, and the business that decides how it is used the Data Fiduciary. Chapter III gives the Data Principal four rights:
| Right | Section | What the person can ask for |
|---|---|---|
| Access to information | 11 | A summary of their personal data you process and what you do with it, and who you shared it with |
| Correction and erasure | 12 | Correct, complete or update their data, or erase it |
| Grievance redressal | 13 | A readily available way to complain to you, answered in time |
| Nomination | 14 | Name someone to use these rights for them if they die or become unable to |
The access and correction rights cover data you process because the person consented, or because they gave it to you voluntarily for a purpose (Section 7(a)). Data you process for other legitimate uses, such as a legal obligation, is outside them.
What must you send for an access request?
Under Section 11, when a person asks, you must give them:
- a summary of the personal data you are processing about them, and the processing activities you carry out with it;
- the identities of every other Data Fiduciary and Data Processor you shared it with, with a description of what was shared. That includes vendors such as your email provider, CRM, payment gateway and cloud host.
This is why a processing register matters. If you don't already know which systems hold a customer's data and which vendors receive it, you can't answer accurately. Sharing with authorities that requested it in writing to prevent, detect or investigate offences need not be disclosed.
When must you correct or erase data?
Section 12 requires you to correct inaccurate or misleading data, complete incomplete data and update data when asked. On a request to erase, you must erase the data unless you still need it for the specified purpose or a law requires you to keep it. Invoices you must keep for tax, for example, stay; marketing profiles go.
Erasure also reaches your vendors. Under Section 8(7) you must make your Data Processors erase the data too, so the request has to reach every system the register lists.
How fast must you respond?
The DPDP Rules, 2025 require every Data Fiduciary to publish on its website or app how a person can make a request, and what details it needs to identify them, such as an account email or customer number. You must then answer grievances within the period you publish, which cannot exceed 90 days. Aim for much less: 30 days is a common internal target and leaves room for difficult cases.
A person must use your grievance process before complaining to the Data Protection Board (Section 13(3)). Answering well and on time is the cheapest way to keep a complaint from going further. Failing these duties falls under the general penalty in the Schedule, up to ₹50 crore.
Do people have duties too?
Yes. Section 15 says a person using these rights must not impersonate someone else, must not hide material information, must not file false or frivolous complaints, and must give information that can be verified when correcting their data. Breaking these duties carries a penalty of up to ₹10,000. It's also why you may ask for reasonable proof of identity before releasing data: sending one customer's records to someone pretending to be them would be a breach of its own.
Who answers questions about the data?
Section 8(9) requires you to publish the business contact details of your Data Protection Officer, if you must have one, or of another person who can answer questions about how you process personal data. Put it in your notice and on the page where people make requests.
A simple process for a small business
- Publish one channel for requests: a web form or a dedicated email address, linked from your notice and footer. Say what identification you need and the time you commit to.
- Log every request with the date received, type, the person, the deadline and the outcome. The log is your evidence.
- Verify identity proportionately: a confirmation email to the address on the account is usually enough; ask for more only when the data is sensitive.
- Search every system on your processing register, not just the main database: email tools, spreadsheets, backups and vendors.
- Act and reply: send the summary, make the correction or confirm the erasure, and list what you had to keep and why.
- Tell your vendors to correct or erase, and keep their confirmation.
- Review the log monthly for requests near their deadline.
These duties apply in full from 13 May 2027. CyberLetics gives you a public rights page where people submit requests, confirms each request by email before the clock starts, tracks the deadline you set, and keeps the log. Its processing register lists which systems and vendors hold each kind of data, so you know where to look. The free website scan is a quick first check of what your site exposes today.