Site

bestbuy.com

Baseline visit
Requested address
https://www.bestbuy.com/
Report ID
20260814-29926bfc6a13763e10942d71b3ecc272
Evidence SHA-256
a72421d180f92b5527d69f7217afc43617376598197511ea2a25aad5ced616de
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

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.

Read the public review record

bestbuy.com's retained request log includes catalogued Google and Microsoft domains.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

GPC off

bestbuy.com itselfat least 234 retained requestsrequests that stayed on the site
Catalogued servicesat least 118 retained requests9 names: Google 94, Adobe 8, OpenX 6, Criteo 2, LiveRamp 2, and 4 more
Hosts the catalog does not nameat least 112 retained requests22 hosts; the catalog cannot say who operates them

GPC on

bestbuy.com itselfat least 225 retained requestsrequests that stayed on the site
Catalogued servicesat least 14 retained requests6 names: Adobe 7, Google 2, Lotame 2, LiveRamp 1, Magnite 1, and 1 more
Hosts the catalog does not nameat least 39 retained requests11 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • the count is a lower bound; more may exist
  • not measured

Retained request rows include 9 distinct catalogued tracking-service entities; 9 of the retained service matches recorded responses across at least 38 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled GPC off, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script and 3 browser-fingerprinting heuristics matched. 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.

≥9tracking-service entities retained
≥230cross-site requests
18third-party cookie records
3fingerprint-like patterns

Review-worthy

Bottom line: this visit has review-worthy signals

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.

This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. Details

The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.

At least 464 retained requests observed in one controlled visit.

What was checked

Page
https://www.bestbuy.com/
When
Aug 14, 2026, 7:14 PM 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
Typed a made-up test value into 2 form fields in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's 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 both visits: Brave Shields matches, third-party services, named platforms, Google Analytics remarketing, advertising pixels, the consent banner and the privacy policy check. Each linked card states what was retained.

Worth checking

At least 118 retained requests out of 273 requests the engine evaluated matched Brave Shields filter lists

At least 118 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

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. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched at least 118 retained 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 variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not comparable totals.

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.

3 disqualifying conditions named by the report's claim policy.

Review-worthy

Catalogued service domains recorded responses during this visit

Google, Adobe and OpenX, plus 6 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. Details

Functional catalog labels include advertising, analytics / tag management and analytics / advertising. This scan could not identify 19 of the 38 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 230 retained cross-site requests across at least 38 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 and Microsoft.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

At least 95 retained requests to these platforms.Show catalog-matched requests

Context

Google Tag Manager loaded; a remarketing sync cannot be told from this report

This visit contacted Google Tag Manager and recorded no request to a Google Analytics collection host. It also recorded DoubleClick hosts whose names this report generalizes, the remarketing sync host's among them.

This report neither shows nor rules out the sync. Details

Tag Manager is a loader. It can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

googletagmanager.com observed; no google-analytics.com or analytics.google.com request; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Review-worthy

Third-party cookies were present

18 third-party cookies showed up during the visit.

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. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

41 cookies total in this report.

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. Details

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: 8 interaction-listener registrations with https://*.*.doubleclick.net/, https://www.googletagmanager.com/ and https://www.gstatic.com/ in the registration call chain. Input-monitoring listener coverage: 4 input-listener registrations with https://www.googletagmanager.com/ and https://www.gstatic.com/ in the registration call chain.

Worth checking

Behavioral fingerprinting heuristics matched

3 behavioral heuristics matched: Offline audio rendering heuristic, Canvas fingerprinting heuristic and Canvas font probing heuristic.

They are review prompts for this visit, not proof of cross-site identity tracking. Details

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.

Offline audio rendering heuristic: 2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 2 others. Canvas fingerprinting heuristic: 1 canvas matched; reads: canvas.toDataURL. Canvas font probing heuristic: 9 measureText calls across up to 9 fonts; measured text contents are not stored.

Scan report ready for bestbuy.com: 464 recorded request rows.

Comparison Reportrequest evidence incomplete

bestbuy.com

Recorded final address https://www.bestbuy.com/

The selected visit did not finish collecting request evidence. Request counts are lower bounds; Run quality records the reason.

ShareDownloads the GPC off visit's request CSV, source report and correction context in a ZIP. Follows the evidence switcher below.PDF + evidence (opens in a new tab)Downloads a ZIP containing the PDF for every recorded visit, exact source JSON, correction context and file hashes. The scanner renders it on request.

GPC Comparison

GPC off and GPC on: two visits, no comparable metric delta

GPC off: started Aug 14, 2026, 7:14 PM UTC · 29,789msGPC on: started Aug 14, 2026, 7:14 PM UTC · 30,821msRan first: GPC on
No metric deltas are comparable across these two visits, so none are shown.
  • Request, cookie, and storage deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not comparable totals.
  • Catalog-matched request and entity deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not comparable totals.
  • Other detector and causal-path deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The pair did not record the privacy-policy detector's status for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The baseline visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not comparable totals.
  • The Shields-number delta (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not comparable totals.
  • Fingerprinting deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Ad-pixel deltas (each visit's own evidence still renders below): The GPC off visit did not complete this measurement, so it has no exact count. The GPC on visit did not complete this measurement, so it has no exact count. The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.

Measurement limits

7 conditions affect how this evidence reads

Both visits

  • Each visit in this report is one automated, headless Chromium visit from a fixed en-US / UTC profile, with no scrolling, clicking, or consent interaction. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Counts are a lower bound: trackers that load only after interaction or consent are not observed; Service Workers are blocked, and Web Worker or WebSocket traffic may be incomplete. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled. Cookie and storage figures are an end-of-visit snapshot, with storage keys read from the top frame only.
  • Blocked a request that could not be verified as public: https://{label}.{label}.addthis.com/{seg}/{seg}
  • Blocked a request that could not be verified as public: https://{label}.owneriq.net/{seg}/{seg}/{seg}
  • The page did not reach network idle before the scan window ended.
  • This scan typed a synthetic test value into 2 form fields (never submitting the form) to test whether typed input is captured and sent to third parties. The value is synthetic and is not stored. Requests the page sent during and after this typing, including any unload beacons, are part of the recorded request log and counts.

GPC on visit only

  • The scan blocked or could not verify one or more Web Workers while applying the simulated GPC signal; request evidence may be incomplete.

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.

Report ID
20260814-29926bfc6a13763e10942d71b3ecc272
Site
bestbuy.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 2); detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

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. 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 .