Northwind Store
https://shop.northwind.example
Observations
- critical
After the reject control on this site's consent banner was activated, Meta Pixel (Meta Platforms) sent 2 further request(s) to www.facebook.com carrying information identifying the browser and the page being viewed.
pre-consent-tracking/tracker-fired-after-reject · 2 requests · first at +5.12s · www.facebook.com
Why this pattern gets examined
A recorded rejection that does not change what is transmitted is the pattern most frequently cited in regulatory decisions on consent banners, because the discrepancy between the interface and the behaviour is directly observable.Background only. Not a statement that any law applies here or was broken.
- high
Meta Pixel (Meta Platforms), an advertising network, received 3 request(s) from this page beginning 0.4 seconds after the page started loading - before the visitor had made any consent choice. The requests were sent to connect.facebook.net, www.facebook.com and carried information identifying the browser and the page being viewed.
pre-consent-tracking/ad-network-before-consent · 3 requests · first at +0.41s · connect.facebook.net, www.facebook.com
Why this pattern gets examined
Transmission of a visitor's browsing activity to an advertising network before a consent choice is recorded is the core factual allegation in the current wave of US session-tracking claims.Background only. Not a statement that any law applies here or was broken.
- high
Hotjar (Contentsquare) began transmitting data 1.1 seconds after the page started loading, before the visitor had made any consent choice. This service reconstructs a replayable recording of the visitor's session, including mouse movement, scrolling and interaction with page elements.
pre-consent-tracking/session-replay-before-consent · 4 requests · first at +1.10s · static.hotjar.com
Why this pattern gets examined
Session recording tools are treated distinctly from ordinary analytics in several frameworks because a third party observes the visitor's interaction with the page in substantially real time.Background only. Not a statement that any law applies here or was broken.
Contacted before a consent choice existed
Scan history
14 chained records| Recorded | Before consent | After reject | Third parties | Chain |
|---|---|---|---|---|
| 12 Aug 2026, 00:57 UTC | 6 | 2 | 11 | #42 |
| 11 Aug 2026, 00:57 UTC | 6 | 2 | 11 | #41 |
| 10 Aug 2026, 00:57 UTC | 6 | 2 | 11 | #40 |
| 09 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #39 |
| 08 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #38 |
| 07 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #37 |
| 06 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #36 |
| 05 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #35 |
| 04 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #34 |
| 03 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #33 |
| 02 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #32 |
| 01 Aug 2026, 00:57 UTC | 5 | 0 | 10 | #31 |
| 31 Jul 2026, 00:57 UTC | 5 | 0 | 10 | #30 |
| 30 Jul 2026, 00:57 UTC | 5 | 0 | 10 | #29 |
Evidence Pack
Any range of these scans exports as a single dated document: what was observed, when, what changed between scans, and the integrity proof - written to be read by someone who has never heard of Provendly.