Four things need to change before the DPDP notice and consent provisions commence on 13 May 2027, and the policy text comes last: the notice shown where data is collected, separate choices for optional uses, a withdrawal route as easy as the sign-up, and records showing what each person saw and chose. A privacy policy does not, by itself, show that your forms collect the right information, your users make meaningful choices or your staff honour those choices. A useful DPDP privacy notice audit starts with the screens and data flows, then corrects the document to match them. Review the enquiry form, checkout, newsletter signup and customer account separately.
Part of the legal advisory and regulatory compliance practice at S Jain & Attorneys, Bangalore.
Position checked on 18 November 2026. The DPDP Act's ordinary notice and consent provisions and the corresponding operational Rules are in the eighteen-month commencement tranche, scheduled to commence on 13 May 2027. The final Rules already exist. Present obligations under the 2011 sensitive personal data rules, contracts and relevant sector law need their own assessment now. Preparing the future notice is not a substitute for checking those duties.
Where should our DPDP privacy notice audit begin?
Begin with the information a person actually supplies and the destinations it reaches, rather than the policy your designer copied. Open each form as a customer would. Record every visible field, compulsory field, attachment box, automatic identifier and service receiving the submission. A form that emails a mailbox, creates a CRM contact and triggers a marketing sequence has three operational consequences even if its button merely says "Submit".
Use the following review sheet for one collection point at a time. It is a design and evidence checklist, not a statutory form prescribed for every business.
| Question | Evidence to inspect | Practical correction |
|---|---|---|
| What do we collect? | Fields, uploads and actual technical records | Remove unnecessary collection and describe the remaining categories |
| Why do we need it? | Specific service and internal use | Separate an enquiry response from an optional campaign |
| Where does it go? | Mailboxes, CRM, vendors and access permissions | Check the notice and supplier instructions against the real route |
| What choice exists? | Default settings and submission behaviour | Test optional choices rather than displaying a decorative checkbox |
| What proof remains? | Notice version, event and later preference changes | Keep proportionate records that can reconstruct the transaction |
Ask the product owner and a person who handles submissions to complete this together. A policy author may not know that a spreadsheet is exported every Friday. A developer may not know that a consultant receives attachments. The useful result is an accurate map of one transaction, with an owner for each correction.
These three checks keep the review attached to the product rather than to abstract promises.
Actual collection
List the fields and technical records collected by each screen, including attachments and automatic transfers that the visible form does not explain.
Separate purposes
Describe the requested service separately from optional marketing or analysis, then test whether the product actually respects the choices it offers.
Usable contact
Check that a person can find a working contact and make a clear request without being sent around an unrelated support process.
What must the notice explain when we ask for consent?
Under the future DPDP notice framework, explain the relevant data, specified purposes and routes for withdrawal, rights and complaints in a form the person can understand independently. Section 5 of the Act and Rule 3 of the final Rules supply the legal starting point. A reference to a hundred-page contract is not a useful explanation of a two-field enquiry form.
Rule 3 requires an itemised account of the personal data and a specific description of the goods, services or uses enabled by the processing. Translate that into facts about your product. "Contact details to answer this request and arrange the consultation you requested" is more informative than "information for our legitimate business activities". Check that the use described is the use your team will actually make.
An illustrative drafting structure is: "We collect [itemised fields] to [specified purpose, and the service or use it enables]. You can withdraw consent for [optional use] at [communication link or other stated means], as easily as you gave it, and use the same route to exercise your rights. Contact [responsible person] with questions about this processing. You can complain to the Data Protection Board of India through [stated route]." The brackets are matters to investigate, not blanks to fill with attractive promises. The complaint line describes the position once the relevant provisions commence on 13 May 2027.
The 2011 Rules require a separate present-law review. Rule 4 already sets out what a published privacy policy must state: clear practices and policies, the types of personal or sensitive information collected, the purposes, disclosures and security practices. Rule 5 adds collection, use and grievance requirements where sensitive personal data is collected, including a Grievance Officer who must redress grievances within one month of receipt. Section 44(2) of the DPDP Act omits IT Act section 43A, and clause (ob) of section 87(2) under which these Rules were made, from 13 May 2027. An ordinary name and email address should not automatically be described as medical or financial information. Conversely, an attachment box can receive that material even when you did not intend to collect it.
Common mistake. Changing the heading of an old policy to "DPDP compliant" while leaving the form, vendor transfers and preference settings untouched proves little about what the customer experienced.
Which purposes should have separate choices?
Separate uses that do not form part of the service the person requested, and assess the lawful basis for each use instead of assuming one compulsory tick can cover everything. Section 6's consent standard is tied to the specified purpose and necessary data. Section 7 identifies particular uses that require their own factual analysis. Neither provision justifies a vague permission to do anything with a customer record.
For example, answering an enquiry, booking a requested demonstration and enrolling the same person in unrelated promotional messaging are different steps. Write down which step the visitor initiated and which step the company added. The interface should not make the visitor agree to an optional promotional use simply to ask a basic question. Marketing also needs its own channel-specific assessment, which a privacy notice cannot replace.
Run a practical test: submit the form with the optional choice unselected, then inspect the resulting record. If the CRM still marks the person as subscribed, the wording is not the main defect. Fix the automation. Repeat the test where the person later changes the choice. A preference stored in one table but ignored by the sending tool is not an implemented preference.
Keep consent-dependent uses distinct from records retained under another identified legal requirement. Otherwise the company may promise to erase an invoice when the person leaves a newsletter, or continue marketing because the invoice must remain. Those are avoidable design errors caused by treating the whole customer record as a single permission.
How should language and withdrawal work in the product?
The options should be understandable and usable at the point where the person needs them. Sections 5(3) and 6(3) address access to notices and consent requests in English or a language specified in the Eighth Schedule. Review the actual choice provided to your audience instead of merely translating a footer that the collection screen never displays.
Keep translated versions aligned. If the English text lists two purposes but another version appears to authorise five, the records do not show a consistent request. Identify the version and language that accompanied each material decision. A later translation should not overwrite the evidence of the earlier screen.
From 13 May 2027, for consent-based processing, section 6(4) requires comparable ease of withdrawal. A one-click signup paired with an unexplained demand for a notarised letter to unsubscribe is an obvious design problem. The appropriate identity check depends on the request. Stopping an email campaign is not the same risk as disclosing a complete account history or changing an account's controlling contact.
Test the route on a phone. Follow the link without an employee account, confirm that it opens the intended page and see whether an ordinary person can identify what will stop. Explain any processing that lawfully continues on another basis. Avoid a generic button claiming "Delete everything now" when the company has not mapped retention and vendor copies.
Who answers requests and what happens after submission?
A working request route needs an accountable recipient, an internal process and a reply that deals with the request. Publishing a mailbox alone does not establish any of those things. The future framework includes contact requirements under section 6(3) and Rule 9, while Rule 14 addresses the means and identification particulars for exercising rights.
Do not appoint every privacy contact as a statutory Data Protection Officer by default. The Act connects that particular office with Significant Data Fiduciaries. Describe the person's actual role accurately, and check whether a designation or other applicable law imposes additional duties. The 2011 Rules also have their own Grievance Officer provision and timetable. Do not replace that present framework with a future DPDP label.
Agree who checks a request, who locates records, who contacts vendors and who approves a response where another person's information is involved. Record receipt and routing dates. Publish only a response period your process and the applicable law support. The future Rule 14 grievance period is not a universal deadline for every conceivable privacy operation, and it should not be presented as today's permission to ignore a live complaint.
For each route, prepare a short internal instruction describing what information is reasonably needed to identify the requester. Avoid collecting a fresh identity-document archive merely because the company did not design its customer reference system. Where the request is unclear, ask a focused question about the account or records concerned rather than demanding unrelated personal information.
How do we prove what the person saw and chose?
Keep enough evidence to reconstruct the relevant notice and decision without collecting unrelated personal data for an unlimited period. Under section 6(10), from 13 May 2027, where consent is the basis and a question arises in a proceeding before the Board, the fiduciary must prove notice and consent in accordance with the Act and Rules. A current screenshot cannot establish what appeared to a person a year earlier.
A proportionate record may identify the account or collection event, timestamp, notice version, language, displayed choices, response and subsequent changes. Which identifiers are necessary depends on the workflow. A signed form, a server-side event and an email confirmation have different strengths. Describe their limits honestly rather than treating any populated CRM column as conclusive proof.
Keep the source text for each material notice version and record when it was deployed. Check what happened during an outage, a migration or a campaign run from another system. A default value introduced by a software import may mean "unknown", even when the interface labels it "yes". Preserve that history rather than rewriting it to make the audit look complete.
Evidence itself needs access and retention controls. In particular, the future Rules include retention provisions that must be read with the underlying processing and applicable law. Do not design proof collection as a reason to keep every session recording or document indefinitely. The purpose is to answer a specific factual question, not to create an unbounded surveillance archive.
These implementation tasks belong to named owners, not to an unattended policy document.
Product owner
Check the actual collection screens and automation so the uses described in the notice match what the software does after a submission.
Response owner
Receive and route requests, identify the relevant account proportionately, and record what action was taken across internal systems and service providers.
Evidence owner
Preserve material notice versions and choice records with access limits, while identifying the applicable purpose and legal basis for each retained category.
What should we change before calling the review complete?
Close the mismatches in the product, documents and operating instructions, then retest them with an ordinary user account. A sensible completion record identifies what was examined, what changed, what remains dependent on a supplier and which future-law steps are scheduled. It should not promise that a checklist establishes compliance with every sector rule.
- Inventory each collection point and its actual recipients.
- Remove unnecessary fields and separate optional purposes.
- Write the notice around verified data flows and applicable requirements.
- Test language, preferences, withdrawal and request routes.
- Check that vendor instructions and evidence records match the user choices.
- Record the result, responsible owners and next review triggers.
The useful practitioner question is simple: if a customer challenges one use of one field, can the company explain why it holds it and show what the customer was told? That question exposes gaps faster than asking whether a polished policy looks sufficiently legal. It also prevents the document team and product team from declaring separate versions of success.
Key takeaway. Treat the privacy notice as the explanation of a functioning collection and request process. Complete the present-law review now, and implement the future DPDP requirements against their actual commencement.
Frequently Asked Questions
Is a privacy policy the same as a DPDP notice?
A policy can describe general practices, while the DPDP notice framework requires information relevant to the processing and consent request. Check what the person actually sees when data is collected.
Must every form have a consent checkbox?
Assess the use and applicable lawful basis first. A checkbox does not by itself establish necessity, adequate notice or valid consent.
Can we copy another company's policy?
It is likely to describe different fields, recipients and purposes. Use the actual data-flow review to write accurate text instead.
Does DPDP require us to appoint a DPO immediately?
Do not assume that every business needs the statutory DPO office. Check the Act's Significant Data Fiduciary provisions, any applicable designation and other current requirements.
Can we require an identity document to unsubscribe?
Match identification to the actual request and risk. Do not impose unnecessary data collection or friction on a straightforward withdrawal route.
Are the final DPDP Rules still awaited?
No. The final 2025 Rules exist with phased commencement and corrections. Distinguish their publication from the later start of the core operational requirements.
Can we label our policy fully compliant after this checklist?
The checklist is a practical review tool. Compliance depends on the real processing, operative law and implemented controls, not the label placed on the document.
What should trigger another review?
A new collection field, purpose, vendor, language version or request process should trigger a targeted review. Legal changes and incidents can also reveal a mismatch.
This article is for general informational purposes only and does not constitute legal advice. Consult a qualified advocate for advice on your specific situation.






