What does sicredi.com.br track?
Before any consent, sicredi.com.br loaded 7 tracking companies and set 14 advertising or analytics cookies.
That's more tracking companies than 86% of the 2,450 sites we scanned. Among the 23 other .com.br sites we scanned, the typical one loaded 6 tracking companies — sicredi.com.br loaded more.
Scanned October 2, 2026 from Germany, loading www.sicredi.com.br/home once and clicking nothing. How we scan
- Tracking companies
- 7
- Tracking cookies
- 14
- Third-party hosts
- 27
- Cookies in total
- 22
Consent banner
No known consent management platform was detected on the page.
Companies contacted before consent
3 of the 11 companies it contacted before consent were social media companies.
- Google Ads7 requestsAdvertising
ad.doubleclick.net, stats.g.doubleclick.net, www.google.de
- Meta50 requestsSocial media
connect.facebook.net, www.facebook.com
- TikTok20 requestsSocial media
analytics.tiktok.com, analytics-ipv6.tiktokw.us
- LinkedIn4 requestsSocial media
snap.licdn.com, px.ads.linkedin.com
- Google Analytics24 requestsAnalytics
www.googletagmanager.com, region1.analytics.google.com
- Microsoft Clarity4 requestsAnalytics
z.clarity.ms, www.clarity.ms, scripts.clarity.ms
- Hotjar3 requestsAnalytics
script.hotjar.com, static.hotjar.com
Other third parties (content delivery, consent, functional, unclassified)
- Google21 requestsFunctional
www.google.com, script.google.com, script.googleusercontent.com
- Google Cloud9 requestsContent delivery
mpc-prod-27-s6uit34pua-uk.a.run.app, mpc2-prod-23-is5qnl632q-ue.a.run.app, mpc2-prod-25-is5qnl632q-wl.a.run.app, mpc2-prod-28-is5qnl632q-ue.a.run.app
- Akamai2 requestsContent delivery
s.go-mpulse.net, c.go-mpulse.net
- Amazon Web Services2 requestsContent delivery
sl-11a463aaedf44600a99367660fd6fa70.ecs.us-east-1.on.aws, k6-e4e4123be8e54363900a90353991ca93.ecs.us-west-1.on.aws
Cookies set before consent
The longest-lived tracking cookie it set was _ga, from Google Analytics, lasting about 13 months.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| _fbp | Advertising | sicredi.com.br | 3 months |
| _gcl_au | Advertising | sicredi.com.br | 3 months |
| _tt_enable_cookie | Advertising | sicredi.com.br | 13 months |
| _ttp | Advertising | tiktok.com (third party) | 13 months |
| _ttp | Advertising | sicredi.com.br | 13 months |
| bcookie | Advertising | linkedin.com (third party) | 12 months |
| lidc | Advertising | linkedin.com (third party) | 1 day |
| ttcsid | Advertising | sicredi.com.br | 13 months |
| ttcsid_CCN0EVRC77UE78HT5D60 | Advertising | sicredi.com.br | 13 months |
| ttcsid_D0JLP23C77UB3ELEIBTG | Advertising | sicredi.com.br | 13 months |
| ttcsid_D3T96LRC77U1STIOQUA0 | Advertising | sicredi.com.br | 13 months |
| _ga | Analytics | sicredi.com.br | 13 months |
| _ga_186Q22521H | Analytics | sicredi.com.br | 13 months |
| _ga_NKVD566DEP | Analytics | sicredi.com.br | 13 months |
| __cf_bm | Functional | linkedin.com (third party) | Under a day |
| _abck | Functional | sicredi.com.br | 12 months |
| _hjSession_2004202 | Functional | sicredi.com.br | Under a day |
| _hjSessionUser_2004202 | Functional | sicredi.com.br | 12 months |
| ak_bmsc | Functional | sicredi.com.br | Under a day |
| li_gc | Functional | linkedin.com (third party) | 6 months |
| RT | Functional | www.sicredi.com.br | 7 days |
| bm_sz | Necessary | sicredi.com.br | Under a day |
The page also wrote 4 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.