What counts as a dark pattern legally, not just colloquially?
The regulatory definitions converge on the same idea from different statutes. The FTC's 2022 staff report ('Bringing Dark Patterns to Light') catalogs design practices that trick or manipulate users into choices they would not otherwise have made: false urgency and scarcity claims, disguised ads, trick questions and double negatives, hidden costs revealed late (drip pricing), forced enrollment and preselection, obstruction (easy to enroll, laborious to cancel, the 'roach motel'), confirmshaming, and interface interference that visually buries the disfavored option; legally these become Section 5 unfair-or-deceptive violations, and where subscriptions are involved, ROSCA violations for inadequate disclosure, consent, or cancellation. California's CCPA regulations define a dark pattern as a user interface designed or manipulated with the substantial effect of subverting or impairing user autonomy, decision-making, or choice, and state flatly that agreement obtained through dark patterns does not constitute consent, with symmetry-in-choice as the operative test (the path to say no cannot be longer, slower, or uglier than the path to say yes). The EDPB's guidelines on deceptive design patterns in social media interfaces build the GDPR version: overloading, skipping, stirring (emotional steering), obstructing, fickle (inconsistent interfaces), and left-in-the-dark, each mapped to the articles they violate, because consent that is not freely given and unambiguous (Article 4(11)) is void, and transparency that is not clear and accessible (Article 12) fails independently. The DSA's Article 25 then bans online platforms from interfaces that deceive, manipulate, or materially distort users' ability to make free and informed decisions, dark patterns as a standalone offense, no consent analysis needed. The common thread across all of them: the law does not test your intent; it tests the interface's effect on choice.
What has US enforcement actually punished?
The FTC record reads like a UX anti-patterns textbook with dollar figures. Epic Games (2023): $245 million in consumer redress, the largest FTC dark-patterns order, for Fortnite's counterintuitive button configurations that triggered unwanted purchases, charges without account-holder consent, and lockouts for users who disputed charges (alongside a separate $275 million COPPA penalty). Amazon Prime (filed 2023, settled 2025): the FTC alleged Amazon knowingly enrolled consumers via cluttered checkout flows and built the 'Iliad' cancellation maze; the 2025 settlement, $2.5 billion ($1 billion civil penalty plus $1.5 billion in consumer refunds), is the largest figure in dark-patterns enforcement and made cancellation friction a board-level topic. Vonage (2022): $100 million for cancellation obstruction (no online cancellation, transfer loops, retention gauntlets). Publishers Clearing House (2023): $18.5 million over deceptive sweepstakes-entangled purchase flows. Credit Karma (2022): $3 million over 'pre-approved' offers that were not. Alongside the FTC: state AGs (the Google location-tracking settlements, $391.5 million multistate in 2022, turned on settings that did not do what they said), and the FTC's click-to-cancel rulemaking (the negative-option rule requiring cancellation as easy as signup, though its 2025 vacatur by the Eighth Circuit pushed enforcement back onto ROSCA and Section 5 case-by-case). Patterns in the pattern: subscription flows are the enforcement epicenter; 'we disclosed it in the fine print' consistently fails; internal documents showing the company knew the design confused users (Amazon's own 'Iliad' naming) are the prosecutors' favorite exhibit; and remedies now routinely include design mandates, not just money.
How do EU rules treat dark patterns, and where do the fines land?
Three overlapping regimes. GDPR: manipulative design invalidates the legal states it manufactures, consent extracted through asymmetric buttons is not freely given, so the processing built on it is unlawful from the start; CNIL's cookie-banner fines (Google 150 million EUR, Facebook 60 million EUR, 2021-2022) were exactly this theory, accept in one click, reject in several, and the EDPB cookie-banner taskforce made first-layer reject parity the de facto EEA standard; the Irish DPC's TikTok decision (345 million EUR, 2023) found dark patterns in children's account settings (public-by-default flows steering minors away from private options), notable as a GDPR fine naming deceptive design as such. ePrivacy adds the cookie-specific layer (consent before non-essential trackers, with the design standards above). The DSA: Article 25 prohibits online platforms from deceptive or manipulative interface design outright, with the Commission enforcing against very large platforms at up to 6% of worldwide turnover; the Commission's proceedings have already cited dark-pattern concerns (its 2024-2025 actions against several VLOPs reference interface design in complaint handling, ad transparency, and minors' protections), and unlike the GDPR, no injured 'consent' needs identifying, the design itself is the violation. The Unfair Commercial Practices Directive rounds it out for pure consumer-law cases (fake urgency, hidden costs), enforced by national consumer authorities, and the EU's Digital Fairness Act work program signals more prescriptive design rules coming. Composite EU exposure for a manipulative flow: invalid consent (GDPR fine plus processing built on it becomes unlawful), a DSA violation if you are a platform, and a consumer-law action, three regulators, one screenshot.
Which design choices create the most legal risk, and what are the compliant alternatives?
Ranked by enforcement gravity. Cancellation asymmetry: signup online in two clicks, cancellation by phone-only, retention scripts, or buried flows, the Amazon, Vonage, and click-to-cancel territory; the standard to build to is symmetry, cancel through the same channel and with comparable effort as enrollment, with save-offers permitted but skippable in one action. Consent asymmetry: accept-all prominent, reject buried in settings, pre-ticked boxes, or 'continue without accepting' in grey 8-point type, the CNIL fine pattern; build first-layer reject with equal visual weight. Forced continuity and hidden enrollment: free trials converting silently, checkout flows that enroll by default, negative options without express informed consent, ROSCA's core; build explicit, separate, unbundled enrollment consent with clear pre-billing disclosure and renewal reminders. Confirmshaming and emotional steering: 'No thanks, I hate saving money' decline links, guilt-framed data prompts, cited in the FTC report and EDPB guidelines; build neutral option labels. Trick questions and double negatives: 'Uncheck this box to not receive no communications', deception per se; build single-polarity, plain-language choices. Preselection against interest: privacy-invasive defaults for minors (the TikTok fine), broad-sharing defaults generally; build privacy-protective defaults, which Article 25 GDPR (data protection by default) requires anyway. False urgency and scarcity: fabricated countdowns and 'only 2 left' claims, straightforward deception; build claims that are true or absent. Obstructed rights: DSAR or opt-out flows demanding excessive identity proof or hidden forms, increasingly cited in state-AG sweeps; build rights paths as smooth as marketing paths. The heuristic underneath all of it: any flow whose conversion rate depends on the user misunderstanding or exhausting is a legal exhibit waiting for a case number.
How do you audit for dark patterns and build design governance that prevents them?
The audit method, adapted from what regulators and plaintiff experts actually do. Inventory the decision surfaces: every flow where a user consents, purchases, subscribes, shares data, sets privacy options, or cancels, including email unsubscribe and account deletion, these are your audited population. Walk each flow adversarially, twice: once trying to say yes, once trying to say no, counting clicks, screens, response latencies, and required inputs for each path; asymmetry ratios (5 clicks to cancel vs 1 to enroll) are the finding format that survives dispute. Screenshot everything with timestamps, both because the audit needs evidence and because your defense file needs to show the interface as it existed on a date (regulators subpoena wayback captures; keep better records than the Internet Archive does). Test comprehension where stakes are high: five-user hallway tests asking 'what do you think this button does' catch trick language faster than legal review; the FTC's cases repeatedly cite evidence that users misunderstood, so evidence that users understood is the counter-artifact. Check the states behind the pixels: does reject actually stop the tags, does cancellation actually stop the billing, does the deletion request actually delete, because a clean interface over a non-functioning backend is a worse case, not a better one. Governance to keep it fixed: a design-review gate where flows touching consent, money, or data require privacy/legal sign-off with the asymmetry checklist; metrics hygiene, treat suspicious conversion wins (a redesign that doubles trial-to-paid via a moved button) as review triggers rather than celebrations; dark-pattern literacy in the design org, most manipulative patterns ship because the team optimized a metric, not because anyone chose deception; and an escalation path for the inevitable conflict between growth experiments and compliance, decided somewhere with authority, documented, because 'the A/B test won' has appeared in discovery more than once, and it has never helped the defense.