Evidence: 100
Access to terminal-equipment information before a consent choice
- Observation
- Before any consent action (valid before-choice runs: 3; highest value in any run): signal families 13; instrumented API events 23910; fingerprint-like behaviors 9; data-flow-linked transmissions 0; correlated-only transmissions 13; third-party destinations 1.
Technical question Did page scripts read browser or device information through instrumented APIs, or send or store values derived from it, before any consent choice in the measured environment?
- Legal mapping
ePrivacy Directive Art. 5(3) - technical-scope analysis may be required (EDPB Guidelines 2/2023).
Article 5(3)European Data Protection Board (EDPB) (opens in a new tab)
Runs this rule reads
- Before choice3 of 3 valid Before choice runs
- Reject all3 of 3 valid Reject all runs
- Accept all3 of 3 valid Accept all runs
- Not established by this scan
- Whether an exemption applies (for example technical storage or access that is strictly necessary for the provider of an information society service explicitly requested by the subscriber or user to provide that service)
- Controller purpose or lawful basis
- Whether each observation constitutes legally relevant access to, or storage of, information in terminal equipment within the technical scope of Art. 5(3)
- Whether the site operator, a third party, or both determine the purpose of the observed script behavior
Rationale and limitations
Rationale
Instrumented browser or device APIs were accessed before any consent action. Whether this access falls within Art. 5(3) depends on legal predicates that this scan does not establish.
Limitations
- Automated technical check: it reports observations that may be relevant to a legal question and does not decide that question.
- Measured in Chrome (Chromium) 153.0.8010.12 (headless, linux) from egress region tr-workstation; one entry URL, fresh profile, no sign-in. Other browsers, regions, devices and visitor states may differ.
- Fixed observation window of 10 s after load; activity outside the window, and on other pages of the site, is not observed.
- Instrumentation runs in an automated browser; APIs that are not hooked are not recorded, and pages may behave differently for automated browsers.
- Counts are the highest value observed in any single valid run of the scenario; repeated runs of the same scenario can differ.
- Instrumented API access shows that a call happened. It does not by itself show fingerprinting, the identification of a person, or a purpose.
- Data-flow links match values returned by browser APIs, or digests of them, to outgoing payloads; matching can miss encodings and short values can match by coincidence.
- Consent interface detection and control selection are automated (CMP adapters and heuristics); banners can be missed, delayed or region-specific, and the control chosen as most comprehensive may differ from what a visitor sees.
Evidence
Computed facts (9)
These are the exact values the rule conditions read for this scan, so the state can be reproduced from them. Counts are the highest value seen in any single valid run.
| Fact | Computed value |
|---|---|
Before choice: api eventsbefore.api_events | 23,910 |
Before choice: behaviorsbefore.behaviors | 9 |
Before choice: correlated linksbefore.correlated_links | 13 |
Before choice: signal familiesbefore.signal_families | 13 |
Before choice: third party destinationsbefore.third_party_destinations | 1 |
Before choice: valid runsbefore.valid_runs | 3 |
Before choice: verified linksbefore.verified_links | 0 |
Consent interface: action failedconsent.action_failed | no |
Consent interface: banner ambiguousconsent.banner_ambiguous | no |