Cookie notice

1. Overview

This notice describes cookies and similar technologies we use on OKtoMeet websites and the product. It should be read together with our Privacy Policy.

2. Essential cookies

We use cookies and local storage that are strictly necessary to operate the service (for example, session and security). These are not used for marketing attribution.

3. Google Tag Manager and Consent Mode

When we deploy Google Tag Manager (GTM), tags respect Consent Mode v2. functionality_storage and personalization_storage default to denied until you choose Functional & preferences in our banner or settings (we update both together). security_storage is granted for strictly necessary security. Other non-essential types default to denied until you choose. Our optional banner categories map as follows: Functional & preferences → functionality_storage and personalization_storage; Analytics & performance → analytics_storage; Marketing & referral → ad_storage, ad_user_data, ad_personalization. Configure GTM triggers to require the matching consent types. Set NEXT_PUBLIC_GTM_ID to enable the GTM container on the site.

Microsoft Clarity (session replay). When Clarity is enabled in our GTM container, it is configured to respect Consent Mode: session replay and related analytics do not run until you accept Analytics & performance in our cookie banner or Cookie settings (that choice updates analytics_storage to granted for your browser). After you grant that category, Clarity may record interactions such as clicks, scrolls, and page content you see during a session so we can diagnose usability issues. If you later turn analytics off or withdraw consent, new recordings do not start; how Microsoft retains or processes data after that is described in Microsoft's Clarity documentation.

When GTM loads. We do not inject the GTM script on your device until you have saved a choice in our cookie banner or Cookie settings and Analytics & performance or Marketing & referral is on (functional-only does not load GTM). That prevents first-party measurement tags in GTM from running at all until then. You should still configure each GTM tag with the correct consent types as a safeguard.

Third-party domains in your browser. Cookies scoped to google.com (for example SID, HSID, __Secure-1PSID) are usually tied to your Google account or Chrome profile, embedded Google widgets, or other Google sites—not something OKtoMeet sets from our own hostname. They are not proof that our analytics ran before consent. In development, __next_hmr_refresh_hash__ is from Next.js hot reload.

4. Referral attribution (member + ambassador)

We use referral attribution for both member waitlist invite links and ambassador / partner referral links. We may set cookies to attribute a subsequent signup on a first-click basis, generally for up to sixty (60) days. Our affiliate platform may set a provider cookie (for example, for tolt referral flows). We may also set a first-party cookie for okm_ref (or a session-scoped fallback such as okm_ref_pending where applicable).

In the EU, UK, and other jurisdictions that require prior consent for non-essential cookies, attribution cookies are treated as marketing / non-essential and are not set until you accept the marketing category in our cookie banner or via Cookie settings in the site footer. If you reject marketing cookies, signups may not be attributed to the member or ambassador that shared the link; we accept that loss of signal as the cost of compliance.

Where local law allows, we may set attribution cookies on landing with a clear notice and an opt-out control. If you later withdraw consent, we delete the cookie; signups after that are not attributed retroactively.

5. Cookie inventory (illustrative names)

6. Contact

Questions about cookies: use the channels in the product or write to [email protected].