What is the django_language cookie?
django_language is a native cookie generated by Django's internationalization (i18n) module, used by thousands of websites and web applications built in Python. It is not a third-party service like Google or Meta, but a built-in feature of the application code running on the server itself.
The cookie typically appears when a visitor manually switches the site's language via a language selector, or when Django automatically detects the preferred language from the browser's settings (the Accept-Language header) and stores it for future visits.
What data it stores
The cookie's value is typically a short language code (for example „en”, „ro”, or „en-us”), matching the language codes configured in that particular Django application. It does not contain personal data, unique user identifiers, or tracking information.
The data stays stored in the visitor's browser and is sent only to the site's own domain (the server running the Django application) with each request, so the correct language content can be rendered. Exact format and subdomain details may vary depending on each application's configuration.
What it is used for
The cookie's purpose is purely functional: it lets the site remember the visitor's preferred language across pages and visits, without them having to reset it every time. For site owners, this means a more consistent browsing experience and fewer redundant clicks for international users.
It is not used for advertising, profiling, or statistical analysis – its only function is remembering the language preference.
Does it require consent?
In CookieFix's classification, django_language falls under „preferences (functional)”. From a strictly technical standpoint, some authorities treat language cookies as close to strictly necessary when the language directly determines the requested content's display; however, since it is not indispensable to the site's basic operation (the site can still show a default language without it), it is prudent to treat it as a preference cookie subject to consent under the ePrivacy Directive (2002/58/EC) and GDPR.
- It should generally be included in the consent banner, under the preferences category.
- It must always be disclosed in the cookie policy, regardless of category.
- It should not be set before consent if the site classifies it as non-essential.
How to block or delete django_language
A visitor can delete or block this cookie at any time from their browser settings (Chrome, Firefox, Edge, Safari), in the per-site cookie management section. Blocking it does not affect the site's core functionality – it only means the preferred language won't be remembered across visits.
For site owners, a consent management platform like CookieFix can automatically block scripts that set preference cookies – including those generated by Django – until the visitor gives consent, helping meet the prior-consent requirement.
Frequently asked questions
No. It is a functional cookie that only stores the visitor's preferred language and contains no identifying or tracking data.
The site will revert to its default language or detect the browser's language again on the next visit, with no other functional consequences.
Since it is classified as a preference cookie and is not strictly necessary, it is recommended to include it in the consent banner and only activate it after acceptance.
It is set directly by the web application built with the Django framework, not by an external provider or third-party service.