WolfBoy blog

Why ClickQuickNow was fined PLN 201,559.50: its 'withdraw consent' link withdrew nothing

A "withdraw consent" link must actually withdraw consent, and a Polish fine, upheld by the Supreme Administrative Court in 2024, shows what happens when it does not. Poland's data protection authority fined ClickQuickNow, an e-mail marketing company, PLN 201,559.50 (≈ €47,000) because its "withdraw consent" link ended on a page announcing a withdrawal that never happened, while the consent stayed in place. Withdrawal requests that arrived as empty e-mails went unprocessed too.

The decision

  • Poland: ClickQuickNow, an e-mail marketing company, anonymised in the decision and named in UODO's news item of 25 February 2021 [7]; UODO's 2024 news items spell it "ClickOuickNow".
  • Decided by the President of the Personal Data Protection Office (UODO), decision ZSPR.421.7.2019 of 16 October 2019. The Voivodeship Administrative Court in Warsaw upheld it, and the Supreme Administrative Court (NSA) dismissed the cassation appeal on 12 November 2024.
  • Fine: PLN 201,559.50 (≈ €47,000, the decision's own conversion).
  • Final (prawomocna), as of November 2026.
  • Official text (Polish): orzeczenia.uodo.gov.pl.

What the decision says the software did

The decision has no numbered paragraphs; this section quotes Part I of its statement of reasons (Uzasadnienie).

What a subscriber went through:

  1. They clicked „odwołanie zgody” ("withdrawal of consent") in a marketing e-mail.
  2. A page asked why, offering two answers (ads that don't interest me; ads too often). Without an answer, it went no further.
  3. The next page read „Pani odwołanie zgody dziś (…)!”, which UODO's English news item gives as "Your withdrawal of consent today 13.02.2019 !", followed by an address to write to.
  4. Consent stayed in place. For the company, only a further e-mail to that address, stating exactly what the person wanted, withdrew it. People who could not withdraw complained to UODO.

UODO on step 3:

„zdecydowana większość osób po zapoznaniu się z treścią tak brzmiącego komunikatu stwierdza, że oświadczenie o odwołaniu zgody zostało przyjęte przez Spółkę w dacie wskazanej w komunikacie i w związku z tym dalszych czynności w tym zakresie już nie podejmuje”

"the vast majority of people who read a message worded like this conclude that the Company accepted their withdrawal on the date the message gives, and so take no further steps" (our translation)

Separately, the company received e-mails with no text every day, sent to an address published on two websites, and „tego typu wiadomości Spółka pozostawia bez rozpatrzenia” ("leaves messages of this kind unprocessed" (our translation)). UODO read them as withdrawals: „określenie adresata w taki sposób wskazuje świadome działania nadawcy takiego e-maila, tzn., że odwołuje on zgodę” ("addressing the message this way shows a deliberate act by its sender, namely that he is withdrawing consent" (our translation)). The decision redacts that address, the websites and the daily count. The company said the two sites were e-mail services whose automated mechanisms sent them.

What this looks like in code

Stack: Node.js, Express, PostgreSQL. The campaign sender selects subscribers whose consents.withdrawn_at is NULL, so only a write to that column stops the e-mails.

This is not ClickQuickNow's code. The decision does not publish any code; this reproduces the behaviour it describes.

// The "withdraw consent" link in every campaign e-mail: /unsubscribe?t=<token>
router.get('/unsubscribe', (req, res) => {
  // Step 1: "Why are you leaving?"  A: ads I'm not interested in / B: ads too often
  res.render('unsubscribe-reason', { t: req.query.t });
});

router.post('/unsubscribe', async (req, res) => {
  const sub = await subscriberFromToken(req.body.t);
  if (!req.body.reason) return res.redirect(`/unsubscribe?t=${req.body.t}`); // no answer, no way on
  await db.query('INSERT INTO unsubscribe_feedback (subscriber_id, reason) VALUES ($1, $2)',
    [sub.id, req.body.reason]);
  // Step 2: a success message. Nothing here writes consents.withdrawn_at.
  res.render('unsubscribe-done', {
    message: `Your withdrawal of consent today ${new Date().toLocaleDateString()}!`,
    footer: 'You can withdraw your consent at any time by writing to privacy@example.com.',
  });
});

Then a mailbox that receives withdrawal requests:

// Polls privacy@example.com every five minutes.
const KEYWORDS = /withdraw|unsubscribe|remove me|delete/i;

async function processInbox(messages, { openTicket, archive }) {
  for (const msg of messages) {
    const text = `${msg.subject ?? ''} ${msg.text ?? ''}`.trim();
    if (KEYWORDS.test(text)) {
      await openTicket(msg); // a person handles it, eventually
    }
    // An empty message matches nothing: archived, never answered, never processed.
    await archive(msg);
  }
}

If a person reads that mailbox, this half is a manual process no code search will find.

One source of such messages is a mailto: address in a List-Unsubscribe header (RFC 2369): the RFC expects mail clients to offer a button that sends to it, and some do, according to SendGrid's documentation.

Why it was a violation

On the link, UODO found that the process „utrudnia, a wręcz uniemożliwia” ("hinders, and indeed prevents" (our translation)) withdrawal, contrary to Article 7(3), under which withdrawing consent must be as easy as giving it. Requiring a reason had no legal basis. The confirmation and the instructions on how to withdraw that followed it were „sprzeczne ze sobą komunikaty” ("contradictory messages" (our translation)), which breached fairness and transparency under Article 5(1)(a). The company did not facilitate the exercise of rights (Article 12(2)), and the process blocked erasure after withdrawal (Article 17(1)(b)). UODO rated the 17(1)(b) and 5(1)(a) breaches the most serious, for their seriousness and the number of people affected (redacted; UODO's 2024 news item gives more than 2.1 million in the database on 31 January 2019). It judged the breach of Articles 7(3), 12(2) and 17(1)(b) intentional.

On the mailbox, under Article 24(1) (Part II), the company's measures were ineffective: the empty-e-mail problem had not been remedied, and the company „nie prowadzi żadnej korespondencji w sprawie wniosków o odwołanie zgody” ("conducts no correspondence about withdrawal requests" (our translation)). In Part I, UODO noted it could have written back to ask what an e-mail meant. Under Article 6(1) with 5(1)(a) (Part III), the company kept withdrawal e-mails from people absent from its database instead of deleting them once it had checked; this weighed little in the fine.

According to UODO's English summary, the NSA said in its oral reasoning that the link "did not result in the prompt revocation of consent and, in fact, the messages sent via the link were misleading to the person who wished to withdraw consent."

The fix

Every channel calls one function that writes the withdrawal and cancels queued sends (services/consent.js, then the route and the inbox job):

async function withdrawConsent(subscriberId, via) {
  await db.query(`UPDATE consents SET withdrawn_at = now(), withdrawn_via = $2
     WHERE subscriber_id = $1 AND purpose = 'marketing' AND withdrawn_at IS NULL`,
    [subscriberId, via]);
  await db.query('DELETE FROM send_queue WHERE subscriber_id = $1', [subscriberId]);
}

router.get('/unsubscribe', (req, res) => res.render('unsubscribe-confirm', { t: req.query.t }));
router.post('/unsubscribe', async (req, res) => { // also the RFC 8058 one-click target
  const sub = await subscriberFromToken(req.body?.t ?? req.query.t);
  if (!sub) return res.status(400).render('unsubscribe-error');
  await withdrawConsent(sub.id, 'link');
  if (req.body?.reason) await saveFeedback(sub.id, req.body.reason); // optional
  res.render('unsubscribe-done', { message: 'Consent withdrawn. No more e-mail from us.' });
});

async function processInbox(messages, { reply, openTicket, deleteMessage }) {
  for (const msg of messages) {
    const sub = await findSubscriberByEmail(msg.from);
    if (!sub) { await reply(msg.from, NO_DATA_REPLY); await deleteMessage(msg); continue; }
    const text = `${msg.subject ?? ''} ${msg.text ?? ''}`;
    if (msg.to === WITHDRAW_ADDRESS || WITHDRAW_WORDS.test(text)) {
      await withdrawConsent(sub.id, 'email'); // an empty message here is a withdrawal
      await reply(msg.from, 'Your consent is withdrawn. We have stopped sending you e-mail.');
    } else {
      await reply(msg.from, 'We received your message. What would you like us to do?');
      await openTicket(msg);
    }
  }
}

What changed:

The sketch stops the e-mail but does not erase the record. Article 17(1)(b) provides for erasure once consent is withdrawn and no other legal ground remains.

Check your own code

Sources

  1. UODO (President of the Personal Data Protection Office), decision ZSPR.421.7.2019 of 16 October 2019 (Polish) — https://orzeczenia.uodo.gov.pl/document/urn:ndoc:gov:pl:uodo:2019:zspr_421_7
  2. UODO, "The Supreme Administrative Court confirmed that withdrawal of consent cannot be impeded", 15 November 2024 — https://bip.uodo.gov.pl/en/553/1790
  3. Regulation (EU) 2016/679 (General Data Protection Regulation) — https://eur-lex.europa.eu/eli/reg/2016/679/oj
  4. RFC 8058, "Signaling One-Click Functionality for List Email Headers" — https://www.rfc-editor.org/rfc/rfc8058
  5. RFC 2369, "The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields" — https://www.rfc-editor.org/rfc/rfc2369
  6. Twilio SendGrid (an e-mail sending service), "List-Unsubscribe", vendor documentation — https://www.twilio.com/docs/sendgrid/ui/sending-email/list-unsubscribe
  7. UODO, „WSA oddalił skargę ClickQuickNow na decyzję UODO”, news item of 25 February 2021 (Polish; archived copy, the original address no longer resolves) — https://web.archive.org/web/20230609015535/https://archiwum.uodo.gov.pl/pl/138/1927

Quotations were checked against these sources on 17 November 2026.

This is general information about a published decision, written by a software developer; it is not legal advice and does not establish whether any law applies to you or whether your product complies.

This article was written with AI assistance and checked against the official sources listed above.