What does jw.org track?
jw.org loaded no advertising or analytics trackers before consent.
Scanned October 2, 2026 from Germany, loading www.jw.org/en once and clicking nothing. How we scan
- Tracking companies
- 0
- Tracking cookies
- 0
- Third-party hosts
- 6
- Cookies in total
- 1
Consent banner
No known consent management platform was detected on the page.
Companies contacted before consent
2 of the 3 companies it contacted before consent were functional companies.
None.
Other third parties (content delivery, consent, functional, unclassified)
Cookies set before consent
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| aws-waf-token | Necessary | www.jw.org | 4 days |
The page also wrote 5 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.