Keep the double opt-in confirmation email as proof of consent. A German court rejected IP logs.

Ulf Aslak Lai photo Ulf Aslak Lai Published 16 Nov 2026 AI drafted 10 min read
Keep the double opt-in confirmation email as proof of consent. A German court rejected IP logs.

A man in Germany kept getting marketing emails from a travel and online marketing company he says he had never given his address to. When the regional data protection regulator asked the company to prove he had agreed, it sent one line. The line held his email address, an IP address with a sign-up time of 17:22:20 on 29 June 2023, and a second IP address with a time five minutes later, logged when someone clicked the double opt-in link. On 27 July 2026 the Administrative Court of Düsseldorf, the German court that reviews decisions by public authorities in that region, ruled that this line proves nothing 1.

Under the GDPR, a company that sends marketing on the basis of consent has to be able to prove that consent, and the court said a company that cannot is treated as never having had it. The proof the court found missing was the confirmation email.

I think it matters well outside Germany, because the record the court rejected is close to what a newsletter tool will hand you as proof. After reading the judgment I opened Mailchimp's GDPR help page. Under "How can I demonstrate that I collected consent?", it tells customers to export their audience and look at the date, time and IP address of each sign-up and each confirmation. It also suggests a screenshot of the sign-up form and its saved form versions, which covers the wording. It does not mention the confirmation email. So if you run a newsletter, gated guides, webinar sign-ups or a free tier that gets marketing email, this is about your list: people who have not bought anything from you are usually emailed on the basis of consent.

What did the Düsseldorf court decide?

It upheld a reprimand against the company for processing a person's data without being able to prove his consent 1. A reprimand is an official finding that the law was broken, with no fine attached 3, and the court called it the mildest of the corrective measures open to the regulator 1. The judgment is final, and the regulator, the data protection commissioner of North Rhine-Westphalia (LDI NRW), announced it on 5 October 2026 2.

That was a mild outcome for an unusually bad record. When the man first complained, in 2020, the company said it could not show his confirmation email because it did not keep confirmation emails "for data protection reasons". In October 2022 the LDI NRW told it in writing that a valid double opt-in needs a complete record of the consent, stored so that it can be printed. The company still had no such record when the man got another email in 2024 and the regulator asked again. The next company with the same gap could be fined: the GDPR lets a regulator impose a fine instead of, or on top of, a reprimand 3.

The court noted that the man's evidence "practically ruled out" that he had consented, then said that did not decide the case 1. What decided it was whether the company could prove he had consented, and it could not. (The judgment and the press release are in German; the quotes here are my translations.)

Does your legal documentation match what you ship?

Lawcel watches your product changes and flags the moment your terms or privacy policy fall out of sync, then proposes the edits for your team to approve and publish.

Get started

Because it does not connect the consent to the person, and it does not show what was agreed. The court gave three reasons 1:

  1. An IP address identifies a device's internet connection. It can lead to whoever pays for the internet line. It cannot show who was using a device on it at that moment.
  2. An email account is not tied to a device. Nothing links the IP address in the log to the mailbox the emails went to.
  3. A logged IP address shows only that data arrived. The second entry records that a device sent something to the company's server five minutes after the first. It does not show what was sent: whether anyone ticked a consent box, or what the box said.

GDPR Article 7(1) says that where processing is based on consent, "the controller shall be able to demonstrate that the data subject has consented" 3. The court, following earlier German case law, held that the burden of proof sits with the company, and that consent that cannot be proved counts as consent that was never given. Consent was the only legal ground the company claimed for the emails, so without provable consent the emails were unlawful.

Having double opt-in switched on is not proof either. The Düsseldorf company pointed to a written description of its sign-up process that it had given the regulator, and the court said the description did not replace proof: the regulator had never approved a way around Article 7, and the company had not followed its own process anyway. The European Data Protection Board (EDPB), the body of all EU data protection regulators, says the same in its consent guidelines: "It would not be sufficient to merely refer to a correct configuration of the respective website" 4.

It has to show that this person agreed, when, and to what. The GDPR does not prescribe a format. The EDPB says a company should be able to show how and when consent was obtained and what information the person was given at the time, and suggests keeping information on the session in which consent was given, documentation of the consent process as it was then, and a copy of what the person was shown 4.

Put together with the judgment, a record for one subscriber holds:

Keep It shows
Email address Who
Form wording then What they agreed to
Sign-up time When
Confirmation email Sent to that inbox
Click on its link Inbox confirmed

The confirmation email carries the most weight. If your email tool puts a unique link in each confirmation email and logs the click on it, it is fair to ask why that log is not enough. The Düsseldorf company also logged a click, and the court said the log proved nothing, because nothing tied it to the mailbox. A click log is your own system saying a link was clicked. Without the email, you can only claim that the link went to that address and that the email said what you say it said. With the stored email, you can show the regulator the message, the address it went to, the wording it carried and the exact link that was clicked later. That is what turns a click into evidence that someone with access to that inbox confirmed.

The company's first excuse, that it deleted confirmation emails to protect privacy, also fails against the EDPB's guidance. The obligation to prove consent lasts as long as the processing does, and after it ends the proof may be kept for as long as it is needed to defend a legal claim 4. The EDPB also says the proof should not lead to collecting more data than needed. A copy of a short confirmation email to a person you are already emailing is well within that.

Does this apply outside Germany?

Yes. The judgment binds only this case, but Article 7(1) is part of the GDPR and the same in every EU country 3, and the EDPB's guidance on proving consent points the same way 4.

Consent is also the starting point for most marketing email in the EU. The ePrivacy Directive, the EU law on electronic marketing and cookies, allows marketing email only to people who have given prior consent, with one exception, often called the soft opt-in, for a company emailing its own customers about similar products or services 5. Someone who joined a newsletter, downloaded a guide or registered for a webinar has bought nothing, so emailing them marketing usually needs their consent. The same often goes for free-tier users. My co-founder Kenneth's post on unsubscribe rules after the Debenhams complaints covers the other end of the same list: why one unsubscribe has to reach every tool you send from.

What should you check in your own sign-up flow?

If you send marketing email to people who signed up through a form, you need to be able to produce, for any one subscriber, the wording they agreed to and the confirmation email they received. Otherwise, when someone says they never signed up, a regulator will treat every marketing email you sent them as sent without consent. These are the checks I would run, in this order.

  • Try it on one real subscriber. Pick a person who joined your list a year ago and try to produce their record from what you hold today. If all you can find is an address, IP addresses and times, you have the record the court rejected.
  • Keep the consent wording by version. Store the text of the sign-up form with a date or version number each time it changes, and record which version each subscriber saw. Some tools keep form versions for you; check that yours does.
  • Keep the confirmation email as each subscriber received it. That means the rendered message, with their address and their link, stored where you can find and print it by address. A template version plus a send log is a reconstruction, and I would not count on it: what the regulator asked for, and the court found missing, was the email itself. Lawyers who advise German online shops recommend the same record.
  • If your tool cannot keep that copy, move the confirmation step. Mailchimp's GDPR help page mentions no way to keep one. In that case I would send the confirmation email from your own app, through the email service you already use for password resets, keep a copy, and add the person to the newsletter tool only after they click. It takes some engineering work, because no setting does it for you.
  • Carry the record across tool changes. Moving to a new email tool, or merging lists, can drop the original sign-up record. Mailchimp warns that merging audiences with its own tool removes the sign-up time from exports. Before a migration, export the full record and keep it.
  • Keep it for as long as you rely on it. Keep a subscriber's proof while you email them on the basis of their consent. After they leave, keep it only as long as you may need it to defend a claim, then delete it.

A new email tool also adds a company that receives your users' data, which your privacy policy has to name. Lawcel, the compliance tool we build, reads pull requests and tickets against your legal documents and flags that change when the tool arrives through code. It does not store consent records; the check on one real subscriber above is the way to find out where yours stand.

FAQ

No. The regulator had asked the company to use double opt-in. What failed was the record: the company kept IP addresses and times, but not the confirmation email or what the person agreed to.
No. The regulator issued a reprimand, a formal finding that the law was broken, which the court upheld. The judgment is final.
As long as you rely on the consent, and afterwards only as long as you need it to defend a legal claim, according to the EDPB's consent guidelines.
The judgment binds only this case, but the rule it applies, GDPR Article 7(1), is the same in every EU country, and the EDPB's guidance on proving consent points the same way.

References

  1. Verwaltungsgericht Düsseldorf, judgment of 27 July 2026, 29 K 9714/24 (in German) - accessed 16 Nov 2026
  2. LDI NRW, press release of 5 October 2026: advertisers must be able to prove consent to online advertising (in German) - accessed 16 Nov 2026
  3. Regulation (EU) 2016/679 (GDPR), Articles 5(2), 7(1) and 58(2)(b) - accessed 16 Nov 2026
  4. EDPB Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1, section 5.1 (demonstrate consent) - accessed 16 Nov 2026
  5. Directive 2002/58/EC (ePrivacy Directive), consolidated text, Article 13 (unsolicited communications) - accessed 16 Nov 2026

About the author

Ulf Aslak Lai

Ulf Aslak Lai

Co-founder, Chief Technology Officer

Ulf is Co-founder and CTO at Lawcel. He leads engineering architecture for connectors, analysis pipelines, and the safeguards needed when automation touches regulated customer content.

  • Platform architecture
  • Data governance
  • ML/AI systems
GDPR

An unsubscribe must stop marketing email from every tool you use, under EU and UK law

Under EU and UK law, every marketing email must offer a free, easy way out, and an opt-out has to take effect in every tool that sends the marketing it covers: the newsletter, CRM sequences and product email. Withdrawing consent must be as easy as giving it, so if one tick put someone on several lists, one step should take them off all of them.

GDPR

"By using the Service, You agree" in a privacy policy is not consent under GDPR

If a privacy policy names consent for marketing and the only consent behind it is a line like "By using the Service, You agree", the EDPB's guidelines leave that marketing with no legal basis: using a service is not consent, and a company cannot swap to legitimate interest once its consent proves invalid. What works is a separate opt-in, such as an unticked box, and a record.

GDPR

Guessing a prospect's work email is legal in France if they could reasonably expect it

On 16 October 2026 France's data protection regulator, the CNIL, said a company may guess a prospect's work email from their name and employer without asking first, if the person could reasonably expect it. By default, people with no online presence or who hide their contact details could not, so theirs needs safeguards or consent. Each person must be told where the address came from, by the first email or within one month, whichever is sooner.

GDPR

Is legitimate interest enough for product analytics? Check what your tool stores on the device first.

Not on its own. Two rules apply to analytics, in order. Article 5(3) of the ePrivacy Directive, the rule behind cookie banners, governs storing or reading anything on the visitor's device and offers consent or one of two narrow exemptions, never legitimate interest. GDPR Article 6 governs the analysis you run afterwards, and there legitimate interest is available if you can pass the balancing test.