cut short: detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 1 privacy-policy visit was cut off at the configured ceiling; recorded by the scanner
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 (detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 1 privacy-policy visit was cut off at the configured ceiling). 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
pinterest.com triggered fingerprint-like browser API patterns.
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.
The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.
The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from the report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort, with each percentile card naming its metric-specific measured-site denominator (among 98 sites with a successful load across all cohorts; other methodologies, request-capped visits, and post-choice consent visits are excluded from this denominator, while failed or block-page attempts are outside that coverage), a curated set of popular, mostly commercial sites, not a random sample of the web, and otherwise uses fixed reference thresholds. The request log, domain table, and methodology remain below for verification.
140 requests observed in one controlled visit.
Context
5 of 122 requests the engine evaluated matched Brave Shields filter lists
5 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 0 request rows in this visit.Show matched requests
Context
This GPC comparison supports no comparable delta
The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
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.
1 disqualifying condition named by the report's claim policy.
Context
Other third-party operators were identified outside the tracking-service catalog
Google were named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as tracking services.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking. This scan could not identify 2 of the 6 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
104 cross-site requests across 6 third-party hosts.Below the median for third-party domains across the 54 sites measured for this metric.Show third-party requests
Context
Requests were dispatched to major-platform domains the catalog does not carry
This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.
Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload. These domains are not counted as catalog-matched requests.
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.
8 cookies total in this report.No third-party cookies observed.
Context
Input-monitoring signal involving a script from another domain
Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain, whose operator this scan did not establish.
This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Stack attribution records the script origins present in the bounded registration call chain; a cross-site origin in that chain does not by itself establish that the cross-site script registered the listener, because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain, so the card says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected); treat this card as a review prompt rather than proof.
112 interaction-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain and 41 input-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain
These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup. They are review prompts for this visit, not proof of cross-site identity tracking.
1 offline render with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering and 1 canvas matched; reads: canvas.toDataURL
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: detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 1 privacy-policy visit was cut off at the configured ceiling; recorded by the scanner
cut short: detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 1 privacy-policy visit was cut off at the configured ceiling; recorded by the scanner
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. 16 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 13 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. 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 .