Privacy
djangodocs.dev has no accounts, no cookies and no advertising. It counts how it is used, without knowing who uses it. This page says what is collected, where it goes, and for how long.
Reading the documentation
Pages load a small script from fivebar, a cookieless analytics service. For each page it sends the page’s address, the page you came from, the width of your window, and, as you leave, how long the page was open, how far down you read and how quickly it loaded. It also sends which language and which Django version you were reading, and the words you searched the documentation for.
fivebar keeps counts, never a record of one person: so many views of a page, from a country, in a browser, on a day. Your IP address and browser’s user agent are used to work out your country and browser, and to count you once a day, and are not kept. Search terms are kept in lower case, and never one that looks like an email address or a long number such as a phone number.
The counts are public, at fiveb.ar/djangodocs.dev.
fivebar’s privacy policy sets out in full
what it receives and keeps. A content blocker that blocks
fiveb.ar stops the script altogether, and the site works the same
without it.
Searching
Search is answered by this site from its own index. The site does not keep what you searched for; the count above is the only record of it.
The MCP server
An app that uses the documentation through djangodocs.dev/mcp needs no account and sends no key. Each tool call is counted in fivebar, as a view of the tool’s name, with:
- whether the call succeeded, and how long it took;
- the Django version and language it asked about;
- the name the app gives itself, such as
claude-ai; - the session id the app hands back on each call, a random one the server makes and does not store;
- the IP address and user agent the call came from, which for most apps are those of the app’s own servers rather than of the person using it.
What the call asked for, such as the search terms or the page fetched, is not sent. fivebar uses the address, user agent and session id to tell callers apart and to place them in a country, and keeps none of the three.
In your browser
Where a page shows commands for both Linux and macOS and Windows, the one you pick is remembered in your browser’s local storage, so other pages show it first. It is never sent anywhere. Nothing else is stored in your browser.
Hosting
The site runs on Cloudflare, which receives every request, and with it your IP address and the details any website sees. Cloudflare uses them to serve and protect the site, and may ask your browser to report network errors back to it. When something goes wrong in the site’s own code, the error is logged at Cloudflare for finding the fault, and deleted within days. See Cloudflare’s privacy policy.
Nothing is sold or shared with anyone else, and no other company’s scripts, fonts or trackers are loaded. Links to docs.djangoproject.com and other sites take you to them, under their own policies.
Who runs it
djangodocs.dev is run by Jason Cartwright, who decides what it collects, and is not affiliated with the Django Software Foundation. Because nothing kept identifies you, there is no record of your visits to show, correct or delete; to ask about anything here, get in touch through that site.
Changes
When what the site collects changes, this page changes with it. It last changed on 25 October 2026.