India's new Parliament building in New Delhi, photographed by the Ministry of Parliamentary Affairs in May 2023
DPDPThe DPDP build year: from privacy policy to operating control.
India's Parliament building, New Delhi. Photograph: 27 May 2023.Image: Ministry of Parliamentary Affairs / PIBGODL-IndiaImage fitted for layout; headline added by Securelay. Editorial context, not endorsement.
Primary source MeitY — DPDP Act commencement notification dated 13 November 2025Primary source MeitY — Digital Personal Data Protection Rules, 2025

Start with the real data

Map personal data by system, processor, field, principal, purpose, retention, residency, transfer, and AI exposure. Prioritize the paths with the largest plaintext blast radius and the weakest ability to answer rights requests.

Convert purpose into enforcement

A purpose string in a spreadsheet cannot stop an API call. Bind disclosure and processing paths to explicit purpose, consent state, role, and data scope. Withdrawal and expiry should change runtime behavior, not merely generate a ticket.

Exercise rights and breach workflows

Run realistic access and erasure requests across processors. Time the work, verify identity and authorization, preserve receipts, and document exceptions. Then rehearse a breach scenario using the same inventory and evidence paths.

Use the date precisely

Some provisions commenced on 13 November 2025 and specified provisions follow after one year. Most core operational provisions follow after eighteen months. Applicability and legal interpretation belong with qualified counsel; engineering teams should use the schedule to drive concrete readiness gates.

Put the control on the data path.Discuss an architecture review