Manage the Webstore cookie notice
The Webstore publishes a cookie notice listing every cookie it sets. This article explains why those cookies cannot be switched off, how guests reach the notice, and what you must do to keep it accurate. For the cookies themselves, see Zenoti Cookie Notice β Webstore.
Audience: Webstore administrators and compliance teams responsible for publishing the cookie notice and keeping it current.
On this page
- Before you begin
- How necessary cookies work
- Where the cookie list is published
- Access the cookie notice on the Webstore
- Keep the cookie notice current
- Tips
- Troubleshooting
- Related articles
Before you begin
- You must have admin access to the Zenoti admin portal to review or update Webstore configuration.
- Familiarize yourself with your organization's privacy and cookie compliance obligations before publishing or modifying the cookie notice.
- No special Zenoti permission is required to read the cookie notice as a guest β it is publicly accessible from the Webstore footer.
Note: Necessary cookies cannot be disabled by guests or suppressed by cookie consent preferences or Global Privacy Control (GPC) signals. They are required for the Webstore to function. Non-essential cookie suppression is governed separately β see Global Privacy Control (GPC).
How necessary cookies work
The Webstore sets a defined set of necessary cookies every time a guest visits. These cookies are classified as non-optional: without them, core Webstore functionality β including session continuity, booking context, and returning-visitor recognition β does not work as intended.
Because necessary cookies are strictly required for the service to operate, they are not subject to cookie consent preferences. Guests cannot opt out of necessary cookies, and GPC signals do not suppress them.
The cookie notice documents every cookie the Webstore sets, including the issuing party, the cookie name, how long the cookie persists, and a plain-language description of its purpose. The notice is accessible from the Webstore at all times and must be kept current whenever cookies are added, removed, or modified.
Where the cookie list is published
Every cookie the Webstore sets β Zenoti cookies, third-party infrastructure and security cookies, local storage items, and analytics and marketing cookies β is listed in the published cookie notice, together with its issuing party, name, expiry, and purpose.
Read: Zenoti Cookie Notice β Webstore
That notice is the single source for cookie details. This article covers the process around it: how guests reach it, and how to keep it current.
Important: Necessary cookies are set automatically when a guest visits the Webstore and cannot be suppressed by the guest or by consent management tools. Third-party infrastructure and security cookies cannot be suppressed either, without degrading session stability or security protection.
Note: Session-duration cookies are deleted when the guest closes their browser. Longer-lived cookies persist for the expiry shown against each entry in the cookie notice.
Access the cookie notice on the Webstore
Guests can access the cookie notice directly from the Webstore without signing in.
- Open the Webstore in a browser.
- Scroll to the footer of any Webstore page.
- Select the cookie notice link in the footer.
The cookie notice opens and lists every cookie set by the Webstore β see Zenoti Cookie Notice β Webstore.
Tip: If you cannot locate the cookie notice link in the footer, verify that the footer link is configured in your Webstore template. See Template and Branding Settings for footer configuration guidance.
Keep the cookie notice current
The cookie notice must be updated whenever the Webstore introduces new cookies or modifies existing ones β including changes to cookie names, durations, issuing parties, or purposes. This includes changes introduced by updates to the CDN, load balancer, or consent management platform.
Important: When new third-party infrastructure or consent management cookies are introduced β for example, by changes to the CDN, load balancer, or consent platform β the cookie notice must be updated to include the new cookie name, issuing party, duration, and plain-language purpose description before the change is deployed to production.
Review the notice after Webstore updates
- After any Webstore release or configuration change that may affect cookies, open the Webstore and navigate to the cookie notice via the footer link.
- Compare the published notice against the cookie tables in Zenoti Cookie Notice β Webstore.
- If the notice is out of date, update it through your organization's content management process or contact your Zenoti account team for assistance.
Add new cookies to the notice
If your organization adds tracking or analytics integrations that set additional cookies (for example, a Facebook Pixel or GA4 measurement tag), those cookies must also be documented in the cookie notice before the integration is enabled.
- Identify the new cookie name, issuing party, duration, and purpose from the integration's documentation.
- Add the cookie details to the cookie notice before enabling the integration on the Webstore.
- Classify the new cookie correctly β necessary cookies cannot be suppressed; non-essential cookies must be subject to consent controls.
Important: Non-essential cookies (such as analytics or advertising cookies) must be suppressible by guest consent preferences and, where applicable, by GPC signals. Do not classify non-essential cookies as necessary. See Global Privacy Control (GPC) and Compliance and Consent for guidance on non-essential cookie handling.
Worked example: Your organization enables the GA4 integration. GA4 sets its own cookies (for example,
_gaand_ga_<ID>) issued by Google, with a two-year duration, for analytics purposes. Before enabling GA4 on the Webstore, add these cookies to the cookie notice with the issuing party listed as "Google", the correct duration, and a plain-language description such as "Used to distinguish users and sessions for analytics reporting." Then classify them as non-essential and ensure they are subject to consent controls.
Tips
- Review the cookie notice after every Webstore release. Zenoti may update the cookies the Webstore sets as part of product updates. Treat each release as a trigger to verify the notice is still accurate.
- Review the notice before deploying infrastructure changes. Changes to your CDN, load balancer, or consent management platform may introduce new cookies. Update the cookie notice before the change goes live, not after.
- Keep cookie descriptions plain and specific. Guests reading the notice are not technical users. Describe each cookie's purpose in terms of what it does for the guest experience, not how it works internally. For example, "maintains your active session so your booking is not lost" is clearer than "stores session state on the server."
- Coordinate with your legal or compliance team. Cookie notice requirements vary by jurisdiction. Your legal team should review the notice for completeness and language before it is published, and again whenever it is updated.
- Test the footer link after template changes. If you update the Webstore template or footer configuration, verify that the cookie notice link still appears and resolves correctly. Changes to the template may take up to 30 minutes to propagate due to cache invalidation.
- Document the date of each notice update. Maintaining a record of when the cookie notice was last reviewed and updated supports compliance audits and demonstrates due diligence.
Troubleshooting
The cookie notice link does not appear in the Webstore footer.
Verify that the footer link to the cookie notice is configured in your Webstore template settings at Configuration > Online booking > Online booking settings > Webstore V2. If the link is missing from the template configuration, add it. Changes may take up to 30 minutes to appear on the live Webstore.
A guest reports that a cookie listed in the notice does not match what their browser shows.
Open your browser's developer tools and inspect the cookies set by the Webstore domain. Compare the names, durations, and issuing parties against the tables in Zenoti Cookie Notice β Webstore. If there is a discrepancy, the notice may be out of date β update it to reflect the current cookie set. If you see cookies that are not listed in the notice, they may have been introduced by a third-party integration (such as analytics or advertising tags) and must be added to it.
A guest asks why they cannot opt out of the Webstore cookies.
The cookies listed as necessary in Zenoti Cookie Notice β Webstore, including the third-party infrastructure and security cookies, are necessary for the Webstore to function. They are not subject to consent preferences or GPC signals. Explain to the guest that these cookies are strictly required for session management, server routing, security protection, and returning-visitor recognition, and that the Webstore cannot operate without them. If the guest has concerns about non-essential cookies, refer them to the consent controls available on the Webstore and to your organization's privacy notice.
The cookie notice content appears outdated after a Webstore update.
Zenoti Webstore updates may change the cookies the system sets. After any update, review the published cookie notice against the current necessary cookies list and update the notice if needed. If you are unsure whether a recent update changed the cookie set, contact your Zenoti account team for confirmation before updating the notice.
The OneTrust consent banner reappears for guests who have already made their cookie choices.
The OptanonConsent cookie stores the guest's consent preferences for one year. If the banner is reappearing, verify that the OptanonConsent cookie is being set correctly after the guest interacts with the banner. Common causes include browser settings that block third-party cookies, private browsing mode, or a cookie policy change that requires guests to re-consent. Check your OneTrust configuration and consult OneTrust documentation for further guidance.