Baseline visit v2 schema (r2)

homedepot.com

https://www.homedepot.com/

Aug 14, 2026, 7:15 PM UTC

cut short: fingerprinting evidence was censored before completion — the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); recorded by the scanner

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

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: evidence was cut short before completion (fingerprinting evidence was censored before completion — the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); and 2 more). 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.

Scan report ready for homedepot.com: 338 recorded request rows.

Comparison Reportv2 schema (r2)

homedepot.com

https://www.homedepot.com/
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.

What this actually means

homedepot.com's observed Meta Pixel requests contained populated identifier fields.

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.

6tracking-service entities
302cross-site requests
14third-party cookie records
≥4fingerprint-like patterns retained

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

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 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; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.

338 requests observed in one controlled visit.

Worth checking

115 of 290 requests the engine evaluated matched Brave Shields filter lists

115 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 55 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. and The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than 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.

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

Worth checking

2 first-party DNS aliases matched tracking checks

Recorded DNS aliases resolve to catalogued tracking-related services: Adobe. 1 resolved target matched Brave filter lists; those matches do not identify the operators.

The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. A filter-list match alone is not a verified service identity or proof of tracking.

{label}.homedepot.com → {label}.online-metrix.net (Brave filter-list match; operator unverified) and {label}.homedepot.com → {label}.{label}.{label}.{label}.{label}.omtrdc.net (Adobe; catalog match)Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Google, Quantum Metric and Adobe, plus 3 others were sent requests during this visit, but 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.

Policy at https://www.homedepot.com/privacy/{seg}; 0 checkable statements matched; 0 of 6 observed tracking companies named in the policy.

Review-worthy

Catalogued service domains recorded responses during this visit

Google, Quantum Metric and Adobe, plus 3 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, analytics / tag management and session replay / product analytics. This scan could not identify 20 of the 36 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: Quantum Metric; the domain match alone does not prove that a recording occurred. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: HUMAN Security.

302 cross-site requests across 36 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 Microsoft, plus 1 other.

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

24 requests to these platforms.Show catalog-matched requests

Worth checking

Advertising pixels carried populated identifier fields

Meta Pixel attached populated personal-identifier fields (external ID) to requests observed in this visit.

Recognized identifier fields held non-empty values. The scanner records their categories, never their values, so their contents, hashing, successful delivery, and eventual use are not verified. Event labels do not establish that the corresponding user action occurred.

Meta Pixel: custom event and PageView; identifiers external ID (2 requests)Show catalog-matched requests

Nothing observed

Google Analytics present, no remarketing signal

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.

Google Analytics host observed; no stats.g.doubleclick.net request.Show catalog-matched requests

Review-worthy

Third-party cookies were present

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

55 cookies total in this report.High third-party cookies count (at or above the 12 reference threshold).

Worth checking

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

174 interaction-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 5 others in the registration call chain, 42 input-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 4 others in the registration call chain and known session-replay vendor(s): Quantum Metric

Worth checking

Behavioral fingerprinting heuristics matched

At least 4 behavioral heuristics matched in retained evidence: Offline audio rendering heuristic, Canvas fingerprinting heuristic, Canvas font probing heuristic and WebRTC peer-connection probing.

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.

2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 2 others, 1 canvas matched; reads: canvas.toDataURL, 10 measureText calls across up to 10 fonts; measured text contents are not stored and 2 peer connections with 2 data channels, 2 offers, and 2 local descriptions

GPC Comparison

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

GPC off: 16,228msGPC on: 16,260ms
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.
  • 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.
  • 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 fingerprint-heuristics detector's status differed between the two visits, so their numbers measure different things. The keystroke-exfiltration detector's status differed between the two visits, so their numbers measure different things. 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 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.
  • Fingerprinting deltas (each visit's own evidence still renders below): At least one visit did not complete the fingerprint measurement, so no exact cross-visit delta is shown.
  • Ad-pixel deltas (each visit's own evidence still renders below): At least one visit did not complete the pixel measurement, so no exact cross-visit delta is shown.

Measurement limits

8 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.
  • The page did not reach network idle before the scan window ended.
  • The in-page fingerprint observer could not read one or more frames, so fingerprint-like API calls and heuristics for this visit are incomplete.
  • This scan typed a synthetic test value into 1 form field (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.
  • Resolved 2 first-party subdomains that are CNAME aliases for third-party trackers (CNAME cloaking), which request-URL matching alone would miss.
  • Read the site's privacy policy (https://www.homedepot.com/privacy/{seg}) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.

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-0d43cea9be32d1d52650401b4661cce3
Site
homedepot.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: fingerprinting evidence was censored before completion — the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 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: request evidence was censored before completion — the producer recorded an additional collection loss (recorded loss count: 13); fingerprinting evidence was censored before completion — the in-page fingerprint observer did not finish (recorded loss count: 2); detector output evidence was censored before completion — the synthetic keystroke probe did not finish (recorded loss count: 1); 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. 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 .