Data Protection Officer under the DPDP Act: who must appoint one
By Abhijeet Singh · Primary sources verified by dpdprules.orgPublished · Last reviewed 16 min read
Jump to sourcesWho must appoint a Data Protection Officer under the DPDP Act?
The short answer
Once section 10 is in force and subject to section 17, a Data Fiduciary or class notified as significant must appoint a Data Protection Officer. Section 10(2)(a) requires the individual to represent the Significant Data Fiduciary under the Act, be based in India, be responsible to its Board of Directors or similar governing body, and be the contact point for grievance redressal. Section 8(9) and Rule 9 separately require a Data Fiduciary, subject to section 17, to publish the business contact information of the officer, if applicable, or an alternative person who can answer processing questions, prominently on its website or app and in every rights response. Reading "if applicable" as the section 10 officer is this site's interpretation. Sections 17(1) and 17(2) disapply both duties for covered processing, but the text does not explain how relief tied to particular processing affects the appointment duty for the whole organisation where the same fiduciary also conducts other processing. Section 17(3) can disapply section 10 for notified Data Fiduciaries or classes; section 17(5) can temporarily disapply any provision for specified Data Fiduciaries or classes. At 26 October 2026, no designation notification was located in this site's registry, timeline or the 19 DPDP records within MeitY's 1,615 record enumeration. The eGazette was not checked, so this is not a certified negative. The duties commence on a computed 13 May 2027, interpretation until officially confirmed.

