REPPED.

Cookies Policy

Last updated July 4, 2026

REPPED uses a small number of cookies: some are strictly necessary to keep the Service working (like staying signed in), some come from Google AdSense to show and measure advertising, and one set comes from Google Analytics, which is how anyone here knows whether the site gets visitors at all. That is the complete list — there is no other tracking.

Analytics and advertising both run under Google Consent Mode, and until you accept they are set to denied: the visit is still counted, but cookielessly, with nothing written to your device and no identifier kept. Accepting is what creates the _ga cookies in the table below.

CookieProviderPurposeDuration
sb-access-token / sb-refresh-tokenSupabase (first-party)Keeps you signed in between visitsSession / up to 1 year
__Secure-3PSID and relatedGoogle AdSenseAd personalization and frequency cappingUp to 2 years
IDE / DSIDGoogle DoubleClickMeasures ad performance and shows relevant ads based on your browsingUp to 13 months
_ga / _ga_<id>Google Analytics 4Counts visits and tells apart one visitor from another. Only written if you accept — see belowUp to 2 years

Necessary vs. advertising cookies

The Supabase session cookie is strictly necessary — without it, you'd be signed out on every page load. It cannot be disabled while staying signed in, though you can always play as a guest with no cookies tied to an account at all.

Google's advertising cookies are not required for the Service to work. You can opt out of personalized ads (REPPED will still show ads, just not tailored to your browsing) at Google Ads Settings or aboutads.info/choices.

Managing cookies in your browser

Most browsers let you block or delete cookies in their settings. Blocking all cookies will sign you out of REPPED and may prevent ads from loading, but guest gameplay is unaffected since guest data lives in localStorage, not cookies.

More information

See our Privacy Policy for how we handle personal data more broadly, or contact privacy@repped.fun.