Skip to main content
Home/DPDP Dictionary/Clear Affirmative Action
DPDP Dictionary · Consent, notice & lawful grounds

Clear Affirmative Action

A deliberate act, such as ticking a box or pressing a button, through which a person shows consent.

Consent, notice & lawful groundsReviewed October 2026
In simple words

A clear affirmative action is something a person deliberately does to say yes, such as ticking an empty box or tapping an "I agree" button. Doing nothing, scrolling on or leaving a box pre-ticked does not count.

Meaning of Clear Affirmative Action

Silence, inactivity and pre-ticked boxes are not clear affirmative actions. The person must do something that clearly signals agreement to the specific purpose in front of them.

Section 6(1) of the DPDP Act says consent must be free, specific, informed, unconditional and unambiguous, and that it must be signified by a clear affirmative action. The phrase sets a minimum on how a person shows agreement. The Act does not list the exact gestures, so the test is practical: does the act show, without guesswork, that this person chose to agree to this purpose?

Acts that typically qualify include ticking an unticked box that sits beside a specific purpose, pressing a button labelled in plain words such as "Yes, send me the monthly statement by email", choosing an option in a settings screen, signing a form that names the purpose, or giving a clear spoken or typed answer that is recorded. The key is that the person did something intended to give permission, and that the thing she agreed to was visible when she did it.

Acts that usually do not qualify are silence, inactivity, scrolling, continued browsing, boxes ticked by default, and toggles preset to "on". Equally weak is a single button that says "I agree to everything" for a bundle of unrelated purposes, because the act does not tie to a specific purpose. In effect, the clear-action requirement works hand in hand with "specific" and "unambiguous" in the same sub-section.

It is useful to compare this with the GDPR, where the European regulators have repeatedly said that pre-ticked boxes and silence are not valid consent. The DPDP Act reaches a similar practical position through its own wording. It also interacts with Section 7(a). When someone voluntarily hands over data for a specified purpose and does not object, that can be a legitimate use without any separate consent click; but the use is limited to that purpose, and anything beyond it needs a real affirmative act.

Examples of Clear Affirmative Action

Quick example

Clicking "I agree" on an unticked, purpose-specific consent request is a clear affirmative action. Continuing to browse a site is not.

Telecom retailer

At a store counter, an executive turns a tablet toward a customer and asks her to tick one of two separate boxes: SIM-related service messages, and partner promotions. Both start unticked. She ticks the first and leaves the second, and the system records exactly that choice.

Insurance aggregator

A web form for comparing policies shows a button "Yes, share my details with the three insurers I select". The visitor picks two insurers and clicks the button, and the platform shares data only with those two for quote purposes.

Media website

A news site's banner offers equal-sized buttons for "Allow personalised ads" and "Use only essential [cookies](term/cookies)". No ad trackers load until a visitor presses the first button, and scrolling is not treated as an answer.

Why Clear Affirmative Action matters

The way consent is captured is often the weakest link in an organisation's privacy programme, and it is the first thing a complainant or the Board looks at. If the interface relied on default settings, the consent may fail altogether, and Section 6(10) places on the Fiduciary the burden of proving otherwise.

Processing without a valid ground breaches Section 4, and in the Schedule to Section 33 residual breaches are exposed to penalties of up to ₹50 crore. For users, the clear-action rule protects against being enrolled in marketing, data sharing or profiling by default, and for honest businesses it provides a clean, auditable standard to design against.

How it works in practice

  1. 1Audit every consent point, including web forms, mobile permissions, call-centre scripts, in-store tablets and WhatsApp journeys, and list what the person must do to say yes. Anywhere the answer is "nothing", you have a gap.
  2. 2Switch all default-on checkboxes and toggles to off. Make the person take the step, and present the choices for different purposes as separate controls.
  3. 3Label buttons with the action and the purpose in plain words. "Allow my location for finding nearby stores" is clearer than "OK", and a refusal such as "Not now" should carry similar visual weight.
  4. 4For voice or assisted channels, script a clear question, wait for an explicit answer, and save the recording or a timestamped log. A hesitant "hmm" should be treated as no answer.

Where it appears in the DPDP Act and Rules

Common mistakes to avoid

Treating a scroll, a click on the page, or a closed banner as agreement. These are not deliberate acts of consent; treat them as no answer and keep non-essential processing off.

Using pre-ticked boxes because they raise opt-in rates. The higher number is not valid consent, and a regulator can discount it entirely.

One "I agree" button covering terms of service, marketing and data sharing together. Separate the purposes so that each choice is its own act.

Forgetting to log the act. An action no one can later demonstrate is no help when Section 6(10) asks you to prove consent.

Compliance tips

  • Run a quick usability test: ask five users what they think they agreed to after a flow. If answers differ from your intention, the action is not clear enough.

  • Keep the "yes" and "no" paths equally easy: same size, same screen, similar wording, no extra confirmation hoops on one side only.

  • Document the screen design, copy and technical behaviour for each consent point in a short design note and update it with every release.

Common questions about Clear Affirmative Action

Is a pre-ticked box a clear affirmative action?

No. A box already ticked requires no act from the person, so it does not show deliberate agreement. Section 6(1) requires consent to be signified by a clear affirmative action, so the person should have to tick the box, press the button or otherwise act herself.

Does continuing to use a website count as consent under the DPDP Act?

Generally no. Continued browsing or scrolling is not a clear affirmative action tied to a specific purpose. Non-essential processing, such as advertising trackers, should wait until the visitor makes a deliberate choice. Essential functions, such as keeping a login session working, are a separate matter.

Can a verbal yes be a clear affirmative action?

It can be, if the question was clear, the person answered explicitly, and you keep reliable evidence such as a call recording or a timestamped log. The risk with voice is proof, since Section 6(10) puts the burden on the Fiduciary to show that consent was properly obtained.

More in Consent, notice & lawful grounds

General information, not legal advice. Check the Act, the Rules and any notifications for your situation.

Keep learning