Multilingual Privacy Notices Under DPDP: The 22-Language Question Answered

Buried in Section 5(3) of the DPDP Act 2023 is the requirement most compliance checklists skip: every Data Principal has the option to access your privacy notice "in English or any language specified in the Eighth Schedule to the Constitution". Here's what that means in practice, and what it doesn't.

What the Provision Actually Says

The operative words are worth quoting in full, because the count turns on them:

"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." — Section 5(3), DPDP Act 2023

Section 5(3) attaches to the notice obligation of Section 5(1): the notice that accompanies every consent request must give the customer the option to access it in English or an Eighth-Schedule language. Three things follow. First, English sits outside the Eighth Schedule and is named separately — which is why the correct answer to "how many other than English" is 22, not 21. Second, the choice of language belongs to the customer, not to you. Third, the obligation is about genuine accessibility — a notice the customer cannot read cannot produce the "informed" consent Section 6 demands.

Do You Really Need 22 Translations?

The pragmatic reading — and the one consistent with the Act's plain-language purpose — is that you must serve the languages your customers actually use. A Coimbatore retailer whose customers speak Tamil and English needs those two done well; maintaining a Bodo translation no customer will ever request does nothing for compliance in substance. What you cannot do is ignore the provision because translation is inconvenient: if a meaningful part of your customer base reads Hindi or Kannada, an English-only notice is a live gap.

The Operational Playbook

1. Identify your real language set. Two to four languages cover most SMB customer bases.
2. Translate the notice properly. Reviewed, plain-language translations — Rule 3's "clear and plain language" standard applies in every language you serve. Start from our notice-writing guide.
3. Serve the right version automatically. Detect or ask; don't make customers hunt for a language toggle buried in a footer.
4. Keep versions in sync. When the notice changes, every language version changes together — a stale translation is a wrong notice.
5. Record the language served. Your consent record should say which language the customer consented in — that's your accessibility evidence.

Why This Is the Provision Worth Taking Seriously

India transacts in Indian languages — voice notes, WhatsApp orders, counter conversations. The businesses that treat Section 5(3) as a checkbox will serve English legalese to customers who tap through it uncomprehending, and hold consent records that prove exactly that. The businesses that serve real multilingual notices get something better than compliance: customers who actually understood what they agreed to. That's the thesis behind EasyDP's multilingual notices — your customers' own Indian languages across web, WhatsApp and offline, with the language logged on every consent.

Serving each customer the right language by hand becomes difficult past a few hundred customers. It is one of the jobs DPDP compliance software should take over: the notice goes out in the language the customer reads, and the record shows which version they saw.