Cookie Policy

Effective date: 2026-06-09 Last updated: 2026-04-29

This Cookie Policy explains what cookies and similar technologies Versus ("we", "us") uses, why we use them, and what choices you have. It supplements the Privacy Policy.

Note for the operator (Francis): this policy is written assuming the only cookies in use today are authentication/session cookies set by Lovable Cloud / Supabase. Before launch, confirm with Lovable whether any analytics, A/B testing, or marketing cookies are in play. If they are, this document needs to list them by name, purpose, retention, and provider — and a real consent banner (not info-only) must be wired up. Search this document for TODO before launch.


A cookie is a small text file that a website stores in your browser. Cookies remember things across page loads — most usefully, that you're logged in. Similar technologies include local storage, session storage, and indexed databases in the browser, which we use the same way: to keep your session alive and to remember your preferences locally on your device.


2. What we use

2.1 Strictly necessary cookies (always on)

These are required for the Service to work. You cannot use Versus without them.

Name (pattern)Set byPurposeRetention
sb-*-auth-token and relatedLovable Cloud / SupabaseAuthentication and session management. Keeps you signed in across pages and tabs.Up to 30 days, refreshed on use
Stripe session and fraud-prevention cookies (only on the checkout page)StripeRequired by Stripe to process payments and prevent fraud during checkoutPer Stripe's policy

We also use browser local storage to remember:

  • Your provider keys (BYOK) when you have not opted in to server-stored keys.
  • UI preferences (e.g. collapsed Report Card, last-used roles).
  • The has_completed_onboarding flag.

Local storage is not technically a cookie but performs a similar role. It stays on your device until you clear it or sign out. Clearing your browser storage will sign you out and delete locally stored keys.

2.2 Analytics cookies

TODO before launch: confirm with Lovable / Supabase whether any analytics cookies are set. If a privacy-friendly tool (e.g. Plausible, Fathom) is enabled, list it here as informational with no consent gate. If a tool that requires consent (e.g. Google Analytics, Meta Pixel) is enabled, this section must list it explicitly and a consent banner with accept/reject options must be wired before any analytics scripts load.

As of the "Last updated" date above, we do not knowingly run third-party analytics. If that changes before or after launch, this section will be updated and we will notify users where required by law.

2.3 Advertising and tracking cookies

We do not run third-party advertising trackers. The Service is not ad-supported.


3. Your choices

You can:

  • Reject non-essential cookies when a banner offers you the choice (today, none are in use, so no banner is shown).
  • Block or delete cookies in your browser settings. Doing so for the strictly necessary cookies will sign you out and prevent you from using the Service.
  • Clear local storage in your browser to remove BYOK keys and UI preferences from your device.
  • Use private / incognito mode, which clears all of the above when the window closes.

We do not respond to "Do Not Track" browser signals at this time, because we don't run advertising or third-party trackers in the first place. If we ever do, we'll honor the signal where applicable law requires.


4. Changes

We may update this Cookie Policy when our use of cookies changes (for example, if we add an analytics tool). The "Last updated" date at the top will change. Material changes will be announced by email or in-app notice where required.


5. Contact

Questions about cookies:

Versus Quebec, Canada info@tryversus.app