StatuteCase file
Lumen PR #2
Fixed and proven

Reject means reject

Kane caught a visitor being tracked after they clicked “Reject”. Claude Code fixed it. Kane proved the fix.

2 → 0tracker requests without consent
2rounds
3Kane runs in a real browser
46.0Kane credits
Exhibit A · what Kane recorded

Kane found no way to refuse cookies, and 2 tracker requests went out before the visitor made any choice.

Kane's screenshot, step 6: Waiting after completing the navigation and reload tasks. The outline marks what it clicked.
WhenTrackerRequestTimesVisitor ID sent
During the visitgoogletagmanager.com tag manager code only, not countedGET www.googletagmanager.com/gtag/js3
During the visitgoogle-analytics.comPOST www.google-analytics.com/g/collect2137328153.1794929716
What happened
  1. Round 1 · Kane · Reject means reject

    Violation

    Kane found no way to refuse cookies, and 2 tracker requests went out before the visitor made any choice.

    1. Step 1: Navigate to http://localhost:30001 Navigate to http://localhost:3000
    2. Step 2: Clicking Lumen Plus in the site navigation2 Clicking Lumen Plus in the site navigation
    3. Step 3: PRIMARY: Reload that page3 PRIMARY: Reload that page
    4. Step 4: A cookie or analytics consent banner is shown.4 A cookie or analytics consent banner is shown.
    5. Step 5: Waiting do not look for one5 Waiting do not look for one
    6. Step 6: Waiting after completing the navigation and reload tasks6 Waiting after completing the navigation and reload tasks
    Step 1 · Navigate to http://localhost:3000Step 2 · Clicking Lumen Plus in the site navigationStep 3 · PRIMARY: Reload that pageStep 4 · A cookie or analytics consent banner is shown.Step 5 · Waiting do not look for oneStep 6 · Waiting after completing the navigation and reload tasks
  2. Round 1 · Claude Code

    Changed the app

    The Google tag was hardcoded in every page's <head> and loaded straight away, so it ran before any choice and the site had no way to decline.

    In server.js I removed that static tag and added an Accept/Decline banner. The tag now loads only when the stored choice is "accepted", or right after the visitor clicks Accept. On first visit, and after Decline, nothing loads. node --check server.js passes, but I haven't run the app or re-run Kane against it.

  3. Round 2 · Kane · Reject means reject

    Proven

    Kane refused cookies and recorded 11 requests; none went to a known tracker and no visitor ID was sent.

    1. Step 1: Navigate to http://localhost:30001 Navigate to http://localhost:3000
    2. Step 2: A cookie or analytics consent banner is shown.2 A cookie or analytics consent banner is shown.
    3. Step 3: Clicking Decline on the cookie consent banner3 Clicking Decline on the cookie consent banner
    4. Step 4: Clicking Lumen Plus in the top navigation4 Clicking Lumen Plus in the top navigation
    5. Step 5: Waiting after reloading the opened Lumen Plus page5 Waiting after reloading the opened Lumen Plus page
    Step 1 · Navigate to http://localhost:3000Step 2 · A cookie or analytics consent banner is shown.Step 3 · Clicking Decline on the cookie consent bannerStep 4 · Clicking Lumen Plus in the top navigationStep 5 · Waiting after reloading the opened Lumen Plus page
  4. Round 2 · Kane · Accept still works

    Proven

    After "Accept", the tags loaded as intended (google-analytics.com, googletagmanager.com).

    1. Step 1: Navigate to http://localhost:30001 Navigate to http://localhost:3000
    2. Step 2: Accepting cookie consent in the banner2 Accepting cookie consent in the banner
    3. Step 3: Clicking Lumen Plus in the top navigation bar3 Clicking Lumen Plus in the top navigation bar
    4. Step 4: Waiting after opening one page from the site's navigation4 Waiting after opening one page from the site's navigation
    Step 1 · Navigate to http://localhost:3000Step 2 · Accepting cookie consent in the bannerStep 3 · Clicking Lumen Plus in the top navigation barStep 4 · Waiting after opening one page from the site's navigation
The rule

When a visitor refuses cookies, no advertising or analytics tracker may load, before the choice or after it, and no visitor ID may be sent to a tracker.

Why it matters
  • ePrivacy Directive 2002/58/EC, Art. 5(3): storing or reading non-essential data on a device needs prior consent
  • GDPR (EU) 2016/679, Art. 4(11) and Art. 7: consent must be freely given and as easy to withdraw as to give
  • California Civil Code §1798.120 (CCPA/CPRA): consumers may opt out of the sale or sharing of their personal information