Protecting client information begins with knowing where it goes. A file uploaded to an AI or cloud service may pass through several processors. A product description is not evidence that a particular confidentiality or security requirement has been met.
What information is necessary?
Identify the task and remove unnecessary identifiers before testing a tool. Check your authority to share the record, including restrictions in court orders, client instructions and applicable law. Keep the original in the approved matter repository.
Who can access the data?
Ask which staff, administrators and service providers can access content, for what purposes and under what controls. Check retention, backup deletion, exports and what happens when an account closes. Ask separately whether content is used for model training and whether any controls apply to every connected service.
What does encryption mean here?
Encryption in transit and at rest are distinct from end-to-end encryption. Do not label server-side AI processing end-to-end encrypted without evidence of the architecture and key control. Request current documentation for any certification or audit claim rather than assuming it applies to every product and deployment.
Which DPDP provisions apply now?
MeitY’s 2025 Rules have phased commencement, and the Act has its own enforcement-timeline notifications. Check the applicable provisions and effective dates rather than treating publication of the Rules as commencement of every obligation. Confidentiality and other existing duties need separate assessment.
How should the practice decide?
Maintain an approved-services register, assign access by role, review exports and agree an incident-response contact. Record the purpose and authority for sharing each sensitive category. JuniorLawyer’s Privacy and Security pages describe its published position; they are not an independent compliance certification.
Have the responsible lawyer and information-security adviser resolve gaps before uploading confidential material.
Phased commencement and incident preparation
As of 18 November 2026, the November 2025 notifications use a phased timetable:
| Phase | Act and Rules |
|---|---|
| Publication in November 2025 | Institutional and specified enabling provisions, including the Board framework; Rules 1, 2 and 17–21 |
| One year after publication (November 2026) | Section 6(9), Section 27(1)(d), and Rule 4 concerning consent managers |
| Eighteen months after publication (May 2027) | Most substantive processing duties, rights and enforcement provisions; Rules 3, 5–16, 22 and 23 |
Check the Act commencement notification and Rules and corrigendum for the exact provision and date. The Data Protection Board’s institutional establishment is distinct from commencement of every substantive duty.
Prepare an incident register and escalation owner now. When Rule 7 applies, breach notices to affected people and initial information to the Board are required without delay; further prescribed information ordinarily follows within 72 hours, unless extended. The Act’s Schedule includes a maximum penalty of ₹250 crore for failure to take reasonable security safeguards and ₹200 crore for breach-notification failures. These are statutory maxima, not automatic fines. Existing confidentiality and other reporting obligations need separate assessment during the transition.