Skip to main content

The 3rd and main DPDP commencement date is computed as 13 May 2027, which is interpretation until officially confirmed.

Sources last verified on 28 October 2026. Methodology

DPDP notice languages: does section 5(3) require 22 versions?

Notice

By · Primary sources verified by dpdprules.orgPublished · Last reviewed 11 min read

Jump to sources

Does the DPDP notice have to be in 22 languages?

The short answer

No; section 5(3) is not in force and does not say to publish 22 notice versions up front. It says the Data Fiduciary must give the Data Principal the option to access the notice in English or any language specified in the Eighth Schedule to the Constitution. On this site's reading, that means readiness to provide the notice in the listed language the individual chooses; the Data Fiduciary cannot replace the individual's option with its own language choice. Section 6(3) gives the same option for each consent request, and Rule 3 sets the notice quality requirements. These duties are not universal. Section 17 can disapply section 5 and section 6(3) for particular processing, remove the Act for listed processing, or support a notification removing named provisions. Neither instrument expressly makes consent automatically invalid solely because the person could not read the notice. Where the option applies, this site interprets a breach of section 5(3) or section 6(3) as falling within residual Schedule entry 7, not the 250 crore entry for section 8(5). A penalty still requires the section 33 process. Section 5, section 6(3), section 17 and Rule 3 are not in force. The first computed date is 13 May 2027 and official publication records plus counting uncertainty could move it as late as 15 May 2027. Both dates are interpretation until officially confirmed.

More answered questions →

Diagram: Section 5(3): the language option belongs to the person. The same diagram appears further down this article, where it is described in full.

A claim keeps appearing in vendor decks and compliance blogs: DPDP notices "must be presented in English or any of the 22 languages", or bluntly, "your privacy notice has to be in 22 languages". The actual provision says something narrower and more interesting, and the difference decides whether you are running a translation readiness programme or a 22 language publishing project.

What section 5 requires before the language question arises

Section 5(1) requires that every request for consent under section 6 be accompanied or preceded by a notice from the Data Fiduciary telling the Data Principal 3 things: the personal data and the purpose for which it is proposed to be processed, the manner in which she may exercise her rights under section 6(4) and section 13, and the manner in which she may complain to the Data Protection Board. Section 5(2) extends this to consent collected before the Act commences: a comparable notice must go out as soon as reasonably practicable, and processing may continue unless and until consent is withdrawn.

That is the notice. Then comes the subsection everyone paraphrases.

The language subsection, verbatim

DPDP Act 2023, s. 5(3) · Notice · verbatim

"The Data Fiduciary shall give the Data Principal the option to access the contents of the notice referred to in sub-sections (1) and (2) in English or any language specified in the Eighth Schedule to the Constitution."

Read it slowly, because every word is doing work.

Whose option it is. The duty on the Data Fiduciary is to give the Data Principal the option. The choice of language belongs to the individual reading the notice, not to the organisation writing it. A fiduciary that publishes its notice in English alone and calls that "English or any of the 22 languages, and we picked English" has inverted the sentence.

What the option covers. The option is to access the contents of the notice. The person must be able to read what the notice says, in full, in the language they opt for. It is an access guarantee attached to the notice contents, not a formatting instruction about how the notice is first presented.

What it does not say. The text does not say the notice must be presented in every listed language simultaneously, and it does not say the fiduciary may satisfy the provision by choosing any one language from the list. Where the duty applies, the practical reading is this: whichever listed language a Data Principal opts for, you must be able to serve the notice contents in that language.

Where the number 22 comes from

The DPDP Act and the DPDP Rules never state a number. The words are "in English or any language specified in the Eighth Schedule to the Constitution", full stop. The Legislative Department Constitution print consolidated as on 1 May 2024 numbers the Schedule entries 1 to 22 on printed pages 325 to 326, which are PDF pages 356 to 357, and closes at Urdu. That is a count in that dated print, not a claim about the current whole Schedule. A 9 March 2026 record shows that Mizo inclusion was still being sought on that date, but it cannot establish whether any other amendment occurred. This repository held no later consolidated Constitution print when the source chain was checked on 28 October 2026. The legal anchor is the reference to the Schedule, so the safer implementation reads the live constitutional list instead of hardcoding 22.

