What is the locale cookie?
"locale" is a common cookie name used by numerous web platforms and applications (content management systems, front-end frameworks, e-commerce platforms, SaaS apps) to remember a visitor's language and/or region preference. There is no single "provider" — essentially any multilingual website can set a cookie under this name or a similar one (e.g. "lang", "language", "i18next").
The cookie usually appears as soon as the visitor manually selects a language from a menu, or sometimes automatically, based on the browser's detected language, on the first page load.
What data it stores
The stored value is typically a short language and/or region code (for example something similar to "en", "en-US" or "ro-RO"), without directly identifiable personal data. The exact format varies between implementations, since each platform defines its own logic.
The data generally stays stored locally in the visitor's browser and is sent to the site's server with each request so it can render content in the correct language. The cookie is usually not shared with third parties.
What it is used for
The main purpose is functional: the site automatically displays content in the visitor's preferred language or regional variant, without requiring them to pick it again on every page or every new visit.
For the site owner, this cookie improves user experience and can reduce bounce rates on multilingual sites by guiding visitors straight to the relevant language version.
Does it require consent?
The "locale" cookie is typically classified as preferences (functional), not strictly necessary. Under the ePrivacy Directive (transposed in Romania via Law 506/2004) and GDPR, preference cookies are generally not indispensable to the site's core technical operation and may require the visitor's prior consent, especially if combined with other purposes or set for a long duration.
- Site owners should verify exactly how the "locale" cookie is implemented on their platform (some CMSs only set it upon explicit language selection, which can affect classification).
- The cookie must be clearly listed in the cookie policy, with its purpose and duration.
- It's advisable to include it as a separate category in the consent banner, for transparency.
How to block or delete locale
A visitor can delete or block this cookie at any time from their browser settings (Chrome, Firefox, Edge, Safari), under the site data/cookie management section. Blocking it usually doesn't affect the site's core functionality — the visitor will simply need to reselect their language on each visit.
For site owners, a CMP like CookieFix can automatically block scripts that set the "locale" cookie until the visitor gives consent for the preferences category, ensuring compliance before any data is stored.
Frequently asked questions
No, it's usually not strictly necessary. The site can function without it — the visitor will just have to choose their language again on each visit.
It doesn't have a single provider — it's a generic name used by many CMSs, frameworks, and online stores to remember a visitor's language or region preference.
The typical duration is around 1 year, but it can vary depending on the platform setting it.
It normally stores only a language or region code, without information that directly identifies the person.