Can one click really approve 1,741 advertising partners?

What noyb alleges

noyb says the consent request nudges visitors toward accepting tracking by 1,741 partners. The organization argues that GDPR consent must be freely given, specific, informed and unambiguous, and that a single broad acceptance cannot meet that standard when the data recipients and purposes are practically unreadable.¹

The complaint estimates that even spending six minutes on each partner's privacy policy would take at least 170 hours. The exact reading time is an illustration rather than a legal threshold, but it captures the mismatch between the button's simplicity and the decision's scope.¹

Cybernews independently reported the filing and its central allegation. The case was sent to the Austrian Data Protection Authority. Until that authority decides, the accurate language is alleged, complaint and requested remedy, not violation or fine.^1,2

• The filing is dated July 30, 2026.
• The 1,741 figure comes from the consent interface described by noyb.
• No final regulatory decision is cited in this article.

Why giant partner lists are not just paperwork

Each partner can represent a separate company, purpose, retention policy and onward-transfer path. A person pressing accept is not merely agreeing to one website remembering a preference. The button can authorize an advertising supply chain that is difficult to map after the fact.^1,2

Large lists also weaken comparison. A visitor cannot easily tell whether rejecting will break the dictionary, whether a smaller set is necessary for the service, or whether hundreds of optional purposes have been bundled together. The cost of understanding is placed on the person with the least time and information.¹

Consent fatigue is the predictable result. When every site presents a different wall of vendors, people learn to click the fastest route. That behavior does not prove users are indifferent to privacy. It may show that the interface has made a meaningful choice too expensive.^1,2

• A partner count is not the same as a purpose count.
• Necessary service functions and advertising should be distinguishable.
• A fast accept path should have an equally clear reject path.

What a visitor can do today

If the banner offers reject all or manage choices, use that before opening the service. Take a screenshot when the choices are confusing or the reject path fails. A dated record is more useful than a memory if you later contact the site or a regulator.¹

Browser controls can reduce some tracking, but they do not rewrite consent already stored on a site. Clear the site's cookies and local storage if you want to trigger the banner again, then revisit the privacy choices. Remember that clearing all browser data can sign you out elsewhere.^1,2

For a dictionary, offline apps and browser dictionaries may provide the same core function with fewer advertising requests. That is a product comparison, not a claim that every offline app is private. Check permissions, data-safety disclosures and whether lookups are sent to a server.²

• Look for reject all before opening detailed settings.
• Save evidence if the interface blocks or reverses your choice.
• Compare an offline option for repeated dictionary use.

What a fair consent design would change

A fair design would explain the main purposes in ordinary language, separate necessary processing from optional advertising, and keep refusal as easy as acceptance. It would also let a person revisit the decision without hunting through footer links.¹

Vendor counts alone do not decide legality. A regulator will consider the actual interface, purposes, legal basis and evidence of what users were told. But a count in the thousands is a warning that the information architecture may be serving the ad system better than the person.^1,2

The dict.cc complaint is valuable even before a ruling because it gives readers a concrete diagnostic. When one button claims to represent thousands of relationships, ask whether the choice is specific enough to mean anything at all.^1,2

Website operators also need a way to challenge the advertising platform they inherited. A consent-management package may arrive with a default vendor catalogue that expands over time. Regular audits should remove unused partners, map every purpose to an actual product need and verify that a refusal is respected by the network requests that follow.¹

A regulator's eventual decision may turn on details beyond the headline number, including how partners are grouped and what happens after each choice. Whatever the outcome, the complaint gives product teams a practical test: if staff cannot explain the partner list in a short review, an ordinary visitor probably cannot consent to it meaningfully.^1,2

• Consent should be granular enough to reflect real purposes.
• Withdrawal should be as easy as acceptance.
• Treat the pending complaint as an allegation until a regulator rules.