What Is Valid Consent Under the DPDP Act?
What is valid consent under the DPDP Act? Learn the key consent requirements, invalid consent examples, withdrawal rules, consent records and best practices.
By Promiz · Published · 8 min read · Based on the DPDP Act, 2023 and DPDP Rules, 2025 · Not legal advice
Valid consent under the DPDP Act must be free, specific, informed, unconditional and unambiguous. It must also be given through a clear affirmative action and cover only the personal data necessary for the specified purpose.
That means a simple "I Agree" button does not automatically make consent valid.
How the consent request is designed, what information the person sees, what data is covered, whether the choice is genuine, and whether the organisation can prove what happened all matter.
This guide explains what valid consent under the DPDP Act means, what can make consent invalid, whether pre-ticked checkboxes are allowed, how consent withdrawal works, what a consent record should contain, and how businesses can review their consent flows.
New to terms like Data Principal and Data Fiduciary? Read DPDP Act 2023 Explained: Data Principal vs Data Fiduciary vs Data Processor first.
What is valid consent under the DPDP Act?
The DPDP Act allows personal data to be processed based on consent or certain legitimate uses.
When an organisation relies on consent, the Data Principal should understand what they are agreeing to and what their personal data will be used for.
Valid consent therefore needs to be more than a technical checkbox. It should represent a genuine and informed decision by the Data Principal.
For businesses, the practical question is: can you clearly show what the person agreed to, what they were told, and when they agreed?
If you cannot, the consent may be difficult to demonstrate later.
What makes consent valid?
Valid consent has five important qualities.
- Free - the person has a genuine choice.
- Specific - consent relates to a clearly stated purpose.
- Informed - the person receives the information needed to make the decision.
- Unconditional - consent is not improperly tied to an unrelated condition.
- Unambiguous - there is no doubt that the person agreed.
Consent must also be given through a clear affirmative action.
In practice, businesses should design consent requests so that people can understand the purpose, make a genuine choice, and actively indicate their decision.
For example, compare "We may use your data for business purposes" with "I agree to receive promotional emails about products and offers".
The second example gives the person a much clearer understanding of what they are agreeing to.
A consent request should also avoid unnecessary data collection. Consent for one purpose does not automatically justify collecting every type of personal data.
What can make consent invalid?
Several common consent practices can create problems.
Pre-ticked checkboxes
A pre-ticked checkbox should not be used as the basis for valid consent.
For example,
☑ I agree to receive marketing emails.
The box has already been selected.
A clearer approach is
☐ I agree to receive marketing emails.
The person has to actively select it, providing a clearer affirmative indication of their choice.
Bundling consent with terms and conditions
Consent for an optional purpose should not simply be hidden inside acceptance of unrelated Terms and Conditions.
For example: "By accepting these Terms, you agree to receive promotional emails."
This combines two different decisions:
- Accepting the Terms required to use the service.
- Agreeing to receive marketing communications.
If marketing is optional, the person should have a separate and meaningful choice.
Collecting unnecessary personal data
Consent is limited to the personal data necessary for the specified purpose.
For example, a telemedicine service may need certain information to provide medical services but may also ask to access the user's phone contacts. If the contact list is not necessary for providing the service, that unrelated data should not simply be treated as necessary because the user agreed to the broader request.
A useful rule for product teams is that the purpose, the consent request and the personal data collected should make sense together.
Using unclear consent requests
A button that says "Accept" without meaningful information around it does not provide a strong consent experience.
The consent request should use clear and plain language. The person should be able to understand:
- What personal data is being processed
- Why it is being processed
- What purpose they are agreeing to
- How consent can be withdrawn
- How they can exercise their rights
- How they can contact the organisation or raise a complaint
The goal is simple: a person should understand the decision before making it.
Can consent be withdrawn under the DPDP Act?
Yes. Consent can be withdrawn at any time.
An important requirement is that withdrawal should be as easy as giving consent. If giving consent takes one click, withdrawal should not require a complicated manual process.
Compare the two experiences:
- Giving consent: click "Accept".
- Withdrawing consent: log in → find privacy settings → email support → submit a form → wait for confirmation.
That creates an unnecessarily difficult withdrawal experience. A better approach is to provide a clear preference or privacy centre where people can manage their consent choices.
What happens after consent is withdrawn?
Withdrawal is not simply a change to a checkbox in the user interface.
Once consent is withdrawn, the organisation needs to stop processing based on that consent within a reasonable time and ensure relevant Data Processors also stop processing, unless processing is otherwise required or authorised by law.
Processing carried out before withdrawal remains lawful.
Organisations should therefore consider what happens across:
- Applications
- Databases
- CRM systems
- Marketing platforms
- Analytics tools
- Data Processors
- Other downstream systems
Personal data may also need to be erased when consent is withdrawn or the purpose is no longer served, subject to applicable legal retention requirements.
This is why consent withdrawal needs to be connected to the wider data-processing workflow, rather than treated as only a front-end setting.
How should businesses prove consent?
The Data Fiduciary is responsible for proving that the required notice was given and consent was obtained when the question arises. That makes consent records important.
A useful consent record should capture information such as:
- Who gave consent
- What notice they saw
- Which notice version and language applied
- Which purposes they accepted or rejected
- When they gave consent
- Whether and when they later withdrew it
A simple database value such as marketing_consent = true does not tell the complete story. A stronger consent record can show the context behind that decision and help an organisation demonstrate how consent was obtained.
Is consent always required under the DPDP Act?
No. The DPDP Act also provides for certain legitimate uses where consent is not required. These include specified situations such as:
- Personal data voluntarily provided for a specified purpose
- Certain legal obligations
- Medical emergencies
- Employment-related processing
Organisations should not automatically ask for consent for every processing activity. Before creating a consent request, ask: do we actually need consent for this processing activity?
If another lawful ground applies, the organisation should manage the activity accordingly rather than creating unnecessary consent and withdrawal requirements.
What about children's data?
When the Data Principal is a child, or a person with a disability who has a lawful guardian, additional requirements apply.
The Data Fiduciary must obtain verifiable consent from the parent or lawful guardian. The DPDP Act also places restrictions on tracking, behavioural monitoring and targeted advertising directed at children.
Businesses handling children's data therefore need to design their consent process differently from a standard adult consent flow.
How Promiz helps manage consent
Managing valid consent is not only about displaying a checkbox. Organisations also need to maintain consent records, manage purposes, support withdrawal and ensure consent changes can reach relevant systems.
Promiz helps organisations manage these consent workflows through capabilities such as:
- Purpose-specific consent - separate purposes can be presented so people can make meaningful choices.
- Consent notices - people receive relevant information before making their decision.
- Consent records - decisions can be linked to purposes and notice versions with timestamps.
- Easy withdrawal - people can change or withdraw consent through a preference centre.
- Purpose-based retention — retention periods can be connected to consent purposes.
Promiz is a consent management platform. It does not replace the Data Fiduciary's responsibility to determine the appropriate legal basis, provide required notices or comply with the DPDP Act.
Questions teams ask
Are pre-ticked checkboxes allowed under the DPDP Act?
A pre-ticked checkbox should not be used as the basis for valid consent. Consent must be given through a clear affirmative action, and a box that is already selected means the person took no action. Present the box unticked so the person actively selects it.
Can consent be withdrawn under the DPDP Act?
Yes. Consent can be withdrawn at any time, and withdrawal should be as easy as giving consent. If giving consent takes one click, withdrawal should not require logging in, emailing support, and submitting a form. A preference or privacy centre is a better approach.
What happens after consent is withdrawn?
The organisation needs to stop processing based on that consent within a reasonable time and ensure relevant Data Processors also stop, unless processing is otherwise required or authorised by law. Processing carried out before withdrawal remains lawful. Personal data may also need to be erased, subject to legal retention requirements.
What should a consent record contain?
Who gave consent, what notice they saw, which notice version and language applied, which purposes they accepted or rejected, when they gave consent, and whether and when they later withdrew it. A single database value such as marketing_consent = true does not tell the complete story.
Is consent always required under the DPDP Act?
No. The DPDP Act also provides for certain legitimate uses where consent is not required, including personal data voluntarily provided for a specified purpose, certain legal obligations, medical emergencies, and employment-related processing. Check whether another lawful ground applies before building a consent request.
How is consent handled for children's data?
When the Data Principal is a child, or a person with a disability who has a lawful guardian, the Data Fiduciary must obtain verifiable consent from the parent or lawful guardian. The DPDP Act also restricts tracking, behavioural monitoring, and targeted advertising directed at children.
Promiz supports your DPDP compliance programme. It is not legal advice. Your legal team decides purposes, lawful bases and retention periods.