Cookie policy

Effective Date: 01 January 2026; Last Updated: 20 May 2026

1. What This Covers

This policy explains what cookies are, which ones Rafflery uses and why, and how you can control them. For the broader picture on personal data, see our Privacy Policy.

2. What Cookies Actually Are

Cookies are small files stored on your device when you visit a website. They let the site remember things — your session, your preferences, whether you’ve visited before. Similar technologies like web beacons, pixels, and local storage work in comparable ways and are covered by this policy too.

3. The Cookies We Use

Strictly Necessary

These can’t be switched off. The platform doesn’t work without them — logging in, maintaining your session, submitting entries, staying protected against request forgery. If you block these, expect things to break.

Cookie	What it does	Duration
`session_token`	Keeps you logged in	Session
`csrf_token`	Protects against cross-site request forgery	Session
`cookie_consent`	Remembers your cookie choices	12 months
`entrant_session`	Maintains entry session for participants	Session

Functional

These remember preferences and settings. Disabling them won’t break the platform, but some things will reset between visits.

Cookie	What it does	Duration
`locale_pref`	Saves your language/region	12 months
`dashboard_state`	Remembers dashboard layout	30 days
`last_campaign`	Tracks which campaign you last worked on	7 days

Analytics

We use Google Analytics to understand how the platform gets used — which features see the most traffic, where people run into problems, how campaigns perform across different contexts. The data is aggregate and pseudonymised. We’re not trying to identify individual users through analytics.

Cookie	Provider	What it does	Duration
`_ga`, `_ga_*`	Google Analytics	Aggregate behaviour tracking	24 months
`_gid`	Google Analytics	Session differentiation	24 hours
`_gat`	Google Analytics	Request throttling	1 minute

Marketing and Retargeting

These are off by default. They’re only activated if you (as an organiser) have explicitly enabled them for your account, or if a participant has consented through the campaign’s consent mechanism. They’re used for ad performance tracking and retargeting.

Cookie / Pixel	Provider	What it does	Duration
`_fbp`	Meta Pixel	Campaign performance tracking and retargeting	90 days
`_fbc`	Meta	Click attribution from Facebook ads	90 days
`_gtm`	Google Tag Manager	Tag management and firing	Varies

4. Third-Party Cookies

Some cookies on Rafflery pages aren’t set by us. When entry uses Facebook Login, Meta may set cookies under Meta’s own policy. Our billing provider sets session cookies during checkout. Any embedded content from external providers may also bring their own cookies with it.

Rafflery doesn’t control those. Each provider’s own policy governs them.

5. Controlling Cookies

When you first visit Rafflery.io, a consent banner gives you the choice: accept all, reject non-essential, or customise by category. Your selection is stored for 12 months. You can change it any time using the “Cookie Settings” link in the footer.

You can also manage cookies directly in your browser. Most browsers let you view, block, or delete cookies. The setting locations vary:

Chrome: chrome://settings/cookies
Firefox: about:preferences#privacy
Safari: Preferences > Privacy
Edge: Settings > Cookies and site permissions

Just be aware that blocking strictly necessary cookies will break core platform functionality.

For analytics and ad cookies specifically, opt-out tools are available separately:

Google Analytics: https://tools.google.com/dlpage/gaoptout
Meta Ad Preferences: https://www.facebook.com/ads/preferences

6. What Happens on Campaign Pages

When a participant enters a campaign through a Rafflery landing page or embedded widget, we set only the minimum cookies needed to process the entry — strictly necessary and functional, as described above.

Analytics and marketing cookies on campaign pages are controlled by the Campaign Organiser, not by Rafflery. If a campaign uses the Meta Pixel or Google Analytics for its own tracking, that’s the organiser’s configuration and their responsibility to obtain appropriate consent from participants.

7. Updates

This policy will change from time to time as the platform evolves or regulations shift. Updates go live on this page with a revised date. For anything material, we’ll give notice via email or in-platform notification.

8. Questions

Email: [email protected]