Section 6(3) requires every request for consent to be presented in clear and plain language, "giving her the option to access such request in English or any language specified in the Eighth Schedule to the Constitution", together with the contact details of a Data Protection Officer where applicable or another authorised contact. Where both provisions apply, the language capability is used twice: once for the section 5 notice and once for the consent request itself.

Rule 3 sets the quality bar in every language

Rule 3 says the notice must be presented and understandable independently of other information and must give, in clear and plain language, a fair account of the details needed for specific and informed consent. At minimum, that account includes an itemised description of the personal data and specified purposes with a specific description of the goods, services or uses enabled. It must also give the communication link and other means to withdraw consent with comparable ease, exercise rights and complain to the Board.

Nothing in Rule 3 is English only. Where Rule 3 applies, a translated notice that drops the itemised data description, compresses the purposes, or loses the withdrawal link does not meet the same content requirements as the English version. Translation is not summarisation.

Check section 17 before treating the option as universal

The option is broad, but it is not universal. Section 17(1) disapplies most of Chapter II for 6 categories of processing, so sections 5, 6(3) and 8(4) do not apply to that processing. Section 17(2) disapplies the Act for 2 further categories. Section 17(3) can support a notification removing section 5 and certain other named provisions for specified classes, but it does not name section 6(3). Section 17(5) can support a time limited notification declaring any provision inapplicable to a Data Fiduciary or class. Read the routes separately in the section 17 exemptions guide and the official section 17 text.

Section 17 names provisions of the Act, not Rule 3. The effect of an Act exemption on that separate Rule is therefore an interpretation question, not something this page presents as official text. First identify the processing and applicable exemption route; then decide which notice and consent duties remain.

Practical recommendation for an app or a website

Where the option applies, a language selector on notice and consent screens, or honouring the account or device language with a visible way to switch, is a practical mechanism. Keep the notice as structured content so that when a purpose changes, every language version updates together. This is implementation advice, not wording found in the Act.

Which languages to prepare first is a business call. Where section 5(3) applies, plan the pipeline so it can eventually serve the full constitutional list, while sequencing the work by the languages users actually read. That sequence is a recommendation, not an official requirement. The provision ranks no language; it gives the individual the option.

The vendor phrasing, corrected politely

"Must be presented in English or any of the 22 languages" is an understandable compression, but it makes 2 quiet substitutions: it turns give the option to access into present, and it hands the choice implied by "or any" to the fiduciary instead of the Data Principal. The stronger variant, "must be in 22 languages", overshoots in the other direction by inventing a simultaneous publication duty. Compliance planning should run on the words: give each person the option, and be ready to honour whichever language they pick.

Diagram headed "Section 5(3): the option belongs to the Data Principal". It quotes the subsection from Gazette issue No. 25 at page 5 and shows that the duty is to give the option to the Data Principal. Where the duty applies, this site's reading is readiness to serve the notice contents in whichever listed language the person opts for, not every version up front and not a single language picked by the Data Fiduciary. It contrasts 2 vendor compressions that are not in the text. A section 17 panel says section 17(1) can disapply sections 5 and 6(3) for particular processing, section 17(2) can disapply the Act, notification routes differ, and the effect on Rule 3 remains interpretation. A status band records that, as at 28 October 2026, sections 5, 6(3), 17 and Rule 3 are not in force. Their 18 month groups have a first computed date of 13 May 2027 and a latest candidate of 15 May 2027, both interpretation until officially confirmed. The footer says the instruments state no number and that 22 comes from the Constitution print consolidated as on 1 May 2024, not a current whole Schedule count.

Open the full size language option diagram.

What happens if the option is not given

Where the option applies, neither instrument attaches an automatic consequence to a language failure. They do not expressly say that a notice a person cannot read makes consent invalid by itself or that the failure carries the headline cap of 250 crore rupees. Here is what the text does say.

The 250 crore figure belongs to a different duty. Section 33(1) lets the Board impose "such monetary penalty specified in the Schedule", and the Schedule is a table of 7 entries. The 250 crore entry is entry 1, and it names 1 thing: failing to take reasonable security safeguards to prevent personal data breach under section 8(5). Entry 2 names section 8(6), entry 3 section 9, entry 4 section 10, entry 5 section 15, and entry 6 breach of any term of a voluntary undertaking accepted by the Board under section 32. Neither section 5(3) nor section 6(3) appears anywhere in entries 1 to 6, which leaves the residual entry:

