DPDP Act compliance, run as everyday privacy work
DPDP Act compliance means knowing what personal data you hold and why, telling people about it, keeping it safe, answering their requests on time and reporting breaches properly. BeAuditReady gives your privacy lead one place to keep the record of processing, run requests and grievances, set retention rules and prove each step later.
4 tasks: CRM, app DB, support desk, email vendorFulfilment
Response drafted · needs approvalResponse review
Marketing SMS after withdrawalEscalated
Identity verified · method recordedResponded
Legal hold on loan records blocks erasure task 3 of DPR-0231. Reason and approver recorded.
What the Digital Personal Data Protection Act 2023 covers
The Act applies to digital personal data processed in India, and to processing outside India when it is connected with offering goods or services to people in India. Data collected on paper and later digitised is covered too. The company that decides why and how data is processed is the Data Fiduciary. A vendor processing on its behalf is a Data Processor, and the Fiduciary stays responsible for what the Processor does.
You can process personal data with valid consent, or for a limited list of "legitimate uses" in the Act, such as data a person gives voluntarily for a specific purpose, employment-related processing and compliance with a legal obligation. Everything else needs consent that is free, specific, informed, unconditional and unambiguous, and withdrawing it has to be as easy as giving it.
How the DPDP Rules 2025 phase in
MeitY notified the DPDP Rules on 13 November 2025 and staggered their start. The dates below are measured from that notification.
November 2025
Data Protection Board
The Rules on setting up and running the Data Protection Board of India took effect on notification. The Board is the body that inquires into breaches and imposes penalties.
November 2026
Consent Managers
About 12 months after notification, the registration and obligations of Consent Managers begin. They must be registered with the Board.
May 2027
Most Fiduciary duties
At 18 months, the core obligations apply: notice, security safeguards, breach intimation, retention and erasure, data principal rights, children's data and the extra duties of Significant Data Fiduciaries.
Eighteen months is less time than it looks. Most of it goes on the first step: finding out which teams collect personal data, in which systems, shared with which vendors, and for what purpose. Contracts with processors and the request process come after that.
DPDP Act compliance duties and what BeAuditReady provides
The Act sets the duties; the Rules add the detail. Here is each one next to what you can do about it in BeAuditReady today.
| Duty | What the law expects | What BeAuditReady gives you |
|---|---|---|
| Notice | A clear notice, understandable on its own, listing the personal data and the purpose, how to withdraw consent, how to exercise rights and how to complain to the Board. | Notices linked to purposes and processing activities, with versions, approvals and effective dates. Old versions stay on record, so you can show which notice a person saw. |
| Consent and withdrawal | Consent that is specific to a purpose, and withdrawal as easy as giving it. Processing stops within a reasonable time after withdrawal. | The processing inventory records which activities rely on consent and which on a legitimate use. Withdrawal requests arrive through the request intake and become tracked tasks per system. |
| Security safeguards | Reasonable safeguards to prevent a breach. The Rules point to measures such as encryption or masking, access control, logs to detect misuse, backups and contract terms with processors. | DPDP requirements mapped to controls you may already run for ISO 27001 or SOC 2, with evidence, owners and expiry dates. Connectors check settings such as MFA and encryption daily. |
| Breach intimation | Inform the Board and each affected data principal without delay, then a detailed report to the Board within 72 hours unless extended. | Privacy incidents with affected data, awareness timestamps, a notification assessment and separate reporting clocks. Drafts are reviewed by people and receipts recorded. Nothing is filed automatically. |
| Retention and erasure | Erase personal data once the purpose is served or consent is withdrawn, unless another law requires you to keep it. Processors must erase too. | Retention rules per activity and data class, legal holds that block erasure, and approved erasure tasks with completion attestations. It does not delete data in your databases. |
| Rights and grievances | Publish how people can request access, correction, completion, erasure or nomination, and how to raise a grievance. The Rules set an outer limit of 90 days to respond. | A branded public intake page, identity checks that do not ask for Aadhaar by default, a case workflow from received to closed, deadline tracking and approval before any response goes out. |
| Children's data | Verifiable consent of a parent or lawful guardian before processing data of anyone under 18. No tracking, behavioural monitoring or targeted advertising aimed at children. | A children's data flag on each processing activity, privacy assessments for those activities, and the verification method you use recorded as a control with evidence. |
| Processors | Engage a processor only under a valid contract, and stay responsible for its processing. | Vendor register with risk tier, contracts, notice dates and scheduled reviews. Processors appear as recipients against each activity, so an erasure request knows which vendors to chase. |
| Significant Data Fiduciaries | A DPO based in India, an independent data auditor, and a Data Protection Impact Assessment and audit at least once a year under the Rules. | Privacy assessments with risks, mitigations and approvals, and an audit workspace where your data auditor sees only what you share for a set period. |
Requests will come through support, email and WhatsApp. Plan for that.
Under the Act, a data principal can ask for a summary of the data you hold and who you shared it with, ask for it to be corrected, completed, updated or erased, nominate someone to act after death or incapacity, and raise a grievance with you before going to the Board.
The hard part is not the form. It is the erasure request for a customer whose records sit in your CRM, app database, support desk and email platform, while finance has to keep the invoices for tax. BeAuditReady splits that request into a task per system and processor, applies the legal hold where one exists, and holds the response until someone approves it.
- Every case has a received date and a due date you can see on one list
- Identity verified in proportion to the request, without asking for Aadhaar by default, and the method recorded
- Grievances tracked separately, with escalation when they age
- Responses reviewed before they go out, and the sent version kept
- Closed cases stay on record for the time your retention rule sets
A practical order of work before May 2027
01
Build the inventory
List each processing activity: purpose, data categories, systems, processors, retention and lawful basis. A questionnaire per team or a CSV import gets you a first draft.
02
Fix notices and contracts
Rewrite notices against real purposes, then check that every processor contract covers security, breach reporting and erasure.
03
Stand up requests and incidents
Publish the intake page, assign owners per system and rehearse one breach from awareness to Board report.
04
Set retention and review
Agree retention per activity with legal and finance, then schedule reviews so the inventory does not go stale.
The full step-by-step list, with what to collect at each stage, is in our DPDP Act compliance checklist. If you also hold ISO 27001 or are working towards it, the security safeguard controls carry over; see the ISO 27001 page.
Why boards are asking about the DPDP Act now
The Schedule to the Act allows the Data Protection Board to impose penalties of up to ₹250 crore for failing to take reasonable security safeguards to prevent a breach, and up to ₹200 crore for failing to notify a breach or for breaching the duties on children's data. These are ceilings, not fixed fines. When the Board sets an amount, it can consider what you did to limit the harm, and a documented record of safeguards, assessments and decisions is the best evidence you will have.
Privacy and DPDP operations
See the full set of privacy modules: inventory, notices, requests, retention, incidents and assessments.
Explore the privacy solutionDPDP Act compliance questions
Straight answers. If yours is not here, ask us on a demo call.
When do the DPDP Act obligations actually start?
Is BeAuditReady a Consent Manager under the DPDP Act?
Do we need a Data Protection Officer?
How quickly must we report a personal data breach?
What is the maximum penalty under the DPDP Act?
We are a B2B SaaS company. Does the DPDP Act apply to us?
Is this legal advice?
See how your DPDP programme would look in BeAuditReady
Bring a list of your main systems and vendors. We will sketch your processing inventory, the request flow and the breach clocks with you, and show where the gaps are likely to be before May 2027.
No sales script. Bring your auditor's questions if you have them.