What does readthedocs.org track?
Before any consent, readthedocs.org loaded 1 tracking company and set 0 advertising or analytics cookies.
That's fewer tracking companies than most sites we scanned: 75% of the 2,450 sites we checked loaded more.
Scanned October 2, 2026 from Germany, loading about.readthedocs.com/?ref=app.readthedocs.org once and clicking nothing. How we scan
- Tracking companies
- 1
- Tracking cookies
- 0
- Third-party hosts
- 5
- Cookies in total
- 3
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 analytics companies.
- Plausible1 requestAnalytics
plausible.io
Other third parties (content delivery, consent, functional, unclassified)
- GitHub3 requestsFunctional
avatars.githubusercontent.com, github.com
- Font Awesome52 requestsContent delivery
ka-p.fontawesome.com, kit.fontawesome.com
Cookies set before consent
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.