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
wordpress.org's retained request log includes catalogued Google domains.
Retained request rows include 1 distinct catalogued tracking-service entity; 1 of the retained service matches recorded responses across at least 6 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. It also looks like 1 browser-fingerprinting heuristic matched.
The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds.
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 50 retained requests observed in one controlled visit.
Context
at least 7 retained requests matched Brave Shields filter lists
at least 7 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 5 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.
Privacy policy read; it made no statement this scan can check
None of the statements this scan knows how to check appear in the policy text, so nothing was compared against this visit's evidence (1 of 1 observed tracking company named in the policy). That is a limit of the automated check, not a finding about the site either way.
Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
Policy at https://wordpress.org/about/privacy; 0 checkable statements matched; 1 of 1 observed tracking company named in the policy.
Context
Catalogued service domains recorded responses during this visit
Google 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 analytics / tag management and advertising. This scan could not identify 3 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.
at least 21 retained cross-site requests across at least 6 retained third-party hosts.Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
Incomplete evidence: Google Analytics present, no remarketing signal in retained evidence before collection stopped
Google Analytics was observed, but no DoubleClick remarketing sync appeared in this visit.
Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
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 canvas matched; reads: canvas.getImageData
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. 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 .