Cookie Policy
Last updated: 1 September 2026
2. Types of Cookies/SDKs We Use
Below is a plain‑English list. For each type we explain examples, why we set them and how long they typically live. Durations are maximums; many cookies expire sooner.
Strictly necessary
- What: authentication and session tokens, security data, checkout state and your consent record
- Why: log you in, keep you logged in, route traffic reliably, protect against attacks and complete purchases
- Examples:
authToken, checkout session state andCookieConsent - Lifespan: session to 180 days; authentication duration depends on the account session
Preferences
- What: settings you request, including theme, football/betting mode and odds format
- Why: remember your choices so you don’t have to reset every visit
- Examples: Ressq theme, mode and odds-format storage
- Lifespan: up to 12 months or until you clear it
Analytics & performance
- What: page views, product events, session IDs, performance information and, with permission, session diagnostics
- Why: understand usage, debug problems, improve features
- Examples: PostHog cookieless measurement; with analytics permission, PostHog (
ph_*) and Google Analytics - Lifespan: PostHog's cookieless identifier rotates daily; optional provider storage normally lasts up to 13 months
- Cookieless details: after you choose Necessary only, PostHog briefly uses the request's network address, browser user agent and site domain with a rotating salt to create a pseudonymous measurement identifier. The raw hash inputs are removed before the event is stored. No PostHog cookie or browser storage is used, and session replay and surveys stay off.
Marketing & attribution
- What: ad-click identifiers, campaign parameters, affiliate referral data and advertising conversion events
- Why: attribute trials and subscriptions, measure Meta campaign performance and credit affiliate referrals
- Examples: Meta Pixel (
_fbpand_fbc), Rewardful, UTM storage and Ressq affiliate storage - Lifespan: campaign attribution is kept for up to 30 days; provider identifiers vary and are removed where possible when you withdraw permission
3. Consent & How To Change Your Choice
We ask before setting optional analytics or marketing cookies and before loading the other optional providers. You can accept all, use Necessary only, or select categories individually. Update or withdraw your choice any time via .
Choosing Necessary only does not prevent sign-in, subscriptions or core football features from working. It permits basic cookieless PostHog measurement but not PostHog browser storage, cross-day recognition, session replay or surveys.
4. Managing Cookies In Your Browser
You can also block or delete cookies in your browser settings. Here are guides for popular browsers (links open in a new tab):
Disabling essential cookies may break core functionality (login, checkout, etc.).
5. Providers
Web providers are controlled by the Ressq cookie preferences as follows:
- PostHog: basic cookieless product and audience measurement after an explicit Necessary only choice; full persisted analytics only with analytics permission
- Google Analytics/Google Tag Manager: optional product and performance analytics, loaded only with analytics permission
- Meta Pixel and Meta Conversions API: advertising measurement. Server conversion events are sent only when marketing consent was recorded with the checkout
- Rewardful and Ressq affiliate attribution: referral measurement
6. Updates To This Policy
We’ll update this page if our cookie/SDK usage changes. Check the “Last updated” date at the top. For material changes, we’ll notify you (e.g. via banner).
7. Contact
Questions about cookies? Email contact@getressq.com.
