DM4: Privacy, consent and the law for marketers
Consent banners and dark patterns
🎯You'll be able to
Design a consent banner with an equal choice, and recognise the dark patterns India's consumer protection guidelines name.
🏠The everyday picture
A waiter who asks "Would you like dessert?" is offering a choice. One who brings dessert, adds it to the bill and makes you call the manager to remove it is not.
📘What it really is
- A fair banner:
- says what is measured, why, and who receives it, in plain words;
- offers Accept and Reject as equally visible buttons on the first screen (same size, same style);
- has no pre-ticked boxes, and separate choices if there are several purposes (analytics, ads);
- stores the choice and lets people change it later from every page ("Cookie settings");
-
sends nothing optional before the choice.
-
Dark patterns are designs that trick or pressure people. The Central Consumer Protection Authority's Guidelines for Prevention and Regulation of Dark Patterns, 2023 name 13: false urgency, basket sneaking, confirm shaming, forced action, subscription trap, interface interference, bait and switch, drip pricing, disguised advertisement, nagging, trick question, SaaS billing and rogue malware.
-
In consent banners the common ones are interface interference (a bright Accept and a grey "Manage settings" link), nagging (the banner returning on every page after Reject), and forced action (no access until you accept).
-
Strictly necessary storage (the cart, the consent choice itself) doesn't need analytics consent; analytics and ad cookies do.
📝A worked example
Input: the starter banner: "We use cookies to give you the best experience on MittiMart. [Accept all] Manage settings".
| Problem | Pattern | Fix |
|---|---|---|
| No Reject on the first screen | interface interference / forced action | "Reject analytics" button beside Accept |
| Accept is a button, settings a small link | interface interference | Two buttons, same class and size |
| Tags fire before any choice | (no real choice) | Send nothing until "granted" |
| No way back | (withdrawal) | "Cookie settings" in every footer |
Expected output: a redesigned banner in site/js/consent.js; Project 1's test 2 then checks both buttons' text size, weight, height and
width.
🌍Where it's used
- Consent management platforms offer banner templates; teams still need to check the defaults are fair.
- Regulators and consumer groups publish examples of unfair banners.
- UX and legal teams test banners with users to check people understand the choice.
📝Case scenario
A food delivery app's banner made "Accept" a large orange button and "Reject" a grey link two screens deep. Analytics showed 97% accepted. After a redesign with equal buttons, 64% accepted. The team had fewer tracked visitors but could rely on the consent it had.
🖱️Try it
Visit three sites for the first time (a private browser window helps) and screenshot each consent banner. Mark whether Reject is as easy as Accept. Success: a short table naming any dark pattern you see.
⚠️Common mistakes
- An unequal choice. Sign: one bright button and one faint link. Fix: two buttons of the same style.
- Tags before the choice. Sign: requests to analytics while the banner is still showing. Fix: wait for "granted".
- Asking again and again after Reject. Sign: the banner on every page. Fix: remember the choice; show it again only from "Cookie settings".
🛠️For your project
Project 1's tests 1, 2, 3 and 8 check the banner: nothing before a choice, an equal choice, nothing after Reject, and a way back.
✅Quick check
Name two dark patterns from India's 2023 guidelines.
Show the answer
For example basket sneaking, confirm shaming, false urgency, nagging or interface interference.
Does the cart need analytics consent?
Show the answer
No; storage that the shop needs to work is strictly necessary. Analytics and ad cookies need consent.