What is the umami.disabled cookie?
umami.disabled is a value stored in localStorage by the open-source Umami analytics script when a website gives visitors an explicit option to disable tracking (for example, via a “Do not track me” button or an opt-out link displayed on the page).
This entry only appears if the site administrator has implemented this opt-out feature within Umami’s interface or through a custom script that sets this flag. It is not created automatically just by loading the analytics script.
What data it stores
umami.disabled stores a simple boolean value (usually “true”) indicating that Umami tracking should be ignored for that visitor, in that browser. It does not contain unique identifiers, IP addresses, or other personal data.
Unlike HTTP cookies, this value stays exclusively in the visitor’s browser (localStorage) and is not automatically sent to the server with each request; it is read directly by the Umami script in the browser to decide whether to send analytics events.
What it is used for
The purpose of this entry is purely functional: it allows the site to honor the visitor’s choice not to be tracked, without showing the opt-out option again on every visit. In practice, it remembers a privacy preference expressed by the user.
For the site administrator, having this mechanism demonstrates good practice regarding transparency and control given to visitors, complementing the consent required for other analytics cookies.
Does it require consent?
CookieFix classifies umami.disabled under preferences (functional). Although its purpose is to block tracking rather than enable it, it still needs to be listed in the cookie policy, since it involves storing data on the user’s device, as required under the ePrivacy rules implemented via Romania’s Law 506/2004.
- If the opt-out feature is offered independently, without the main Umami tracking script already running, storing this preference can generally be treated as strictly necessary to the opt-out mechanism itself.
- If it is part of an analytics setup that otherwise requires consent (statistics category), the administrator must ensure the Umami script as a whole only starts after the visitor’s consent.
- Recommendation: explicitly list this cookie/localStorage entry in your cookie policy, along with its purpose and duration.
How to block or delete umami.disabled
A visitor can manually clear this localStorage value from browser settings (Settings → Privacy → Site Data → clear data for that domain) or by using private/incognito browsing mode.
For site administrators, a CMP like CookieFix can automatically block the Umami script and any related mechanisms from running until the visitor gives consent, ensuring the correct order: user choice first, script activation second.
Frequently asked questions
It’s a localStorage entry used by the Umami analytics script to remember that a visitor has chosen to opt out of tracking.
No, it is stored in localStorage rather than as a classic HTTP cookie, but it is treated similarly under the ePrivacy Directive and should be listed in the cookie policy.
It is persistent, meaning it stays saved in the browser until the visitor manually deletes it or clears the site’s data.
It can generally be treated as strictly necessary to the opt-out mechanism, but administrators should review their specific setup and list it in the cookie policy regardless.