DPDP Act 2023Updated 22 November 20268 min read

Duties of Data Principals Under Section 15 of the DPDP Act

Section 15 of the DPDP Act gives individuals five duties, from not impersonating others to not filing frivolous complaints, backed by a penalty of up to ₹10,000.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Section 15, DPDP Act, 2023
Number of duties
Five, clauses (a) to (e)
Maximum penalty
Up to ₹10,000
Who imposes it
Data Protection Board after inquiry
Applies from
13 May 2027
Related rule
Rule 14 (identifiers for rights requests)

Quick answer

Section 15 of the DPDP Act, 2023 imposes five duties on Data Principals: comply with applicable law, do not impersonate another person, do not suppress material information when providing data for State-issued documents or identifiers, do not register false or frivolous grievances or complaints, and furnish only verifiably authentic information when seeking correction or erasure. Breach can attract a penalty of up to ₹10,000.

  • Data Principals have five statutory duties under section 15 of the DPDP Act.
  • The maximum penalty for breaching a Data Principal duty is ₹10,000, far below fiduciary penalties.
  • Duties do not reduce a Data Fiduciary's obligations; a fiduciary cannot refuse rights requests by citing them.
  • Fiduciaries may ask for identifiers published under Rule 14(1)(b) to verify requests, not for excessive proof.
  • False correction requests and impersonation in rights requests are the duties most relevant to product teams.

Who this is for: Individuals and consumers, Customer support and trust & safety teams, Data Protection Officers, Product managers building rights-request flows

What are the duties of a Data Principal?

Most privacy laws only give individuals rights. The DPDP Act also gives them duties. Section 15 says a Data Principal shall perform the following while exercising rights under the Act:

  1. Comply with the provisions of all applicable laws while exercising rights under the Act.
  2. Not impersonate another person while providing her personal data for a specified purpose.
  3. Not suppress any material information while providing her personal data for any document, unique identifier, proof of identity or proof of address issued by the State or any of its instrumentalities.
  4. Not register a false or frivolous grievance or complaint with a Data Fiduciary or the Board.
  5. Furnish only such information as is verifiably authentic while exercising the right to correction or erasure.

The design intent is to discourage abuse of rights mechanisms — for example, using erasure requests to wipe fraud records, or flooding a company and the Board with complaints. The duties also connect the Act to identity-document integrity, which matters for Aadhaar-linked and KYC processes.

These duties sit alongside the rights in sections 11 to 14: access, correction and erasure, grievance redressal, and nomination. A Data Principal who is a child acts through a parent or lawful guardian, since the Act's definition of Data Principal includes them.

What is the penalty for breaching these duties?

The Schedule to the Act sets the penalty for breach of section 15 at up to ₹10,000. Compare that with fiduciary penalties of up to ₹250 crore for security failures, and up to ₹200 crore each for breach-notification and children's data failures.

BreachMaximum penalty
Data Principal duties (s.15)₹10,000
Any other provision of the Act or Rules₹50 crore
SDF additional obligations₹150 crore
Children's data obligations₹200 crore
Breach intimation failure₹200 crore
Reasonable security safeguards₹250 crore

Penalties are imposed only by the Data Protection Board after an inquiry, considering factors such as nature, gravity and duration of the breach, and they go to the Consolidated Fund of India. A Data Fiduciary cannot fine a user or deduct anything for a "frivolous" request.

The Act also allows the Board to issue a warning or impose costs where it finds a complaint false or frivolous, which is a separate deterrent from the section 15 penalty. In practice, expect the duty to be invoked rarely and mainly in clear-cut abuse cases.

What the duties mean for Data Fiduciaries

The duties are not a shield. A Data Fiduciary must still respond to every rights request and grievance through the system it publishes under Rule 14, within a period not exceeding 90 days. What the duties do give you is a principled basis for verification.

Verification you can lawfully ask for

Rule 14(1)(b) requires you to publish the particulars, such as a username or other identifier, needed to identify a Data Principal under your terms of service. Rule 14(5) defines "identifier" to include customer identification file numbers, application reference numbers, enrolment IDs, email addresses, mobile numbers and licence numbers. Ask for what you have published, matched against what you already hold.

What not to do

  • Do not demand fresh government ID for a simple access request when a logged-in session already authenticates the user.
  • Do not reject correction requests simply because the user cannot prove a negative; ask for reasonable evidence.
  • Do not label complaints "frivolous" internally to justify ignoring them. Only the Board can treat a complaint as false or frivolous.

Where the duties help

  • Correction requests that try to change KYC-verified fields (name, date of birth) without evidence — section 15(e) supports asking for verifiable documents.
  • Impersonation in account-recovery or rights flows — section 15(b) supports step-up authentication.
  • Repeated identical complaints — log them, respond consistently, and keep the record for any Board inquiry.

Designing rights flows around the duties

