SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.
Incomplete evidence: evidence was cut short before completion (the Worker instrumentation could not record every request, so the request evidence is incomplete). Counts for the affected evidence are lower bounds; families that completed carry only their ordinary limits. The evidence receipt states the exact per-visit quality.
What this actually means
twitch.tv's retained request log includes 1 distinct catalogued tracking-related service.
SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.
Bottom line: activity evidence was cut short, so few signals is not a verdict
Evidence collection did not finish for request evidence, so the quiet result reflects incomplete activity evidence, not a verdict about the site. The scoped effect is that request counts are retained lower bounds. Recorded cause: the Worker instrumentation could not record every request, so the request evidence is incomplete.
The cards below translate the evidence into plain language. This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. The request log, domain table, and methodology remain below for verification.
at least 237 retained requests observed in one controlled visit.
Context
at least 5 retained requests matched Brave Shields filter lists
at least 5 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.
The hand-curated service catalog separately matched at least 3 retained request rows in this visit.Show matched requests
Context
This Shields comparison is not conclusive
The "No blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete. and The "Brave-list blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete.
The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.
Catalogued service domains recorded responses during this visit
Amazon Ads appeared in the request log.
A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Functional catalog labels include advertising. This scan could not identify 2 of the 4 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: Sentry.
at least 43 retained cross-site requests across at least 4 retained third-party hosts.Show third-party requests
Context
Incomplete evidence: No requests to major-platform domains were recorded in retained evidence before collection stopped
No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.
Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped
This visit did not contact Google Analytics.
Neither Google Analytics nor its remarketing sync was observed in this visit. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
The automated visit did not observe third-party cookies.
This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.
6 cookies total in this report.
Nothing observed
No fingerprint-like API calls observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
0 API families recorded.
Raw evidence
Open the interactive evidence explorer
The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.
This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.
cut short: the Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
cut short: the Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.
Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.
This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.
Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. A study has been recorded for pixel-events and does not support a published rate under the current build. How detector accuracy is measured.
Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .