Site Behavior Lab
Site

www.bankofamerica.com

Baseline visit
Requested address
https://www.bankofamerica.com/
Report ID
20260817-9b38be306ac2cba0b5cdce71f68d724c
Evidence SHA-256
9f800cdf1e28ce8239d02e5486db393febcf1e7912823ae04f8749a02ba7cf9f
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

bankofamerica.com recorded 16 fewer third-party requests in the visit configured for Brave-list blocking.

Where this page's requests went

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

No blocking

www.bankofamerica.com itself99 requestsrequests that stayed on the site
Catalogued services17 requests2 names: Tealium 16, Adobe 1
Hosts the catalog does not name98 requests8 hosts; the catalog cannot say who operates them

Brave-list blocking

www.bankofamerica.com itself43 requestsrequests that stayed on the site
Catalogued services16 requests1 name: Tealium 16
Hosts the catalog does not name83 requests3 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
  • not measured

The visit with no blocking made 214 requests; the visit configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit) recorded 16 fewer third-party requests. The blocker directly stopped 9 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance. 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.

2tracking-service entities
115cross-site requests
4third-party cookie records
≥1fingerprint-like pattern retained

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

Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web. Details

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.

214 requests observed in one controlled visit.

What was checked

Page
https://www.bankofamerica.com/
When
Aug 17, 2026, 5:57 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: CNAME cloaking, the consent banner, the privacy policy check, fingerprinting, session-recording signals, the typing test and advertising pixels. Each linked card states what was retained.

Worth checking

41 requests matched Brave Shields filter lists

41 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 17 request rows in this visit.Show matched requests

Not flagged

Lower values observed across comparable metrics in the Brave-list blocking attempt

The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 16 fewer third-party requests, 4 fewer third-party cookies and 1 fewer tracking-related service request.

Treat this as an observed difference, not a measured blocking rate. Details

Services only seen in the unblocked visit: Adobe. The blocking visit's engine directly blocked 9 requests; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments).

Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests

Worth checking

1 first-party DNS alias matched tracking checks

Of the resolved targets, 1 matched Brave filter lists; those matches do not identify the operators.

These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. Details

The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. A filter-list match alone is not a verified service identity or proof of tracking.

DNS alias: *.bankofamerica.com → *.*.*.we-stats.com (Brave filter-list match; operator unverified).Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Tealium and Adobe 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.

Policy at https://*.bankofamerica.com/en/privacy; 0 checkable statements matched; 0 of 2 observed tracking companies named in the policy.

Look closer

Show catalog-matched requests

Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.

Context

Catalogued service domains recorded responses during this visit

Tealium and Adobe 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 tag management / customer data and analytics / advertising. This scan could not identify 5 of the 10 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

115 cross-site requests across 10 third-party hosts. This report does not record which requests came during the typing test.At or above the median for third-party domains across the 86 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests

Not flagged

No requests to catalogued major-platform domains were recorded

No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.

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

10 cross-site domains seen overall.Show catalog-matched requests

Not flagged

No Google Analytics observed

This visit did not contact Google Analytics.

This does not prove the site never uses Google Analytics; it means this visit recorded no request to it. 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

Context

Third-party cookies were present

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

55 cookies total in this report.At or above the median for third-party cookies across the 86 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Worth checking

Canvas fingerprinting heuristic matched

At least 1 behavioral heuristic matched in retained evidence: Canvas fingerprinting 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.

Canvas fingerprinting heuristic: 1 canvas matched; reads: canvas.toDataURL.

Domain evidence

13 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 10.6 sCatalog matchRoleResource types
*.bankofamerica.com64No catalog matchfirst-partyscript, fetch, xhr, document
www2.bac-assets.com46No catalog matchthird-partystylesheet, image, script, font
*.bac-assets.com34No catalog matchthird-partyxhr, script, image, stylesheet, font
secure.bankofamerica.com34No catalog matchfirst-partyxhr, script, fetch
*.tiqcdn.com16Tealium: tag management / customer dataservicescript
cdn.cookielaw.org12No catalog matchthird-partyscript, xhr, fetch, image
*.glancecdn.net2No catalog matchthird-partyscript
*.demdex.net1Adobe: analytics / advertisingservicefetch
*.onetrust.com1No catalog matchthird-partyxhr
*.agkn.com1No catalog matchthird-partyimage
*.advanced-web-analytics.com1No catalog matchthird-partydocument
*.*.onetrust.com1No catalog matchthird-partyping
www.bankofamerica.com1No catalog matchfirst-partydocument

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
20260817-9b38be306ac2cba0b5cdce71f68d724c
Site
www.bankofamerica.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the in-page fingerprint observer could not read every frame, so the fingerprinting 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 in-page fingerprint observer could not read every frame, so the fingerprinting 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.

Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 98 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.

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 .