Policy version: 2026-10-15. This page explains the cookies and similar technologies identified in the current Sphereo build and how to change your choice.
Necessary technologies
Sphereo uses the Supabase Auth session cookie, named by the Supabase project as sb-<project-ref>-auth-token and, when needed, its numbered chunks. It keeps your account session available across requests. The session cookie is first-party, uses the default Supabase SSR settings and is necessary for sign-in, account security and authenticated features.
The sphereo_consent cookie stores your cookie choice, the policy version and the time of the decision. It is necessary so Sphereo can remember your choice for 12 months. Necessary technologies remain active when optional analytics is rejected.
Referral programme (pending legal validation)
When you visit a Sphereo referral link, Sphereo may set sphereo_referral_code for 30 days and sphereo_device_id for up to 365 days. They support referral attribution, fraud prevention and the points awarded by the existing referral programme. They are currently classified as Necessary for that feature, pending legal validation.
The current referral implementation writes sphereo_device_id from one API response without explicitly declaring Path=/. This technical detail is being reviewed and is not changed by this cookie work.
Functional storage
The audio player uses the first-party browser-storage keys sphereo:audio-position:<src> to remember playback position when you pause or leave a page. The current implementation uses localStorage (not a cookie or sessionStorage). This is Functional storage; it has no explicit expiry and is removed when the track finishes.
Payment and fraud prevention
Stripe.js is loaded when a payment form is used. Stripe may use cookies or similar technologies for payment processing and fraud prevention. These are third-party technologies subject to Stripe's own policy. Their exact browser behaviour is pending verification in a browser.
Optional analytics
When analytics is accepted, Sphereo uses the first-party sphereo_vid visitor identifier for up to 12 months and sphereo_sid in sessionStorage; the session identifier rotates after 30 minutes of inactivity. The Vercel Web Analytics script is loaded only after analytics consent and only when Web Analytics is enabled for the Vercel deployment. These details remain pending legal validation.
Change your choice
Use Cookie preferences in the footer to reopen the settings dialog and save a new choice. You can also use your browser controls to delete cookies or local storage. Deleting necessary technologies can prevent account and checkout features from working.
Technical review
This page is based on a source-code review. Browser verification of Stripe.js and the final legal classification of referral technologies are still pending. The policy will be updated if the implementation or the required legal information changes.