Under the DPDP Act, consent only counts if the person was given a proper notice first. This page covers what that notice must contain and how ConsentPlix shows it in every scheduled Indian language.
What a valid notice needs
Sections 5 and 6 of the Act set four practical rules:
- Separate from your terms. Consent for processing personal data cannot be bundled into general Terms of Service. It needs its own notice and its own action.
- One item per purpose. List the personal data you collect and the specific purpose for each use. A visitor must be able to agree to analytics but refuse marketing, for example.
- Available in the visitor’s language. Section 5(3) gives people the option to read the notice in English or any of the 22 languages in the Eighth Schedule of the Constitution.
- Easy to withdraw. Section 6(4) says withdrawing consent must be as easy as giving it. If agreeing took one click, withdrawing should too.
The notice must also tell people how to exercise their rights and how to complain to the Data Protection Board of India.
How ConsentPlix builds the notice
- Each purpose you configure in the Console becomes its own toggle, unticked by default.
- Every notice version gets a hash. Each consent record stores that hash, so you can later prove exactly which wording a person saw.
- A persistent consent button stays on the page so people can review or withdraw at any time.
Supported languages
ConsentPlix includes translations for all 22 Eighth Schedule languages, plus English.
| Language | Code | Main regions |
|---|---|---|
| Hindi | hi | Delhi, Uttar Pradesh, Madhya Pradesh, Bihar, Rajasthan, Haryana |
| Bengali | bn | West Bengal, Tripura, Assam |
| Marathi | mr | Maharashtra, Goa |
| Telugu | te | Andhra Pradesh, Telangana |
| Tamil | ta | Tamil Nadu, Puducherry |
| Gujarati | gu | Gujarat, Dadra and Nagar Haveli |
| Urdu | ur | Jammu and Kashmir, Telangana, Uttar Pradesh |
| Kannada | kn | Karnataka |
| Odia | or | Odisha |
| Malayalam | ml | Kerala, Lakshadweep |
| Punjabi | pa | Punjab, Chandigarh |
| Assamese | as | Assam |
| Maithili | mai | Bihar, Jharkhand |
| Santali | sat | Jharkhand, West Bengal, Odisha |
| Kashmiri | ks | Jammu and Kashmir |
| Nepali | ne | Sikkim, West Bengal |
| Konkani | kok | Goa, Karnataka, Maharashtra |
| Sindhi | sd | Gujarat, Maharashtra, Rajasthan |
| Dogri | doi | Jammu and Kashmir, Himachal Pradesh |
| Manipuri | mni | Manipur |
| Bodo | brx | Assam |
| Sanskrit | sa | Recognised across India |
Choosing the language
Enable the languages you need for your site in the Console. ConsentPlix then picks the visitor’s browser language if it is enabled, and otherwise falls back to the first language in your list.
To force a language, set data-lang on the script tag:
<script src="https://cdn.consentplix.com/cp.min.js" data-site-token="YOUR_SITE_TOKEN" data-lang="ta"></script>If you build your own banner in Headless Pro mode, add a language picker with data-cp-lang-select. The SDK switches the notice text when the visitor changes it:
<select data-cp-lang-select>
<option value="en">English</option>
<option value="hi">Hindi</option>
<option value="ta">Tamil</option>
</select>