What does chase.com track?
Before any consent, chase.com loaded 0 tracking companies and set 2 advertising or analytics cookies.
Scanned October 2, 2026 from Germany, loading www.chase.com once and clicking nothing. How we scan
- Tracking companies
- 0
- Tracking cookies
- 2
- Third-party hosts
- 6
- Cookies in total
- 22
Consent banner
No known consent management platform was detected on the page.
Companies contacted before consent
1 of the 3 companies it contacted before consent were unclassified.
None.
Other third parties (content delivery, consent, functional, unclassified)
- chasecdn.com5 requestsUnclassified
static.chasecdn.com
- LexisNexis Risk Solutions (ThreatMetrix)2 requestsFunctional
h64.online-metrix.net, 5g3kt0kjlcbxbtsgmxgq3hvqb2j4327cgfvkywwo30b85e96405a271bam1.e.aa.online-metrix.net
- Akamai3 requestsContent delivery
s2.go-mpulse.net, c.go-mpulse.net, 684dd32b.akstat.io
Cookies set before consent
The longest-lived tracking cookie it set was AMCV_EA673DFC5A2F19060A495C9C@AdobeOrg, from Adobe, lasting about 13 months.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| AMCV_EA673DFC5A2F19060A495C9C@AdobeOrg | Advertising | chase.com | 13 months |
| dtCookie | Analytics | chase.com | Session |
| _tmprememberme | Unclassified | chase.com | Session |
| dfs_E_1 | Unclassified | chase.com | Session |
| dfs_E_4 | Unclassified | chase.com | Session |
| dfs_E_5 | Unclassified | chase.com | Session |
| dfs_E_6 | Unclassified | chase.com | Session |
| dfs_E_7 | Unclassified | chase.com | Session |
| dfs_E_8 | Unclassified | chase.com | Session |
| dfs_F_5 | Unclassified | chase.com | Session |
| dfs_F_6 | Unclassified | chase.com | Session |
| dfs_F_7 | Unclassified | chase.com | Session |
| fireOnce | Unclassified | www.chase.com | Under a day |
| NyJB5Jgn | Unclassified | chase.com | 13 months |
| PC_1_0 | Unclassified | chase.com | Session |
| store~logon~treatmentParameter | Unclassified | chase.com | Session |
| thx_guid | Unclassified | page-format.chase.com | 13 months |
| tml | Unclassified | www.chase.com | 1 day |
| tmx_guid | Unclassified | page-format.chase.com | 13 months |
| v1st | Unclassified | chase.com | 13 months |
| AKA_A2 | Functional | chase.com | Under a day |
| RT | Functional | www.chase.com | 7 days |
The page also wrote 7 keys to local storage, which works like a cookie but isn't sent with requests.
Understanding this page
- How to see which cookies and trackers a website loads
A hands-on walkthrough for checking what a site sets before you've clicked anything, using Chrome and Firefox's built-in tools, plus how CookieTosser automates the same check every month.
- What counts as valid cookie consent in the EU
The rules that actually govern cookie banners — the ePrivacy Directive, the GDPR consent standard, the Planet49 ruling, the strictly-necessary exemption, and what "reject" has to offer compared with "accept.
- Consent management platforms explained
What a CMP banner is actually doing behind the scenes, how the IAB's TCF standard and Google's Consent Mode v2 fit in, and why a banner being present is no guarantee that nothing loads before you answer it.