What is the timezone cookie?
"timezone" is a generic cookie name used by many web platforms, themes, and plugins (booking systems, calendars, scheduling tools, forms, analytics tools, or CMS platforms) to remember a visitor's time zone. There is no single provider behind it: the name is used independently by different developers, which is why it is classified generically as "Various".
The cookie is typically set as soon as a visitor lands on the site or interacts with a time-dependent feature, such as a booking calendar, an appointment widget, or content that displays publication times.
What data it stores
The cookie usually stores a text value indicating the visitor's detected browser time zone (for example, a region/city identifier or an offset from UTC). The exact value format varies between providers, since there is no single standard for this cookie.
The data is read by the script that set it, directly in the visitor's browser, to adjust how times are displayed on the page. In general, it does not involve sending data to additional third-party servers beyond the domain that set the cookie.
What it is used for
Its main purpose is functional: the site uses the stored time zone to correctly display availability times, deadlines, publication dates, or scheduling slots, without repeatedly asking the visitor to set their time zone manually.
For site owners, this results in a more consistent experience for visitors located in different time zones than the server or business, reducing confusion caused by incorrectly displayed times.
Does it require consent?
In CookieFix's classification, "timezone" falls under the preferences (functional) category. Under the ePrivacy Directive (2002/58/EC, transposed in Romania via Law 506/2004) and the GDPR, preference cookies are not strictly necessary for a website's core functionality, so they generally require the visitor's prior consent before being set.
- Site owners should verify whether the script setting this cookie is genuinely essential (e.g., to complete a booking) or merely enhances the experience — this determines the correct category.
- The cookie must be clearly listed in the site's cookie policy, including its purpose, duration, and provider (if identifiable).
- If classified as a preference cookie, the related script must be blocked until consent is obtained.
How to block or delete timezone
A visitor can delete or block this cookie from their browser settings (Chrome, Firefox, Safari, Edge), under the cookies and site data management section, by searching for "timezone" or the domain of the visited site.
For site owners, the most practical approach is using a consent management platform (CMP) like CookieFix, which automatically blocks preference-category scripts — including those setting "timezone" cookies — until the visitor gives consent, helping meet GDPR and ePrivacy requirements.
Frequently asked questions
No, it is a low-risk functional cookie that only stores the detected time zone, not sensitive personal data. Technically, though, it could be combined with other signals to approximate a visitor's location.
Because the name "timezone" is used generically by many different scripts and platforms (calendars, booking systems, CMS platforms), without a single standard or recognized provider behind it.
Generally yes, if it is classified as a preference/functional cookie and is not strictly necessary to deliver a service explicitly requested by the user. Check its exact purpose before deciding the category.
The typical observed duration is 1 year, but it can vary depending on the script or platform that sets it.