SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.
Incomplete evidence: evidence was cut short before completion (the visit hit the scanner's request-recording cap, so its counts are truncated; the visit hit the scan proxy's traffic budget, so it stopped forwarding further traffic). 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
apnews.com's retained request log includes catalogued Google, LinkedIn and Meta domains.
SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.
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, cookie counts are an incomplete end-state snapshot and storage counts are an incomplete end-state snapshot.
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 1,000 retained requests observed in one controlled visit.
What was checked
Page
https://apnews.com/
When
Jul 27, 2026, 9:47 AM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the No blocking visit was cut short.
What these visits could not see
Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
Checks with incomplete evidence. In the No blocking visit: every check. Every card below states only what was retained.
Worth checking
at least 465 retained requests matched Brave Shields filter lists
at least 465 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 205 retained request rows in this visit.Show matched requests
Context
This Shields comparison is not conclusive
The "No blocking" visit hit the 1,000-request recording cap, so its counts are truncated. The "No blocking" visit exhausted its proxy connection and target safety budget, 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.
Consent tooling and requests to tracking-service entities appeared before any choice
apnews.com sent a request to OneTrust, a consent management platform (the tooling that shows cookie banners). The request log included at least 19 retained distinct catalogued tracking-related services before the scanner made any consent choice; 19 companies answered.
A request to the platform's loader proves the page attempted to fetch consent tooling. An observed response supports delivery, but neither fact proves a banner was visibly shown to this scanner. Banner display can vary by region and visit context. The scanner never clicks a banner in this mode, so this report records requests made before the scanner made a consent choice. It does not determine whether any request required consent or whether the site's behavior complied with applicable law. More tracking-service entities or requests may appear after "Accept" than this report captures, so the counts here are lower bounds for users who consent.
Consent platform detected via a request to cdn.cookielaw.org.
Opens the request log at its catalog-matched rows, which include requests to the tracking-related services counted here; this visit never clicked the banner.
Context
Tracking companies the privacy policy does not appear to name
LiveRamp, The Trade Desk and Criteo, plus 6 others were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.
Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation. Named in the policy: Magnite, Google and PubMatic, plus 6 others.
Policy at https://apnews.com/…; 0 checkable statements matched; 9 of 18 observed tracking companies named in the policy. Policy mentions of Amazon Ads are unknown because the historical alias matcher was incomplete.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Review-worthy
Catalogued service domains recorded responses during this visit
Magnite, LiveRamp and Google, plus 16 others 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 / supply-side platform, identity / advertising and analytics / tag management. This scan could not identify 124 of the 166 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 940 retained cross-site requests across at least 166 retained third-party hosts.Show third-party requests
Worth checking
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google, Meta and LinkedIn.
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 appears in the retained evidence.
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.
200 third-party cookies showed up during the visit.
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary. This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites.
Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.
Context
Input-monitoring signal involving a third-party script
Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.
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. That is 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. The card therefore 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.
Session-recording listener coverage: 6,199 interaction-listener registrations with https://*.*.permutive.app/, https://*.pub.network/ and https://*.usablenet.com/, plus 15 others in the registration call chain. Input-monitoring listener coverage: 410 input-listener registrations with https://*.*.permutive.app/, https://cdn.cookielaw.org/ and https://cdn.jwplayer.com/, plus 10 others in the registration call chain.
Opens this report's request log filtered to *.*.permutive.app, a script origin recorded in the listener's call chain.
Context
Fingerprint-like browser APIs were called
At least 1 retained high-entropy API call appeared in the incomplete instrumentation log.
These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.
Retained incomplete evidence includes 1 API event record; no exact API-family total is available.
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 visit hit the scanner's request-recording cap, so its counts are truncated; the visit hit the scan proxy's traffic budget, so it stopped forwarding further traffic; 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
complete; 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 .