Product and support teams can reflect section 15 without adding friction for honest users:

  • Authenticate in-session. Put access, correction and erasure in the logged-in account area so identity is already established. For non-account users, verify using a one-time code to the registered email or mobile.
  • Tier by risk. Low-risk changes (marketing preferences) need no extra checks; high-risk changes (bank details, legal name, nominee) need step-up authentication and evidence.
  • Display a short attestation on correction and erasure forms: "The information I am providing is accurate and verifiably authentic." This mirrors section 15(e) and is easy to log.
  • Log the request lifecycle — receipt, verification method, decision, response date — so you can show the Board you handled it in time. Rule 9 also requires every response to include your DPO or contact person's business contact details.
  • Handle nominees carefully. Under Rule 14(4) a Data Principal may nominate one or more individuals. Verify the nominee's authority before acting on death or incapacity.
  • Children and guardians. For a child, the parent acts as Data Principal; for a person with disability, the lawful guardian verified under Rule 11.

For the broader rights framework see Data Principal rights and grievance redressal.

How this compares with GDPR and other laws

GDPR has no equivalent list of duties for data subjects. It addresses abuse differently: a controller may charge a reasonable fee or refuse requests that are manifestly unfounded or excessive, and must be able to show why. The DPDP Act instead gives individuals explicit duties with a statutory penalty, and keeps the fiduciary's obligation to respond.

Two implications for teams running both regimes:

  • Do not import GDPR's "refuse as manifestly unfounded" practice into Indian flows without care. Under the DPDP Act the remedy for abuse lies with the Board, not with the fiduciary refusing to engage.
  • Verification standards can be shared. Identity checks proportionate to the request are good practice in both regimes.

The section 15(c) duty about not suppressing material information for State-issued documents and identifiers overlaps with existing laws on identity documents. Section 15(a) — comply with all applicable laws — is a general reminder that exercising data rights does not override other legal obligations, such as record-keeping rules in banking or tax.

Common mistakes

  1. Treating duties as grounds to refuse. A fiduciary must still respond within its published period, not exceeding 90 days.
  2. Over-verification. Demanding Aadhaar copies or notarised documents for routine requests creates new personal data and friction. Use the identifiers you publish under Rule 14.
  3. Assuming the company can impose the penalty. Only the Board can, after inquiry.
  4. Ignoring the record. If you believe a complaint is false, document facts calmly; the Board decides.
  5. Not telling users how to complain. Rule 3(c)(iii) requires your notice to describe how a Data Principal can complain to the Board. The duty against frivolous complaints does not remove that.
  6. Hiding the contact person. Rule 9 requires the business contact information of your DPO or contact person to be published prominently and repeated in every response to a rights request. Users who cannot reach anyone are more likely to escalate.
  7. No evidence trail. Without timestamps for receipt, verification and response, you cannot show the Board that a disputed request was handled properly, or that a complaint was in fact repetitive. Keep request records in a system that also meets the Rule 8(3) one-year minimum for processing logs.

Further reading on suhasbhairav.com

Key dates

  1. DPDP Act, including section 15 duties, receives assent

  2. Section 15 duties and rights provisions, with Rule 14, apply

Answers

Frequently asked questions

What are the duties of a Data Principal under the DPDP Act?

Section 15 sets five duties: comply with applicable laws, do not impersonate another person, do not suppress material information when providing data for State-issued documents or identifiers, do not file false or frivolous grievances or complaints, and furnish only verifiably authentic information when seeking correction or erasure.

What is the penalty for a Data Principal under the DPDP Act?

The maximum penalty for breaching a Data Principal duty under section 15 is ₹10,000, imposed by the Data Protection Board after inquiry. It is far lower than penalties for Data Fiduciaries, which go up to ₹250 crore for failing to take reasonable security safeguards.

Can a company refuse a privacy request as frivolous in India?

Not on its own authority. A Data Fiduciary must respond through its grievance and rights system within its published period, which cannot exceed 90 days under Rule 14(3). It may verify identity using published identifiers. Only the Board can treat a complaint as false or frivolous.

Can I be fined for complaining to the Data Protection Board?

Only if the complaint is false or frivolous, which breaches section 15(d) and can attract a penalty of up to ₹10,000. Genuine complaints carry no penalty. You must first exhaust the Data Fiduciary's grievance redressal process under section 13 before approaching the Board.

What proof can a company ask for in a correction request?

It can ask for the identifiers it publishes under Rule 14(1)(b), such as username, email, mobile number or customer ID, and reasonable evidence for high-risk changes. Section 15(e) requires Data Principals to furnish verifiably authentic information when seeking correction or erasure.

Do children have duties under the DPDP Act?

For a child, the Data Principal includes the parent or lawful guardian, who exercises rights on the child's behalf. In practice the parent or guardian acting for the child should be treated as bound by the section 15 duties, such as not impersonating another person and furnishing authentic information.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 15 (official text)
  • Digital Personal Data Protection Act, 2023 — Schedule, penalty for breach of section 15 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 14 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.