Compliance

Practical steps for businesses to meet Data Principal duties

Businesses must follow a clear process when a data principal exercises rights, ensuring compliance with Section 15 of the DPDP Act and avoiding penalties of up to ₹10,000 for false complaints or misuse of information

Check your DPDP readiness — free More on the blog

Initial receipt of a data principal request

When a request arrives, the first point of contact – typically the compliance officer or data protection officer – logs the request in a central register. The log records the request type, date, the data principal’s identity, and the channel used. This creates an audit trail that satisfies the duty to comply with applicable laws and provides evidence if the Board later investigates the request.

Verification of identity and authenticity

Before any action, the business must verify that the requestor is the genuine data principal. This involves checking government‑issued proof of identity or address, as required by law, without impersonating another person. The verification team documents the documents examined and notes any discrepancies, ensuring that only authentic information is used for correction or erasure.

Assessing the request for frivolity

The compliance team reviews the request to determine whether it is false or frivolous. This does not mean rejecting the request outright; instead, the team checks if the grievance lacks factual basis or is made in bad faith. If doubts arise, the team records the rationale and escalates to senior management for a decision, keeping the record for possible Board review.

Responding to the request

Once the request is deemed legitimate, the responsible department – for example, IT for data erasure or HR for correction – carries out the action within the statutory time‑frame. The action taken, the date of completion, and the person responsible are all entered into the register. This documentation demonstrates compliance with the duty to furnish only verifiably authentic information.

Handling grievances and complaints

If the data principal files a grievance, the business must follow the grievance procedure under Section 13. The compliance officer records the grievance, acknowledges receipt, and forwards it to the Board if required. The business must not dismiss the grievance as frivolous without proper assessment, as the Board, not the business, decides on the penalty.

  • Log every request in a central register
  • Verify identity using State‑issued documents
  • Document verification outcomes
  • Assess for false or frivolous content
  • Escalate doubtful cases to senior management
  • Execute correction or erasure and record action
  • Maintain full audit trail for Board inspection

Record‑keeping and evidence preparation

All records – request logs, verification notes, decision rationales, and action confirmations – must be stored securely for at least the period prescribed by law. If the Board initiates an enquiry, the business can produce these records to demonstrate that it complied with Section 15 duties, thereby avoiding the ₹10,000 penalty.

Training and internal awareness

Regular training sessions for staff handling data principal requests reinforce the duties under Section 15. Training logs, attendance sheets, and updated SOPs should be kept as part of the compliance evidence. This proactive step reduces the risk of inadvertent breaches and shows the Board that the business takes its obligations seriously.

Common questions

What documentation must a business keep when a data principal makes a request?

The business should maintain a request register, identity verification notes, any assessment of frivolity, the decision rationale, and a record of the corrective or erasure action taken. These documents form the audit trail required under Section 15 and are needed if the Board investigates.

Can a company reject a request it believes is frivolous?

No. The company must assess the request, document its reasoning, and follow the grievance process. Only the Board can determine whether a complaint is frivolous and impose the up to ₹10,000 penalty.

Who in the organisation is responsible for handling data principal duties?

Typically the data protection officer or compliance officer receives the request, while verification may involve the legal or HR team. Execution of correction or erasure is done by the relevant operational department, all coordinated by the compliance function.

What is the financial risk if a business files a false grievance?

If a data principal files a false or frivolous complaint, the Schedule of penalties allows a fine of up to ₹10,000. While modest, it serves as a check against abuse and can affect the business’s reputation if the Board publicises the breach.

Related reading

  • DPDP Consent Notice: Checklist and Format for Websites & Apps — Section 5 makes a standalone consent notice mandatory before collecting any personal data. What it must contain, where to place it, and common mistakes.
  • What Is the DPDP Act 2023? Plain-English Summary for Indian Businesses — India’s Digital Personal Data Protection Act explained without legal jargon — who it applies to, the core rules, and what your business must change.
  • DPDP vs GDPR: 7 Key Differences Every Indian Business Must Know — DPDP is not European GDPR with the section numbers changed. Lawful bases, DPO rules, cross-border transfers and penalties compared side-by-side.

Written by Swaraj Layek

Published 16 October 2026. Founder & CEO at VidhiSar. I have watched four companies pay for the same mistake, and it was never the mistake anyone expected. VidhiSar is software, not a law firm: every answer names the section it relies on so you can check it, and anything turning on your specific facts is worth putting to a professional. More about who builds this

Maintained by the VidhiSar Legal Team

Maintains the law explainers, calculators, templates and blog posts on vidhisar.in: checks them against the statute text and updates them when the law changes. Errors and changes in the law can be reported to legal@vidhisar.in.