DPDP Act 2023, The Schedule · verbatim

"7. Breach of any other provision of this Act or the rules made thereunder. May extend to fifty crore rupees."

Entry 7 of the Schedule to the DPDP Act 2023, quoted from the Gazette table on page 21. The India Code print was used only to cross check the row association.

Where the underlying duty applies, reading a language failure into residual entry 7 is this site's inference from the table structure, not a mapping the Gazette prints. The same reading applies if the failure is characterised as a section 8(4) breach, because the Schedule names only sections 8(5) and 8(6) elsewhere. A Rule 3 breach also reaches the residual wording. Every stated amount says "May extend to", so it is a ceiling and not a tariff. Section 17 must be checked first because an exemption can remove the underlying Act duty.

A penalty is not automatic, and it is not the first step. Before a Data Principal approaches the Board, section 13(3) requires her to exhaust the grievance opportunity under section 13. Section 27(1)(b) then permits a complaint about a Data Fiduciary breach relating to her personal data or rights. A government reference and a court direction are separate alternatives under that clause, not steps after the individual's grievance route. Section 28(3) requires the Board to decide whether sufficient grounds exist for an inquiry, and section 28(4) permits closure with written reasons if they do not. Money arrives only after section 33(1): the inquiry must conclude, the Board must determine that the breach is significant, and the person must have an opportunity to be heard. Section 33(2) lists 7 factors for the amount. The full machinery is in how a complaint becomes an order and an appeal, and the caps are in the penalties article.

No provision expressly makes consent invalid merely because a person could not read the notice. Section 6(2) is the provision that expressly uses invalidity, and it runs a different test:

DPDP Act 2023, s. 6(2) · Consent · verbatim

"Any part of consent referred in sub-section (1) which constitutes an infringement of the provisions of this Act or the rules made thereunder or any other law for the time being in force shall be invalid to the extent of such infringement."

Section 6(2) of the DPDP Act 2023.

2 things follow from the words. The subject is a part of consent, and the operation is limited to the extent of the infringement. The Act's illustration gives the example of consent to insurance processing plus a waiver of the right to complain; the waiver part is invalid. The subsection does not expressly make unreadability an automatic validity switch.

Where comprehension does bear. On this site's reading, section 6(1) matters because informed is one of the stated qualities of consent, and the section 5 notice is the Act's mechanism for informing. Section 2(za) also defines a specified purpose by reference to a notice given in accordance with the Act and Rules. Neither provision states the result of a notice the person could not read, so this remains interpretation. Section 6(10) gives the issue practical force: if consent is the processing basis and a question arises in a proceeding, "the Data Fiduciary shall be obliged to prove that a notice was given" and that consent was given in accordance with the Act and Rules. Where the language option applied, its absence would be part of that proof question. The exposure is evidential, not an automatic statutory switch.

None of it is live yet, and it starts when the duty does. Section 13, section 27 except section 27(1)(d), and sections 28 to 34 sit in the same 18 month commencement group as sections 5, 6(3) and 17. The grievance, complaint, inquiry and penalty machinery therefore starts with the duties discussed here. Whether the Board is operational is a separate question this site tracks.

When this bites

Sections 5, 6(3), 13 and 17 sit in the 18 month group of notification G.S.R. 843(E) paragraph (c). Rule 3 sits in the 18 month group of Rule 1(4). The first computed date is 13 May 2027 from the printed masthead date. The official file code and listing use the next day, and the instruments do not state how the period is counted, so the latest candidate is 15 May 2027. Both dates are interpretation until officially confirmed. The evidence is set out in the 13 or 14 November question. Because translation and review take time, beginning before the official date is confirmed is practical risk reduction, not a statutory requirement.

What to do

Draft the master notice with the privacy notice generator; it assembles the Rule 3 elements from your inputs so translations start from a complete skeleton. Then run your current notice, and the structure of each translated version, through the privacy notice checker, which maps every gap to the exact provision. The official texts live at Section 5 and Rule 3. Notice content is usually drafted by legal, and the legal and privacy counsel guide sets out what else tends to land there.

Section 5, official text →Rule 3, official text →What must a DPDP privacy notice contain? →Section 17 exemptions explained →

Privacy noticeLanguagesSection 5Eighth Schedule to the Constitution

Share this: