Templates & playbooksUpdated 22 November 20269 min read

The Data Protection Officer Under DPDP: Role and Responsibilities

Who 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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Who must appoint
Significant Data Fiduciaries only
Legal basis
Section 10(2)(a), DPDP Act
Location
Based in India
Reports to
Board of directors or similar governing body
Non-SDF requirement
Publish a contact person (Rule 9)
SDFs notified so far
None

Quick answer

Under the DPDP Act, only a Significant Data Fiduciary must appoint a Data Protection Officer. Section 10(2)(a) requires the DPO to represent the SDF, be based in India, be responsible to its board of directors or similar governing body, and be the point of contact for grievance redressal. Every other Data Fiduciary must instead publish a contact person under Rule 9. No SDF has yet been notified.

  • A DPO is mandatory only for Significant Data Fiduciaries, once notified under section 10.
  • The SDF's DPO must be based in India and responsible to the board of directors or similar governing body.
  • Every Data Fiduciary must publish a contact person's business details on its website or app under Rule 9.
  • The contact must also appear in every response to a rights request.
  • A DPO is distinct from the independent data auditor that an SDF must also appoint.
  • Organisations likely to be notified as SDFs should design the DPO role now.

Who this is for: Boards and company secretaries, Chief privacy and compliance officers, General counsel, HR leaders hiring privacy roles, Organisations likely to be designated SDFs

Who needs a Data Protection Officer under DPDP?

Only a Significant Data Fiduciary (SDF). Section 10(1) allows the Central Government to notify a Data Fiduciary or class of Data Fiduciaries as SDFs on the basis of factors including the volume and sensitivity of personal data processed, risk to the rights of Data Principals, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State and public order.

Once notified, section 10(2) requires the SDF to:

  • appoint a Data Protection Officer;
  • appoint an independent data auditor to evaluate compliance;
  • undertake periodic Data Protection Impact Assessments, periodic audits and other measures.

No SDF has been notified at the time of writing. When notifications are issued, Rule 13 obligations, including the annual DPIA and audit, run from the date of notification.

What everyone else needs

Ordinary Data Fiduciaries have no obligation to appoint a DPO. Section 8(9) and Rule 9 require them to publish the business contact information of a person who is able to answer, on behalf of the Data Fiduciary, the questions of the Data Principal about processing of her personal data. Many organisations will still choose to create a DPO-style role for governance reasons, and that is sensible, but it is a choice, not a legal requirement.

What does the Act require of an SDF's DPO?

Section 10(2)(a) sets four requirements for the DPO of a Significant Data Fiduciary.

RequirementWhat it means in practice
Represents the SDF under the ActThe DPO is the organisation's face on data protection matters, including with the Board and Data Principals
Based in IndiaThe role cannot be held by someone located abroad, which matters for global groups with a regional privacy lead elsewhere
Individual responsible to the board of directors or similar governing bodyReporting line to the board, not buried under a business unit head
Point of contact for the grievance redressal mechanismGrievances under section 13 route to or through the DPO

What the Act does not specify

The Act and Rules do not prescribe qualifications, tenure, protection from dismissal, or whether the role can be combined with others. They also do not require registration of the DPO with the Board. Organisations should set these internally, with an eye to independence: a DPO who also owns the processing being reviewed will struggle to challenge it.

Publication

Rule 9 requires an SDF to publish its DPO's business contact information prominently on its website or app and in every response to a rights request.

What does a DPO actually do?

The Act sets the minimum; the job is broader. A workable DPO mandate for an SDF covers:

Governance

  • Report to the board at least quarterly on compliance status, incidents, DPIA findings and audit observations.
  • Own the data protection policy framework and approve exceptions.
  • Advise on new products, vendors and data uses before launch.

Assessments and audits

  • Run or oversee the annual DPIA required by Rule 13(1).
  • Coordinate with the independent data auditor, whose report of significant observations must be furnished to the Board under Rule 13(2).
  • Oversee the algorithmic due diligence in Rule 13(3), checking that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights.
  • Track any data the Government specifies under Rule 13(4) that must not leave India.

Operations

  • Be the point of contact for grievances and supervise response within the published period, not exceeding 90 days under Rule 14(3).
  • Lead breach decisions with security and legal, including Rule 7 intimations.
  • Act as liaison with the Data Protection Board in inquiries.

Culture

Train staff, run awareness campaigns and keep a channel open for employees to raise concerns.

The Rule 9 contact person for everyone else

Rule 9 is short but applies to every Data Fiduciary from 13 May 2027. It requires:

  1. Prominent publication on the website or app of the business contact information of the DPO, if applicable, or of a person able to answer the Data Principal's questions about processing of her personal data.
  2. Inclusion in every response to a communication for the exercise of rights under the Act.

Choosing the person

  • Someone who can actually answer questions or route them accurately: a privacy lead, compliance manager, legal counsel or, in a small business, the owner.
  • A role-based mailbox, for example a privacy address on your domain, with a named owner and backup, so the contact survives staff changes.
  • A phone number or form in addition to email, if your users are less likely to use email.

