Cookie Policy
Effective 8 October 2026 · Version 2026-10-08.7
You can apply for beta access with optional analytics and referral attribution switched off. We use first-party preferences and referral cookies. Google Analytics 4 and Microsoft Clarity session recordings start only with analytics consent and their configured project IDs. We deny advertising storage; Microsoft controls its own cookie implementation.
1. What are cookies?
Cookies are small text files stored by your browser when you use a website. They can remember a choice or recognize a visit. Similar storage, such as localStorage, can also remember information on your device. This policy covers both.
2. Why does Clargus use cookies?
Essential preferences remember your privacy choices and selected website appearance. Optional analytics uses first-party event records, Google Analytics 4 and Microsoft Clarity recordings/heatmaps when configured to understand website use. Optional referral attribution helps us identify which publisher and platform brought an applicant to Clargus. Optional categories remain off unless you enable them. We do not enable advertising or targeting in our integrations and send Clarity an advertising-storage denial. Microsoft documents some vendor cookies with broader purposes; actual behavior depends on its service and browser settings.
3. Your choices
The banner offers equally accessible Accept All Cookies and Reject All buttons. Reject All keeps essential preferences on and optional cookies off. Cookie Settings lets you choose analytics and referral attribution separately. Both optional choices start off. Closing the initial notice leaves them off; closing settings without saving keeps your existing choice. Use Cookie settings in the footer to change your choices at any time. Continuing to browse or agreeing to the Terms does not enable optional tracking.
4. Necessary preferences
clargus_consent remembers the cookie choices, policy version, decision time, and a random reference to the consent record. It lasts up to 180 days and is used to respect your choices and record them in Supabase. It contains no application details.
The theme setting in localStorage remembers a light or dark appearance selected by you. It is not used for analytics or referral tracking. The publisher administration page keeps a signed-in administrator’s access token in memory only. It does not create a persistent public login cookie.
5. Optional analytics
If accepted, clargus_analytics_session stores a random session identifier for up to 30 minutes. We record page paths, form audience, and events such as page views, form starts, and successful submissions in Supabase. First-party events do not capture what you type or form contents. Optional Clarity session recordings are separate and use masked form blocks. Events are recorded only while the current analytics choice allows them.
6. Google Analytics
When configured and you allow analytics, we load the Google tag and send page and form events to Google Analytics 4. The tag is blocked until analytics consent. We configure its analytics cookies for up to 180 days with automatic renewal off. Browser restrictions may shorten that period.
We disable Google signals and advertising personalization. We do not intentionally send names, emails, entered form contents, full query strings, or URL fragments into Google Analytics. Google receives connection and browser/device information when its tag runs. You can withdraw analytics consent using Cookie settings; we stop our analytics events and delete this website’s Google analytics cookies.
Google Analytics retention is managed separately in the Google property and is not controlled by our Supabase cleanup job. User/event retention settings do not govern all aggregated reports. Google’s data practices are described at https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites.
7. Microsoft Clarity
When configured and you consent to analytics, Clarity provides session recordings and heatmaps. Its _clck and _clsk cookies are first-party; Microsoft also documents CLID, MUID, SM, MR and ANONCHK cookies on its domains. Our cookie table does not invent expiry times for this provider-controlled behavior. See https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-cookies.
The SDK is not loaded before optional analytics consent. Typed form fields are masked, and private pages or sensitive URLs are excluded. Recordings carry the same random first-party visitor and session identifiers as our analytics so an administrator can match a recording to a submitted application. Clarity may process eligible page URLs with approved campaign/referral parameters; the query-stripping safeguards for first-party/manual Google events are not a blanket promise about Clarity.
We grant analytics storage only and deny advertising storage. Withdrawal denies storage and stops collection, rather than relying on a vendor cookieless tracking mode. It removes accessible first-party Clarity cookies; it cannot erase Microsoft-domain cookies or already collected recordings. Microsoft controls retention separately.
8. Optional referral attribution
If accepted, clargus_referral remembers the most recent valid publisher link you opened for up to 30 days. Each link maps to a publisher platform account, such as X, LinkedIn, TikTok, Instagram, Facebook, or another listed channel. One creator can have different links for different platforms. Clargus-owned accounts are marked separately.
We use last-link attribution: a newer valid referral replaces an earlier one during the attribution window. A current consented referral can be linked to your beta application. Declining attribution means we do not persist a referral cookie or attach a referral to your application. Link parameters may remain visible in the address bar and hosting logs, but are not treated as permission to track you.
9. Records and withdrawal
We record accept, decline, customize, and withdrawal choices with their version and timestamps in Supabase. A submission stores a separate record of agreement to the Terms and acknowledgement of the Privacy Policy. Optional consent is never bundled into that acknowledgement.
Changing to necessary only removes optional cookies and stops future optional events and attribution. Earlier records remain subject to the Privacy Policy’s retention schedule and applicable rights. Browser controls can also clear cookies, but clearing them alone does not send us a withdrawal instruction; use Cookie settings to record a change.
10. Third-party sites and questions
Social media sites and links outside Clargus have their own cookies and policies. We do not control them. Contact [email protected] with questions about our cookies.