Skip to main content
DPDP-AID Readiness Checkby

Consent and lawful use

Consent must be free, specific, informed, unambiguous and given by a clear action, and withdrawing it must be as easy as giving it. Where consent is not the basis, the legitimate use relied on has to be documented.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

Requirements
10
Must-do
5
Penalty ceiling
Up to ₹50 crore

Breach of any other provision. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 3 of these requirements are in the quick check.

What we assess in this area

  1. MustIn the quick checkCON-01

    Consent is free, specific, informed, unambiguous and given by a clear action

    Where processing relies on consent, the consent must be free, specific, informed, unconditional and unambiguous. The person must give it through a clear affirmative action. Silence, pre-ticked boxes or bundled terms do not count.

    What good looks like

    Every consent request is separate from other terms. It names the data and the purpose. Nothing is pre-ticked. People can refuse without losing services that do not need that data.

    How to get there

    Review every form, app screen and checkout where consent is taken. Remove pre-ticked boxes. Separate consent from terms of service. Test that refusing optional consent does not block the core service.

  2. MustCON-02

    Consent is sought only for data needed for the stated purpose

    Consent is valid only for personal data that is necessary for the specified purpose. Asking for extra data under the same consent goes beyond what the person agreed to, and that part of the consent is not valid.

    What good looks like

    Each consent request asks only for the data needed for its stated purpose. Optional data has its own separate request. Forms and screens have been checked to remove fields that no purpose needs.

    How to get there

    Map every field on each form to a purpose. Remove fields with no purpose. Move optional data behind a separate consent. Repeat the check whenever a form or purpose changes.

  3. MustIn the quick checkCON-03

    Withdrawing consent is as easy as giving it

    People can withdraw consent at any time. The way to withdraw must be as easy as the way they gave consent. Withdrawal does not affect processing done before it, but it does apply from then on.

    What good looks like

    People can withdraw consent in the same place and with a similar number of steps as giving it, for example a toggle in the account or a link in every email. Withdrawals are recorded and acted on promptly.

    How to get there

    List every channel where consent is collected. Add a matching way to withdraw in each one. Count the steps and make them comparable. Record each withdrawal with a timestamp.

  4. MustIn the quick checkCON-04

    Consent records show who, when, which notice version and which purposes

    Where consent is questioned, the business must be able to prove that notice was given and consent was obtained. Without reliable records, the business cannot show that its processing was lawful.

    What good looks like

    Each consent event is stored with the person, the time, the channel, the notice version shown and the purposes agreed. Withdrawals are stored the same way. Records are protected from change and easy to retrieve.

    How to get there

    Version every notice. Log each consent and withdrawal with person, time, channel, notice version and purposes. Store the log so it cannot be edited. Test that you can pull one person's history quickly.

  5. MustCON-05

    Processing stops, including at processors, after consent is withdrawn

    Once a person withdraws consent, the business must stop processing their data within a reasonable time, unless the law requires or allows it to continue. Its processors must stop too.

    What good looks like

    A withdrawal triggers a defined process that stops processing across internal systems and at every processor. Timelines are set and tracked. Any data kept under a legal requirement is recorded with its basis.

    How to get there

    Trace where data for each consented purpose flows. Build a withdrawal workflow that reaches each system. Add a duty to act on withdrawals in processor contracts. Test the workflow end to end.

  6. ShouldCON-06

    Legitimate uses relied on instead of consent are documented

    The Act lists certain legitimate uses where consent is not needed, such as data a person gave voluntarily for a specified purpose, or employment. These uses are narrow and must match the conditions the Act sets.

    What good looks like

    Each activity that relies on a legitimate use names the specific use and explains why its conditions are met. The record is reviewed when the activity changes. Doubtful cases have moved to consent.

    How to get there

    List activities that run without consent. Match each one to a specific legitimate use. Write down why the conditions are met. Move any activity that does not fit to a consent basis.

  7. ShouldCON-07

    Consent requests are available in English or a language of the Eighth Schedule

    People must be able to read a consent request in English or in any language listed in the Eighth Schedule to the Constitution. This helps people understand what they are agreeing to.

    What good looks like

    Consent requests are offered in English and in the Eighth Schedule languages your users are likely to need. People can choose their language easily, and translations are checked for accuracy.

    How to get there

    Find out which languages your users speak. Translate consent requests into those languages first. Add a clear language choice. Have translations reviewed and keep them in step with each notice version.

  8. OptionalCON-08

    A decision on integrating with registered Consent Managers

    The Act allows people to give, manage and withdraw consent through a Consent Manager registered with the Board. Businesses should decide whether and when to accept consent through these platforms.

    What good looks like

    The business has made a documented decision on Consent Manager integration, with reasons and timing. If it integrates, consents received through a Consent Manager are recorded and honoured like any other consent.

    How to get there

    Track the registration of Consent Managers by the Board. Assess whether your users are likely to use them. Record a decision and a review date. If yes, plan the technical integration.

  9. ShouldCON-09

    Consent is captured the same way at every point where you collect personal data

    People share data with you through websites, apps, forms, call centres and in person. Consent must meet the same standard at each of these points. A gap at one channel can undo good practice everywhere else.

    What good looks like

    Every collection point is listed. Each one shows the notice, asks for consent by a clear action and records it in the same consent store. New channels are checked before they go live.

    How to get there

    List every channel that collects personal data, including offline forms and call centres. Check how consent is taken at each. Fix the weakest channel first. Add a consent check to your launch checklist for new channels.

  10. ShouldCON-10

    Verifiable consent from the lawful guardian of a person with disability

    When a person with disability has a lawful guardian, the law expects you to get consent from that guardian. You should also take reasonable steps to confirm the guardian's appointment before relying on their consent.

    What good looks like

    Staff know when guardian consent is needed. The business checks proof of guardianship, records the guardian's consent against the person's record, and lets the guardian exercise rights and withdraw consent easily.

    How to get there

    Decide how people can tell you a guardian acts for them. Define the proof you will accept. Add a guardian consent step to the relevant forms. Train front-line staff to spot these cases.

Other areas we assess

All 13 areas

Check this area against your own business

The free assessment scores this area with the rest and shows you where it ranks against your other gaps.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.