Quick answer
Under Rule 9 of the DPDP Rules, 2025, every Data Fiduciary must prominently publish on its website or app, and mention in every response to a Data Principal's rights request, the business contact information of its Data Protection Officer, if it has one, or of a person able to answer questions about the processing of personal data on its behalf. Rule 9 applies from 13 May 2027.
- Rule 9 applies to every Data Fiduciary, regardless of size, from 13 May 2027.
- Only Significant Data Fiduciaries must appoint a DPO; every other fiduciary publishes a person who can answer processing questions.
- The contact must be published prominently on the website or app, not buried in a long policy.
- The same contact must appear in every response to a communication exercising Data Principal rights.
- Rule 7(1)(e) breach notices and the Second Schedule intimation for State processing also require a contact who can respond.
Who this is for: All Data Fiduciaries, Privacy and legal teams, Customer support leads, Web and app product teams, Small businesses without a DPO
What does DPDP Rule 9 require?
Section 8(9) of the DPDP Act requires a Data Fiduciary to publish the business contact information of a Data Protection Officer, if applicable, or of a person able to answer Data Principals' questions about processing. Rule 9 says how.
Every Data Fiduciary shall:
- prominently publish on its website or app, and
- mention in every response to a communication for the exercise of the rights of a Data Principal under the Act,
the business contact information of:
- the Data Protection Officer, if applicable; or
- a person who is able to answer on behalf of the Data Fiduciary the questions of the Data Principal about the processing of her personal data.
Three words carry the weight:
- "Every": there is no size threshold. A two-person startup and a large bank both publish a contact.
- "Prominently": a contact hidden deep in a long privacy policy is weak compliance. Make it reachable from the footer, the account settings page and the privacy notice.
- "Every response": each reply to an access, correction, erasure, grievance or nomination request must include the contact, including automated replies.
Rule 9 applies from 13 May 2027.
Do you need a DPO or just a contact person?
The DPDP Act requires a Data Protection Officer only for a Significant Data Fiduciary (section 10). That DPO must represent the SDF under the Act, be based in India, be responsible to the board of directors or similar governing body, and be the point of contact for grievance redressal. No SDF has been notified yet, so for now this applies to no one in practice; plan for it "once notified".
Every other fiduciary needs only a person able to answer questions on its behalf about the processing. The Rules do not require that person to have a title, qualifications or independence. In practice:
| Organisation | Sensible choice |
|---|---|
| Startup or small business | Founder, CTO or operations lead, with a role mailbox |
| Mid-size company | Privacy lead or legal counsel, backed by a support queue |
| Large company not yet an SDF | A voluntary DPO or privacy office |
| Notified SDF | Mandatory DPO based in India |
A voluntary DPO is a reasonable choice for larger companies: it builds the function before any SDF notification and gives the Board a single counterpart. If you use the title "Data Protection Officer" voluntarily, publish that person's contact, since Rule 9 refers to the DPO "if applicable".
What "business contact information" should include
The Rules do not define business contact information. The test is whether a Data Principal can actually reach someone who can answer her questions.
A practical minimum:
- Name or role. A named individual or a clear role, such as "Privacy Officer". A role is more durable when staff change; a name adds accountability.
- Email address. A role-based mailbox such as privacy@ that does not depend on one person's inbox.
- Postal address. Useful for formal correspondence and for people who prefer it.
- Phone number or in-app channel, where the business supports them.
Avoid:
- A generic support address with no route to someone who can answer processing questions.
- A web form that only accepts sales enquiries.
- Contact details for a person who has left.
Placement:
| Surface | What to show |
|---|---|
| Website footer | "Privacy contact" link |
| Privacy notice (Rule 3) | Contact block alongside rights and withdrawal links |
| App settings | Privacy section with the contact |
| Rights response emails | Contact in the signature block |
Rule 14(1) separately requires publishing how to make rights requests and which identifiers are needed. Put both on the same page so people find them together. See Data Principal rights.
Including the contact in every rights response
The second limb of Rule 9 is easy to miss. The contact must be mentioned in every response to a communication exercising Data Principal rights. Under the Act those rights include access to information (section 11), correction and erasure (section 12), grievance redressal (section 13) and nomination (section 14).
Implementation:
- Template every response. Acknowledgements, requests for identity details, fulfilment notices, refusals and closure messages should all carry the contact block.
- Automate it. Add the contact to the ticketing system's rights-request macros so agents cannot send a reply without it.
- Keep it consistent. Use the same contact on the website, in the notice and in responses. Mismatched details create confusion and look careless in an inquiry.
- Cover all channels. If rights requests arrive by email, app, chat or a Consent Manager, the response through each channel must carry the contact.
- Version it. When the contact changes, update all templates in one release and record the date.
A related duty sits in Rule 7(1)(e): breach notices to Data Principals must include the business contact of a person able to respond to her queries. Use the same person or team where possible, staffed to handle the spike that a breach notice creates.
Where else the Rules require a contact person
Rule 9 is one of several contact requirements in the Rules. Aligning them reduces duplication.
| Provision | Context | Contact required |
|---|---|---|
| Rule 9 | Website or app, and every rights response | DPO or person able to answer processing questions |
| Rule 7(1)(e) | Breach intimation to each affected Data Principal | Person able to respond to her queries |
| Second Schedule (g)(i) | State processing under section 7(b) | Person able to answer processing questions |
| Rule 14(1) | Rights requests | Means of making requests (not a person, but a route) |
| Rule 14(3) | Grievance redressal | Published response period of no more than 90 days |
For most companies, one privacy contact can serve Rules 7, 9 and 14, with a ticketing queue behind it that tracks the 90-day grievance ceiling.
Government departments processing under section 7(b) need the Second Schedule contact as part of their intimation, in addition to Rule 9.
Significant Data Fiduciaries, once notified, need their DPO to be the point of contact for grievance redressal under section 10, so the Rule 9 contact and the DPO should be the same.
Common mistakes and a quick fix list
Patterns that will look poor in a Board inquiry:
- Personal mobile numbers of a founder published as the contact, which then go unanswered.
- A contact on the website but not in the app, where most users actually are. Rule 9 says website or app, but if users mainly use the app, put it there.
- Rights responses from a no-reply address with no contact block.
- A contact who cannot answer. The Rule requires a person "able to answer on behalf of the Data Fiduciary". A support agent with no access to privacy information does not meet that.
- Outsourced contact with no escalation. If a vendor runs support, make sure processing questions reach someone in your organisation who knows the answers.
Quick fix list for the next six months:
- Choose the contact person or role and a role mailbox.
- Write an internal FAQ so the contact can answer common processing questions quickly.
- Publish the contact in the footer, notice and app settings.
- Add the contact to every rights-response template and breach notice template.
- Set up monitoring on the mailbox with response-time targets aligned to your Rule 14(3) grievance period.
These steps are cheap and low-risk, and they are visible: a Board reviewer or a journalist can check them from outside in seconds.
Further reading on suhasbhairav.com
- BlogData privacy by design for AI features and products
- BlogPrivacy-first data pipelines for agile AI development
- BlogPrivacy by design in AI agent skills for production
- AI SkillsCLAUDE.md Template: Angular Material + FastAPI GDPR Ready App
- AI AgentsAI Agents for Privacy and GDPR Requests: Uses + Example
Before 13 May 2027
Compliance checklist
Choose the contact person or DPO
Name a DPO or a person able to answer processing questions on the fiduciary's behalf.
Rule 9
Create a role-based privacy mailbox
Use a durable mailbox rather than an individual's personal inbox.
Rule 9
Publish prominently on website and app
Show the contact in the footer, privacy notice and app settings.
Rule 9
Add the contact to every rights response
Embed it in acknowledgements, fulfilment, refusal and closure templates across all channels.
Rule 9
Add the contact to breach notices
Include business contact details of a person able to respond in every Data Principal breach message.
Rule 7(1)(e)
Brief the contact
Give the contact an internal FAQ and escalation path so questions are actually answered.
Rule 9
Key dates
Rule 9 contact publication applies to every Data Fiduciary
Answers
Frequently asked questions
Is a Data Protection Officer mandatory under DPDP?
Is a Data Protection Officer mandatory under DPDP?
Only for Significant Data Fiduciaries, under section 10 of the DPDP Act. Every other Data Fiduciary must instead publish the business contact of a person able to answer questions about its processing, under Rule 9. No Significant Data Fiduciary had been notified as of this update.
Where must the DPDP privacy contact be published?
Where must the DPDP privacy contact be published?
Prominently on the Data Fiduciary's website or app, and in every response to a communication exercising Data Principal rights. Good practice is to show it in the footer, in the Rule 3 notice, in app settings and in every rights-response template.
What contact details does DPDP Rule 9 require?
What contact details does DPDP Rule 9 require?
Business contact information of the DPO, if applicable, or of a person who can answer questions about the processing on the fiduciary's behalf. The Rules do not define the fields; a role or name, a role-based email address and a postal address are a sensible minimum.
Does a small business need to comply with DPDP Rule 9?
Does a small business need to comply with DPDP Rule 9?
Yes. Rule 9 applies to every Data Fiduciary with no size threshold. A small business can meet it cheaply by naming a founder or manager as the contact, publishing a role-based email address and including it in replies to rights requests.
When does DPDP Rule 9 apply?
When does DPDP Rule 9 apply?
From 13 May 2027, together with the other operational rules under Rule 1(4). Publishing a contact earlier is harmless and gives time to test that the mailbox is monitored, that templates carry the contact, and that questions about processing are actually answered before the obligation becomes enforceable.
Can the privacy contact be outsourced?
Can the privacy contact be outsourced?
The Rules do not prohibit it, but the person must be able to answer on behalf of the Data Fiduciary about its processing. If a vendor handles first contact, make sure processing questions reach someone inside the organisation who knows the answers, and keep accountability with the fiduciary.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 9 (official text)
- Digital Personal Data Protection Act, 2023 — Section 8(9) (official text)
- Digital Personal Data Protection Act, 2023 — Section 10(2)(a) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 7(1)(e) (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- Templates & playbooksThe Data Protection Officer Under DPDP: Role and ResponsibilitiesWho must appoint a Data Protection Officer under DPDP, what the role requires under section 10 and the Rules, and how non-SDF organisations should staff the Rule 9 contact person.
- DPDP Rules 2025Data Principal Rights Under DPDP Rule 14The DPDP Act grants access, correction, erasure, grievance and nomination rights. Rule 14 sets how fiduciaries publish request channels, identifiers and a grievance period of up to 90 days.
- DPDP Rules 2025DPDP Grievance Redressal: The 90-Day Response RuleRule 14(3) requires every Data Fiduciary and Consent Manager to publish a grievance response period of no more than 90 days and to build systems that meet it, from 13 May 2027.
- DPDP Rules 2025Significant Data Fiduciary Obligations Under DPDP Rule 13Once notified, a Significant Data Fiduciary must run an annual DPIA and audit, report significant observations to the Board, vet its algorithms, and keep Government-specified data in India.
- DPDP Rules 2025DPDP Privacy Notice Requirements Under Rule 3Rule 3 sets the minimum content and form of a DPDP consent notice: standalone, plain language, itemised data, specified purposes and links to withdraw, exercise rights and complain.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.