Common mistakes

  • Publishing a generic support address with no privacy routing.
  • Listing a person who has left the company.
  • Hiding the contact in the footer of a long policy rather than displaying it prominently.
  • Omitting it from automated responses to deletion or access requests.

See publishing the contact person and DPO.

Designing the DPO role: independence, resourcing and structure

For organisations expecting SDF designation, or choosing a DPO voluntarily, these design choices matter more than the job title.

Design choiceRecommendation
Reporting lineDirect line to the board or a board committee, with administrative reporting to the CEO or General Counsel
ConflictsAvoid combining with heads of marketing, product, IT or security, whose decisions the DPO must review
LocationIn India, as section 10(2)(a) requires for SDFs
TeamPrivacy counsel, privacy engineer, DPIA analyst, rights operations
BudgetRing-fenced for tooling, audits and training
EscalationWritten right to escalate to the board without filtering
Group structureA group privacy lead abroad can coordinate, but the India DPO holds the statutory role

DPO versus CISO

The CISO protects systems; the DPO protects people's rights in their data. Security incidents overlap, but a DPO also handles notices, consent, purpose limitation, children's data and rights requests. Keeping the roles separate preserves a useful tension.

Outsourced DPOs

The Act requires the DPO to be an individual based in India responsible to the board. Whether an external individual can meet that standard is not addressed in the Rules; organisations considering it should take advice.

What to do before 13 May 2027

If you could be notified as an SDF

  • Assess your exposure against the section 10(1) factors: volume and sensitivity of data, risk to rights, and the public-interest factors.
  • Identify a DPO candidate based in India, define the mandate, and get board approval for the reporting line.
  • Prepare the DPIA method and audit scope so the first Rule 13 cycle can start soon after notification. See SDF obligations.

For every other organisation

  • Name the Rule 9 contact person and a deputy.
  • Publish the contact prominently on the website and in the app's settings or help pages.
  • Add the contact block to all rights-response templates and automated emails.
  • Train the contact on the Act's rights, grievance timelines and the escalation route to the Board.

For groups with an EU DPO

A GDPR DPO can coordinate Indian compliance, but if the Indian entity becomes an SDF, the statutory DPO must be based in India. Plan for a local appointee rather than extending the EU role.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Assess SDF likelihood

    Evaluate your processing against the section 10(1) factors and document the result.

    Section 10(1)

  2. Name a Rule 9 contact person

    Choose someone who can answer processing questions, plus a deputy.

    Rule 9

  3. Publish the contact prominently

    Display business contact information on the website and in the app.

    Rule 9; s.8(9)

  4. Include the contact in every rights response

    Add the contact block to templates and automated replies.

    Rule 9

  5. Draft a DPO mandate if SDF designation is likely

    Define duties, reporting line to the board, independence and resources.

    Section 10(2)(a)

  6. Locate the DPO in India

    Ensure the statutory DPO for an SDF is based in India.

    Section 10(2)(a)

  7. Separate DPO and independent auditor roles

    Appoint an independent data auditor distinct from the DPO.

    Section 10(2)(b)

  8. Prepare the annual DPIA and audit cycle

    Set method, scope and timing to start after notification.

    Rule 13(1)

Answers

Frequently asked questions

Is a Data Protection Officer mandatory under the DPDP Act?

Only for Significant Data Fiduciaries. Section 10(2)(a) requires an SDF, once notified by the Central Government, to appoint a DPO. Other Data Fiduciaries must publish the business contact information of a person who can answer questions about processing, under section 8(9) and Rule 9, but need not appoint a DPO.

Does the DPO have to be in India?

Yes, for a Significant Data Fiduciary. Section 10(2)(a) requires the DPO to be based in India, to represent the SDF under the Act, to be responsible to the board of directors or similar governing body, and to be the point of contact for the grievance redressal mechanism.

Can our CISO be the DPO?

The Act does not prohibit it, but it creates conflicts. The DPO must review decisions about data use and security that the CISO makes. For an SDF, separate roles with a direct DPO line to the board are the stronger design. For a non-SDF contact person, a combined role is more acceptable.

What is the difference between a DPO and the Rule 9 contact person?

A DPO is a statutory role for Significant Data Fiduciaries with defined requirements in section 10(2)(a). The Rule 9 contact person is any individual able to answer Data Principals' questions about processing on behalf of the fiduciary, required of every Data Fiduciary. Both must be published prominently and included in rights responses.

Has any company been notified as a Significant Data Fiduciary?

Not at the time of writing. The Act allows the Central Government to notify SDFs based on factors such as volume and sensitivity of data and risk to rights. Organisations processing large volumes of sensitive data should prepare, because Rule 13 duties start from the date of notification.

Do I need to register my DPO with the Data Protection Board?

The Act and Rules do not require registration of a DPO with the Board. They require publication of the DPO's or contact person's business contact information on the website or app and in every response to rights requests. Check for any later Board guidance before 13 May 2027.

Legal references and sources

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

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.