Consent or Contract? The Privacy Law Fight Over What Counts as Agreement
Archi4 min read
Contents
Two Legal Bases, Two Different Burdens#
When a privacy regulator announces a fine, the headline usually names the number. The reasoning underneath often turns on a quieter question: which legal basis did the company claim, and did it actually fit? In the EU under the GDPR and in Brazil under the LGPD, consent and contract are separate bases with separate rules. Companies routinely blur them. Regulators do not.
This comparison looks at the two options as a product and engineering choice, not a philosophical one. The angle the headlines miss is operational: each basis demands different evidence, different user interfaces, and different behavior when a user says no.
The GDPR baseline#
Article 6 of the GDPR lists six lawful bases. Consent sits in Article 6(1)(a). Contract necessity sits in Article 6(1)(b). They are not interchangeable. Consent must be freely given, specific, informed, and unambiguous, and it must be withdrawable as easily as it was given. Contract necessity covers processing needed to deliver a service the user actually requested.
The European Data Protection Board has been clear that consent cannot be a precondition for a service when the processing is not necessary for that service. If you sell a newsletter and require consent to a data-sharing arrangement as the price of subscribing, that consent is likely invalid. The contract basis does not rescue it either, because the sharing is not necessary to deliver the newsletter.
Brazil's LGPD, same split, different vocabulary#
The LGPD lists ten legal bases in Article 7. Consent appears in Article 7(I). Contract execution appears in Article 7(V). The Brazilian law adds a detail that matters in practice: consent must be given in writing or by another demonstrable affirmative act, and it must refer to specific purposes. Blanket consent language does not survive.
The LGPD also gives the data subject a right to information about the consequences of refusing consent. That is a design requirement. A cookie banner that only offers accept and manage, with no visible refuse path, is not aligned with the text, even if it is common.
What the Headlines Missed#
Coverage of privacy enforcement tends to focus on the largest fines. The pattern that matters more is smaller and steadier: companies that chose consent because it felt simpler, then discovered they had to build withdrawal, re-consent, and proof of consent into every surface. Companies that chose contract assumed the basis covered more than it does, then had to split processing into two stacks when a regulator asked why analytics ran on contract data.
A practical comparison, then, on three axes.
Axis 1: Proof#
Consent requires a record. You need to show who consented, when, to what wording, and through which interface. That means versioned consent text, timestamps, and a way to tie the record to a specific user session. If your consent text changes, you may need fresh consent. This is real engineering work, and it is the part most often skipped.
Contract necessity requires a different proof: a documented link between the processing and the delivery of the service. You need to show why the data is needed, not merely that it is used. That is a narrower and often harder argument than teams expect. Analytics, personalization, and marketing add-ons rarely pass the necessity test on their own.
Axis 2: Refusal#
With consent, refusal must be as easy as acceptance, and withdrawal must be honored without penalty. That changes the default state of the product. If a user refuses, the service must still work, minus the optional processing.
With contract, refusal is a different event. The user can decline the contract and not receive the service. There is no separate refusal right for the processing itself, because the processing is the service. The catch: you cannot use contract to force optional processing on someone who wants the core service.
Axis 3: Change over time#
Consent is revocable. A user can withdraw at any time, and your system must respond. Contract necessity is tied to the service as delivered. If you change the service materially, you may need to revisit the basis, not just the notice. Neither basis is set-and-forget.
A Third Option That Rarely Gets Its Own Headline#
Legitimate interest, Article 6(1)(f) in the GDPR and Article 7(IX) in the LGPD, is the basis many teams reach for when consent feels heavy and contract feels narrow. It requires a balancing test, documented, and it is not available to public bodies for their core tasks. It is also the basis most likely to be challenged in a complaint, because the balancing test is where disagreements live.
The comparison headlines rarely make: legitimate interest is not a shortcut around consent. It is a separate argument you have to win on paper before you rely on it.
What to Do With This#
Pick the basis per purpose, not per product. A single app can use contract for account creation, consent for marketing email, and legitimate interest for fraud prevention, each with its own record. The mistake is choosing one basis for the whole service and then stretching it to cover everything.
Write the necessity argument for each processing activity before you build the feature. If you cannot finish the sentence "this data is required because the service cannot be delivered without it," contract is the wrong basis. If you cannot show a dated, versioned consent record, consent is not yet in place either.
Regulators read the design, not the banner. The headlines count fines. The decisions behind them count whether your interface, your logs, and your refusal paths match the basis you claimed.
More articles