Cookies and Device Storage

1. Cookies and similar technologies

Cookies are values saved by a browser and returned with relevant requests. Local storage, session storage, IndexedDB, service-worker caches, embedded content, and native-app storage can also retain or access information. A technology’s name does not decide whether it requires consent; its purpose, necessity, and the law applicable to the device matter.

This notice covers technologies used by Zene and relevant third-party integrations. A cache on Zene’s server is different from information written to a user’s device. Clearing one does not necessarily remove the other.

2. Zene session cookies

The website sets zene.access for authenticated access with a configured maximum age of one hour. The zene.refresh and zene.device cookies have a configured maximum age of forty-five days. These values support session renewal and device/session continuity. Cookies can be renewed during use, so a configured lifetime is not a promise that a record is erased on a fixed calendar date.

These cookies are configured as HttpOnly and SameSite=Lax, and Secure outside development. The obsolete zene.session cookie is removed by current session-management flows. Signing out clears Zene’s session cookies; blocking them can prevent sign-in and protected features from working. Browser controls remain available even for cookies needed for those features.

3. Browser and application storage

The website uses storage for language preference, sign-in email-link continuity, cached IP-based location, playback preferences and queue state, seen-story state, and feature caches. Session storage commonly lasts for a tab session; local storage generally remains until application cleanup, browser eviction, or manual deletion. These stores do not all share a verified twelve-month expiry.

Applications use local preferences, media or image caches, and account-related state as needed by implemented features. Use the cache controls available in the installed version, operating-system storage controls, or browser site-data settings. Removing device data can sign you out or remove local preferences and does not submit an account-erasure request.

4. Zene Stores referrals and visit counts

When you open a poster from someone’s Zene store, the website saves a first-party cookie named zene_ref for ten days. It lists, for each poster opened that way, the store it came from and when, so that the store can be credited if you buy that poster. It holds no personal information, is sent with your checkout, and is replaced when you open the same poster from another store. Deleting it means no store is credited for a later purchase; it does not affect what you pay.

Store pages also keep two items in local storage: zene.visitor, an anonymous random identifier, and zene.store-seen, the stores this browser has opened today. They are used only to count visits without counting a reload twice, and you can remove them by clearing site data.

• Zene Stores Terms

5. Advertising, measurement, and embedded content

Google advertising scripts, the Google Ads tag, the Meta Pixel, Firebase analytics, Microsoft Clarity, and configured error-reporting services can send requests from the web experience. The Meta Pixel may set cookies such as _fbp and _fbc, and the Google Ads tag cookies such as _gcl_au, to connect a visit and a purchase to the ad that led to it. Microsoft Clarity may set first-party and third-party cookies, such as _clck and _clsk, to recognise a returning browser and group its visits into sessions. YouTube players, externally served images or streams, maps, and authentication services may also access storage or receive technical data. The applicable providers determine additional cookie names and lifetimes, which can vary with configuration and region.

An advertising-recovery script is not evidence of a complete consent-management system. Loading a script asynchronously is not consent gating. This notice does not assert that non-essential technologies wait for consent or that a reject/customise banner and persistent preference centre are implemented when that has not been verified.

• Google’s use of cookies
• Google Privacy Policy

6. Controls and their limits

Use privacy choices displayed in the service or by its providers, browser controls for individual sites, and operating-system permissions for notifications and advertising identifiers. Withdrawing optional consent should be as accessible as granting it where consent is the basis. Essential account features must not be described as optional advertising merely to obtain an all-or-nothing agreement.

Global Privacy Control and other legally recognised opt-out signals require implementation and testing against the relevant advertising disclosures. This page does not claim an automatic signal handler is currently verified. An email to [email protected] can request assistance, but sending it does not automatically update a browser preference or block a provider request.

Final release requires a current storage inventory and verified controls for each applicable region. No single notice, purchase, or browser setting guarantees that every third-party service has deleted historical information.

• Advertising Privacy Choices
• Privacy Policy