Consent in Every Indian Language

A consent notice that a person cannot read is not a notice. It is a formality that happens to sit above a checkbox. Most conversations about consent in India focus on what the notice must say: the purpose, the data items, the retention period. Fewer focus on the condition that makes any of that matter — the person receiving it has to be able to understand it in the first place.

The DPDP Act addresses this directly. A data principal is entitled to access the notice in English or in any language specified in the Eighth Schedule to the Constitution. That entitlement is part of what makes consent valid.

What the Act asks for

The Eighth Schedule lists 22 languages: Assamese, Bengali, Bodo, Dogri, Gujarati, Hindi, Kannada, Kashmiri, Konkani, Maithili, Malayalam, Manipuri, Marathi, Nepali, Odia, Punjabi, Sanskrit, Santali, Sindhi, Tamil, Telugu, and Urdu. Together with English, that is the full set of languages in which a data principal is entitled to receive the notice describing how their personal data will be used.

The Act does not ask an organization to guess which language a data principal prefers, nor to default everyone to English and treat translation as an accommodation for the few who ask. It sets English and the Eighth Schedule languages as the baseline a data principal can choose from.

Why the language of the notice changes what consent means

Consent under the Act has to be free, specific, informed, and unambiguous. "Informed" carries real weight in that list. A person who taps "I agree" on a notice written in a language they do not read fluently has completed an action, not formed an understanding. The purpose, the data items, the withdrawal mechanism — none of it has actually reached them.

India's population reads and transacts across many languages, and English fluency is not evenly distributed across that population. A notice offered only in English is legible to a subset of the data principals an organization serves and effectively opaque to the rest. Whatever the checkbox records, the consent behind it is thinner for anyone who could not follow what they were agreeing to.

Language, in this sense, is part of the mechanism that makes the consent real.

Twenty-three languages, generated when the notice is needed

ConsentIQ's language switcher offers English and all 22 Eighth Schedule languages as options on a consent notice:

The content behind each of those options is not 22 separately authored notices sitting in storage. A notice is drafted once, in whichever language the organization's compliance or product team works in, against the purposes and data items configured for that consent page. When a data principal selects a language from the switcher, ConsentIQ generates the notice in that language through machine translation, on demand, from the current source text.

That distinction matters more than it looks. A notice changes: a new data item gets added, a purpose gets narrowed, a retention period gets updated. Hand-translating 22 separate versions every time the source notice changes is a maintenance job that falls behind, quietly, until a translated notice no longer matches what the English version says. Generating each language version from the live source at the moment it is requested means the applicant reading it in Kannada or Sindhi sees the same notice the organization currently shows in English — not a copy that was accurate on the day someone last translated it by hand.

The switch belongs to the applicant, not the organization

The choice of language sits with the data principal, not as a setting an administrator picks for them. A cookie banner, an account signup form, a marketing opt-in on a website — whatever the notice is attached to, the same 23-language switcher is available on it, and the person reading the notice decides which of those languages they want it in.

That is a narrower design than promising a translation service for every language spoken in India. It is also the specific right the DPDP Act describes: English or a language from the Eighth Schedule, at the data principal's choice.

Twenty-two languages in the Eighth Schedule, plus English, is the full set the DPDP Act points to. See it in your own environment: book a ConsentIQ demo and proof of concept.