Encounter Cookie Notice
Version: 1.1
Effective date: 11 September 2026
1. About this notice
This notice explains how EONE Global Ltd, trading as Encounter or EONE Encounter, uses cookies and similar storage technologies in the Encounter web service.
For questions, contact info@eoneculture.com.
2. What cookies are
Cookies are small pieces of information stored by a website in your browser. They can help a service recognise a signed-in session, remember a request and protect against misuse.
3. Cookies used by Encounter
The current production service is intended to use only cookies needed for authentication, session refresh, security and preferences you request.
| Cookie or category | Provider | Purpose | Duration |
|---|---|---|---|
| Supabase authentication cookie, including chunked variants where required | Supabase / Encounter | Stores and refreshes the tokens required to keep you signed in and authenticate requests | The browser cookie may be stored for up to 400 days after its last refresh. The authentication session currently has no fixed maximum lifetime or inactivity timeout and continues until sign-out or another provider-side termination event |
encounter_guest_session | Encounter | Holds an opaque key that lets this browser resume a guest profile; answers remain on the server and only a hash of the key is stored there | 30 days from guest-profile creation; use does not extend it |
encounter_guest_link | Encounter | Carries a one-time guest-link intent while you choose which profile to keep | Up to one hour |
encounter_privacy_notice_seen | Encounter | Remembers that this browser dismissed the current Privacy Notice update notification; the value contains only the notice version | 365 days |
| Short-lived authentication flow storage, if present in the final deployment | Supabase / Encounter | Completes and protects the one-time magic-link authentication flow | Not used by Encounter's current magic-link flow; no separate authentication-flow cookie or local-storage value is intentionally created. |
Encounter also has a development-only prototype-session cookie. It is disabled outside local development and is not part of the production service.
The global sign-in form also uses Cloudflare Turnstile for bot protection. Turnstile is configured without pre-clearance and does not require a Cloudflare clearance cookie. It processes short-lived security signals when the form is used.
4. Why there is no cookie banner in the current version
Consent is generally not required for storage that is strictly necessary to provide a service the user requested, such as authentication and essential session security. The notice-dismissal cookie is set only after you choose Dismiss and remembers that preference so the notice is not repeatedly shown. It is not used to identify you, track activity or measure engagement. We still provide this notice so that users understand the storage involved.
The current production design does not include advertising cookies, cross-service tracking or optional analytics cookies.
If we introduce any non-essential storage, we will update this notice and ask for consent before setting it. Rejecting non-essential storage will be as easy as accepting it.
5. Managing cookies
You can block or delete cookies using your browser settings. Blocking strictly necessary authentication cookies will prevent sign-in or cause signed-in features to stop working.
Signing out asks the authentication provider to end the relevant session and remove its browser session information. Clearing browser cookies does not by itself guarantee that a provider-side session has been revoked.
Deleting the guest-session cookie makes that guest profile inaccessible from the browser immediately. The cookie expires 30 days after guest-profile creation and is not refreshed through use. Unless you use the explicit Clear action, the inaccessible server-side guest data is retained until scheduled cleanup after 90 days from guest-profile creation.
6. Changes and contact
We may update this notice when the service or its storage technologies change. The latest version and effective date will be published here.
Contact: info@eoneculture.com