Site Behavior Lab
Site

www.chase.com

Baseline visit
Requested address
https://www.chase.com/
Report ID
20260810-cf417740643818f3d9fb54a8b4261e0e
Evidence SHA-256
c85bea75669f7d47520cdcfc3cf758b00673e79d35b348bd200ed99176dc891f
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

chase.com triggered fingerprint-like browser API patterns.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.chase.com itselfat least 50 retained requestsrequests that stayed on the site
Catalogued servicesat least 0 retained requestsno retained request matched the service catalog
Hosts the catalog does not nameat least 4 retained requests2 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

5 browser-fingerprinting heuristics matched. These are heuristic review signals, not proof of fingerprinting intent. 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.

≥2cross-site domains
≥4cross-site requests
5fingerprint-like patterns

Worth checking

Bottom line: this visit has signals worth checking

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 54 retained requests observed in one controlled visit.

What was checked

Page
https://www.chase.com/
When
Aug 10, 2026, 6: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
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. 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 both visits: Brave Shields matches, the privacy policy check, third-party services, named platforms, Google Analytics remarketing, advertising pixels and the consent banner. Each linked card states what was retained.

Context

At least 2 retained requests matched Brave Shields filter lists

At least 2 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 0 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete. The "Brave-list blocking" visit had one or more requests refused by the scanner's own network guard, 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.

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

Context

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. As a result, nothing was compared against this visit's evidence (no catalogued tracking companies observed to check against it). That is a limit of the automated check, not a finding about the site either way.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

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.

Policy at https://www.chase.com/…/privacy/…; 0 checkable statements matched; no catalogued tracking companies observed to check against it.

Context

Incomplete evidence: No known services matched in retained evidence before collection stopped

No third-party domain in the retained evidence matched the service catalog or another identity source.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

No known operator or catalog entity was matched. This scan could not identify 2 of the 2 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 4 retained cross-site requests across at least 2 retained third-party hosts.Show third-party requests

Context

Incomplete evidence: No requests to catalogued major-platform domains were recorded in retained evidence before collection stopped

No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains appear in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users.

At least 2 retained cross-site domains seen overall.Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

No Google Analytics request appears in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Neither Google Analytics nor its remarketing sync was observed in this visit.

No google-analytics.com, analytics.google.com or googletagmanager.com requests.Show catalog-matched requests

Not flagged

No third-party cookies observed

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.

17 cookies total in this report.

Worth checking

Behavioral fingerprinting heuristics matched

5 behavioral heuristics matched: Canvas fingerprinting heuristic, Offline audio rendering heuristic, Canvas font probing heuristic, WebGL entropy-read heuristic and WebRTC peer-connection probing.

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.

Canvas fingerprinting heuristic: 2 canvases matched; reads: canvas.toDataURL. Offline audio rendering heuristic: 1 offline render with audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering. Canvas font probing heuristic: 218 measureText calls across up to 92 fonts; measured text contents are not stored. WebGL entropy-read heuristic: 9 parameter reads and 1 pixel readback; parameters: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL. Plus 1 other detection.

Domain evidence

4 recorded domains

These are retained domain rows, not a complete inventory.

The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 7 sCatalog matchRoleResource types
www.chase.com37No catalog matchfirst-partydocument, stylesheet, image, script, fetch
*.chase.com13No catalog matchfirst-partyfont, script, other, xhr, fetch
*.go-mpulse.net2No catalog matchthird-partyscript, xhr
static.chasecdn.com2No catalog matchthird-partyfetch, script

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.

Report ID
20260810-cf417740643818f3d9fb54a8b4261e0e
Site
www.chase.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
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; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
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 scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
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 .