Search for Data Protection Officer guidance in India and you may find a job description borrowed from the GDPR. The DPDP Act uses a shorter list and gives the appointment duty to a separately notified group. It also creates a different publication duty for Data Fiduciaries generally. This article separates those duties, states the section 17 qualifications, and identifies which common GDPR assumptions do not appear in the Indian text.
The answer in 2 explanatory tiers
The labels below are this site's explanation. The Act does not call these groups tier 1 and tier 2.
| Question | Notified Significant Data Fiduciary | Data Fiduciary generally |
|---|---|---|
| Must appoint a Data Protection Officer? | Yes under section 10(2)(a), subject to section 17 | No general appointment duty appears in the Act or the Rules as corrected, checked on 26 October 2026 |
| What is required? | Appoint an individual who satisfies the 4 conditions in section 10(2)(a) | Publish the business contact information described in section 8(9), subject to section 17 |
| Where must the contact appear? | Prominently on the website or app, and in every rights response, under Rule 9 | The same 2 places, under Rule 9 |
| How does the group arise? | Central Government notification under section 10(1) | Data Fiduciary status under the Act |
| Schedule maximum | Entry 4 expressly names section 10, up to Rs 150 crore | This site reads section 8(9) and Rule 9 into residual entry 7, up to Rs 50 crore |
| In force? | No; computed 13 May 2027, interpretation until officially confirmed | No; computed 13 May 2027, interpretation until officially confirmed |
Every Schedule figure above is a maximum, not an automatic fine. Section 33 permits a penalty only after an inquiry, a determination that the breach is significant, and an opportunity for the person to be heard.
Section 17 sub sections (1) and (2) disapply sections 8(9) and 10 for the processing they cover. The Act does not explain how relief tied to particular processing affects an appointment duty for the whole organisation where the same fiduciary also conducts processing outside those routes; this site does not resolve that question. Section 17(3) can disapply section 10 for notified Data Fiduciaries or classes. Section 17(5) can temporarily disapply any provision for specified Data Fiduciaries or classes. The section 17 exemptions guide works through those routes separately.
Section 2(z) defines a Significant Data Fiduciary as a Data Fiduciary or class notified by the Central Government under section 10. There is no fixed threshold to compute. At 26 October 2026, no designation notification was located in this site's registry or timeline or among the 19 DPDP records in MeitY's 1,615 record library enumeration. The eGazette was not checked, so this is a bounded search finding and not a certified negative. Section 10(2)(a) has not commenced either. How notification works, and what else it brings, is set out in what changes if you are notified and the Significant Data Fiduciary obligations guide.
What section 10(2)(a) actually requires
Subject to section 17, the appointment duty is 1 clause with 4 limbs. Section 10(2)(a), on Gazette page 9, says the officer shall:
- "represent the Significant Data Fiduciary under the provisions of this Act";
- "be based in India";
- "be an individual responsible to the Board of Directors or similar governing body of the Significant Data Fiduciary"; and
- "be the point of contact for the grievance redressal mechanism under the provisions of this Act".
Read the limbs one at a time, because each is doing precise work.
Represents the fiduciary. Limb (i) says the officer represents the Significant Data Fiduciary under the Act. The text does not say that the officer represents the Data Principal or the regulator.
Based in India. The expression "based in India" is used twice in the Act, here and in section 17(1)(d). Neither the Act nor the Rules states an express residency test, citizenship test or minimum number of days for the expression, verified on 26 October 2026. Its precise meaning is left open.
An individual responsible to the governing body. Limb (iii) rules out a firm, committee or mailbox as the appointed officer because the officer must be an individual. It also names responsibility to the "Board of Directors or similar governing body" of the Significant Data Fiduciary. That is the organisation's own body, not the Data Protection Board of India. Rule 13(2) separately refers to a report from the person carrying out the assessment and audit; it does not assign that report to the officer.
Point of contact for grievance redressal. Limb (iv) wires the officer into the grievance machinery. Subject to section 17, section 8(10) requires a Data Fiduciary to establish an effective grievance redressal mechanism. Section 13 gives the Data Principal a right to readily available redressal and requires her to exhaust it before approaching the Board. Rule 14(3) names 90 days in a sentence that lost its object at notification, so the capped period has to be read from the rest of the sub rule. Section 13 itself names no officer; the connection is made from the section 10 end, and only for a notified fiduciary. The mechanics are covered in the grievance redressal guide.
That is the entire officer clause. S.O. 5458(E), made on 5 October 2026 and printed under the Gazette masthead dated 6 October 2026, changed section 10(2)(c)(ii) from "audit" to "data audit". It did not amend section 10(2)(a).
The separate contact publication duty
Section 8(9) states a general obligation of a Data Fiduciary, but section 17 can disapply it for the processing or class covered by a listed route. Section 8(9) says:
"A Data Fiduciary shall publish, in such manner as may be prescribed, the business contact information of a Data Protection Officer, if applicable, or a person who is able to answer on behalf of the Data Fiduciary, the questions, if any, raised by the Data Principal about the processing of her personal data."
Section 8(9) of the DPDP Act 2023, Gazette page 8.
Three things follow from that sentence. First, the obligation is not limited to a Significant Data Fiduciary, although section 17(1), section 17(2) and section 17(5) can disapply it. Second, the words "if applicable" support the explanatory split above. Section 2(l) defines a Data Protection Officer as "an individual appointed by the Significant Data Fiduciary under clause (a) of sub-section (2) of section 10". This site therefore reads a fiduciary that has not been notified as publishing the alternative contact. That reading is interpretation rather than printed text. Section 2 also begins with "unless the context otherwise requires", so the definition does not conclusively resolve every possible use of the term.
Third, section 8(9) says "publish", not "appoint". This site reads it as requiring publication of a contact who can answer questions, without creating a separate officer appointment duty, title or qualification standard. For planning, a named person and a monitored business contact can meet that function without being described as a statutory appointment.
The manner of publication is not left open. Section 40(2)(h) gives the Central Government power to prescribe "the manner of publishing the business contact information of a Data Protection Officer under sub-section (9) of section 8", and Rule 9 exercises it in 1 sentence:
"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."
Rule 9 of the DPDP Rules 2025, Gazette page 27.
So the duty has 2 places. Prominent publication on the website or app may be satisfied through a suitably visible privacy page; a buried reference might not be prominent. Every response to a communication for exercising a Data Principal's rights must also carry the business contact information.
Rule 9 prescribes the publication manner. It does not address appointment, qualifications or position.
Where the contact person shows up elsewhere
The contact function appears across 5 provisions in closely similar but not identical words. That is a practical reason to settle who answers each channel early.
| Provision | Gazette page | What it requires |
|---|---|---|
| Section 6(3) | 5 | every request for consent must provide "the contact details of a Data Protection Officer, where applicable, or of any other person authorised by the Data Fiduciary to respond" to rights communications |
| Section 8(9) | 8 | publish the business contact information of the officer, if applicable, or a person able to answer processing questions |
| Rule 9 | 27 | the manner: prominently on the website or app, and in every rights response |
| Rule 7(1)(e) | 26 | every intimation of a personal data breach to an affected Data Principal must include the business contact information of "a person who is able to respond on behalf of the Data Fiduciary, to queries" |
| Second Schedule, item (g)(i) | 35 | for processing under section 7(b), the intimation to the Data Principal must give the business contact information of a person able to answer processing questions |
Two patterns are worth noticing. Rule 7(1)(e) and the Second Schedule both name a person rather than an officer, so the breach notice and the section 7(b) intimation do not depend on Significant Data Fiduciary status. Section 6(3) follows the same drafting pattern as section 8(9): the officer first, "where applicable", with an authorised person as the alternative.
The GDPR habits that do not carry
If your privacy programme grew up on Articles 37 to 39 of the GDPR, compare its assumptions carefully. The GDPR column below is a brief orientation to the official OJ text of those articles, read in full on 26 October 2026. The DPDP column is verified against the Gazette texts of the Act, the Rules as corrected, and S.O. 5458(E) on the same date.
| GDPR DPO habit | What the DPDP text says |
|---|---|
| The designation cases cover public authorities except courts acting judicially, core activities involving regular and systematic monitoring on a large scale, and core activities involving large scale processing of Article 9 data or Article 10 criminal conviction and offence data | The appointment duty depends on a section 10 notification, subject to section 17. At 26 October 2026, no designation notification was located on the bounded surfaces described above |
| The officer must have expert knowledge of data protection law and practices | No qualification, certification, experience or expertise standard appears in the Act or the Rules, verified 26 October 2026 |
| The officer must be independent, must not be instructed on how to perform the role, and must not be dismissed or penalised for performing it | The DPDP text contains none of those protections. It separately says that the officer represents the Significant Data Fiduciary |
| The officer must not hold a position causing a conflict of interest | No conflict of interest rule for the officer appears in the Act or Rules. The framework does impose conflict rules on Consent Managers in items 9 and 10 of Part B of the First Schedule and on Board Members in item 8(1) of the Fifth Schedule, verified 26 October 2026 |
| The officer reports to the highest management level | Section 10(2)(a)(iii) names one destination and is silent about everything else: an individual responsible to the Board of Directors or similar governing body. Reading that as excluding any other reporting line is this site's construction, not printed words |
| The officer may be a staff member or engaged under a service contract | Silent. The text requires an individual and says nothing about employment, secondment or engagement, so the question is open |
| Contact details are communicated to the supervisory authority | No filing, registration or intimation of the officer's identity to the Data Protection Board of India appears in either text, checked on 26 October 2026. Section 8(9) and Rule 9 require publication, while section 6(3) requires contact details in every consent request |
| The officer's location is a practical arrangement | "be based in India" is in the operative words of section 10(2)(a), the only geography condition in the clause |
| The officer owns the impact assessment | Section 10(2) creates the officer, the independent data auditor and the assessment as parallel duties. S.O. 5458(E) changes the Act to "periodic data audit". Rule 13 still says "assessment and audit" and refers to the person carrying them out, not the officer. See DPIA under the DPDP Act |
As a site synthesis, the GDPR text protects independence while the DPDP text specifies representation and responsibility to the governing body. An organisation may choose stronger internal safeguards, but should not describe them as requirements printed in the DPDP Act or Rules.
What the text does not say
Stated as dated absences, these points were verified against the full Gazette texts of the Act and the Rules as corrected, plus S.O. 5458(E), on 26 October 2026. The expression "Data Protection Officer" appears 5 times in the Act, on Gazette pages 2, 5, 8, 9 and 18, and once in the English Rules, in Rule 9 on page 27. Across those 6 appearances there is:
- No qualification standard. Not a certification, not a number of years, not a field of study.
- No independence, tenure or dismissal provision. The text does not prescribe tenure or a dismissal rule for the officer.
- No conflict of interest rule, in contrast to the Consent Manager and Board Member provisions in the Rules.
- No periodicity for the officer. Rule 13 fixes a 12 month cycle, but it fixes it for the Data Protection Impact Assessment and the audit. Rule 13 does not mention the officer at all, and attributing an annual duty to the officer through section 10 is a mistake to avoid.
- No registration or intimation duty. Nothing tells the Data Protection Board who your officer is.
- No prescribed reporting line other than the governing body. Clause (h) of section 40(2) reaches the manner of publishing contact information, and no clause from (a) to (y) names section 10(2)(a), while clauses (k) and (l) expressly serve section 10(2)(c). That drafting difference corresponds to Rule 13 addressing the assessment and audit but not the officer. Whether section 40(1) or residual clause (z) could support future officer rules is outside this dated absence finding.
- No alternative title rule. The expressions "Grievance Officer", "privacy officer", "nodal officer" and "compliance officer" appear nowhere in either text. That absence neither requires nor forbids overlap with another role created under a different law.
Absences are not invitations to fill a gap and call the result law. A proposed officer charter can be measured against the 4 requirements in section 10(2)(a); additional qualifications, protections and job terms are organisational choices rather than requirements in that clause.
The numbers attached to getting it wrong
These are Schedule maxima, not automatic fines. Under section 33(1), the Board may impose a Schedule penalty only after an inquiry, a determination that the breach is significant, and an opportunity for the person to be heard. Section 33(2) then lists the matters relevant to the amount.
| What is breached | Where the Schedule puts it | Cap |
|---|---|---|
| Failing the section 10 duties, including the officer, auditor, assessment and data audit duties | entry 4, named expressly | up to Rs 150 crore |
| Failing to publish the contact under section 8(9), or failing the Rule 9 manner | entry 7, breach of any other provision of the Act or the rules | up to Rs 50 crore |
The Schedule, printed on Gazette page 21 under the reference to section 33(1), names sections 8(5), 8(6), 9, 10, 15 and section 32 undertakings in entries 1 to 6. Entry 7 covers a breach of any other provision of the Act or Rules and carries a maximum of Rs 50 crore. Section 8(9) is not named in a specific entry, so mapping section 8(9) and Rule 9 to entry 7 is this site's interpretation.
When any of this starts
The appointment and publication duties are not in force yet, but the definition of Data Protection Officer is in force.
Paragraph (a) of notification G.S.R. 843(E) brought section 2 into force on its date of publication. This site uses the printed Gazette masthead date, 13 November 2025, as the computation basis. That calendar date is interpretation until officially confirmed. Whichever of the 13 or 14 November date readings is used, section 2 is already in force.
Paragraph (c) of the same notification puts sections 7 to 10 and sections 11 to 17 in the group that commences 18 months from publication. Rule 1(4) puts Rules 3, 5 to 16, 22 and 23 in the matching 18 month group. This site computes 13 May 2027 from the printed masthead. That calendar date is interpretation until officially confirmed because the official texts state a period, not the resulting date. An alternative day count could move the result by up to 2 days. S.O. 5458(E) corrects audit wording but does not change this commencement period. The full sequence is on the timeline.
The status at 26 October 2026 is therefore limited and conditional. Section 10(2)(a) is not in force. Once it is in force, a notified Significant Data Fiduciary is subject to the appointment duty, subject to section 17 and the unresolved question about relief tied to particular processing described above. No designation notification was located on the bounded surfaces described above; the eGazette was not checked.
Should you appoint one anyway?
Offered as this site's recommendation, not as law, and split by which tier you expect to be in.
If you do not expect notification, designate a contact person, publish business contact information that a real human monitors, and put that contact into your consent requests, rights response template and breach notification template. Using a plainer title can reduce confusion because section 2(l) defines Data Protection Officer by reference to section 10(2)(a). The Act and Rules do not prohibit another title choice, so this is a clarity recommendation, not a legal rule.
If notification looks plausible, assess all 6 factors in section 10(1): volume and sensitivity, risk to Data Principal rights, potential impact on sovereignty and integrity, risk to electoral democracy, security of the State, and public order. There is no fixed threshold. As a planning recommendation, build a reporting path to the governing body and identify an individual who can satisfy all 4 limbs of section 10(2)(a).
What to do now
Confirm what you are with the role tool, then generate your obligation set with the company compliance plan. It presents contact publication as a general Data Fiduciary action, subject to applicable section 17 routes, and the Significant Data Fiduciary cycle as a conditional action. The official texts live at section 8, section 10, Rule 9 and Rule 13, each with its Gazette citation. The compliance and data protection officers guide covers the rest of what the compliance function usually owns.
Related tool
Role and Actor Checker
Work out your likely role for a processing activity, such as Data Fiduciary or Data Processor.
Open
Related tool
Compliance Plan
Generate 1 company level action plan and see the work for your role first.
Open
Section 10, official text →Section 8, official text →Rule 9, official text →Rule 13, official text →Additional obligations of a Significant Data Fiduciary: DPO, auditor, DPIA →Significant Data Fiduciary: what changes if you are notified →DPIA under the DPDP Act →
Data Protection OfficerSection 10Rule 9Significant Data FiduciaryGDPR comparison