A short list, because we only use the cookies ScoreDate actually needs.
Last updated November 8, 2026
On this page
Draft for review. This text is being finalized with counsel before launch.
The cookies we use
These are first-party cookies set by scoredate.app. On our public website we also use advertising cookies from Meta and Google (listed below), unless you opt out at Your Privacy Choices. None of them run inside the ScoreDate app.
Sign-in (Supabase auth): keeps you signed in. Essential.
score_theme: remembers light, dark or system theme. Up to 1 year.
score_vid / score_sid: a random visitor ID (1 year) and session ID (30 minutes) so we can count visits and see which pages help. They’re not linked to your name unless you sign in.
score_seen: limits how often we update your “last active” time. 1 hour.
score_ref: remembers a friend’s invite link so they get credit if you join. 30 days.
score_invite: holds an invite code while you sign up. Until you finish.
score_attr: remembers which campaign link first brought you here, so we know which ads work. 90 days.
score_ads: remembers if you opted out of ad measurement. 2 years.
Meta (_fbp, _fbc) and Google (_gcl_au and similar): advertising cookies on our public website only, used to measure our ads. Up to 90 days. Not set if you opt out or send Global Privacy Control.
Other browser storage
If you turn on notifications, your browser stores a push subscription and a small service worker so notifications can arrive. We also remember if you dismissed the notifications prompt. Turning notifications off in Settings removes the subscription.
Your control
You can block or delete cookies in your browser settings. Blocking sign-in cookies will sign you out; blocking the others only resets your theme and counts you as a new visitor.