LuckyDate
LuckyDate
Home

Cookie Policy

Last updated: May 16, 2026

We use a small number of cookies. None of them are advertising cookies unless you explicitly accept the analytics banner on your first visit. Here's every cookie we set, in plain English.

Strictly-necessary

These cookies are required for the site to work. We don't ask for consent because the site is unusable without them.

  • luckydate_session — an HTTP-only, SameSite=Lax JWT that keeps you signed in for 30 days. Set when you log in, cleared when you log out or delete your account.
  • luckydate_cookie_consent — stores whether you accepted or declined the analytics banner so we don't ask again. Set when you click a banner button.
  • g_state (Google) — one-shot CSRF token used during Google sign-in. Cleared automatically after the handshake completes.

Analytics (optional)

These only load if you accept the cookie banner. You can change your mind at any time by clearing the luckydate_cookie_consent cookie and reloading.

  • PostHog — product analytics. We use it to understand which features get used and where users get stuck. Sets cookies named ph_*.
  • Meta Pixel (when enabled) — lets us measure ad performance on Facebook and Instagram. Sets cookies named _fbp and _fbc.

Local storage

We also use browser local storage (which is similar to a cookie but stays on your device only) for a handful of preferences: notification-sound on/off, your selected language, the cookie consent state mirror, and a few small UI flags. These never leave your device.

Changing your mind

You can withdraw analytics consent at any time. The easiest way is to clear cookies for luckydate.org in your browser settings — on the next page load the banner reappears and you can choose again. For broader data rights see our Privacy Policy.

Contact

Cookie questions? Reach us at info@luckydate.org.