By Michael J.A. Wohl
Ruby Fortune Casino has been operating since 2003, and twenty-plus years of continuous operation across three regulatory frameworks — the Kahnawake Gaming Commission, the Malta Gaming Authority, and the AGCO — shapes its cookie environment in specific ways. The MGA licence brings GDPR-aligned consent standards into the platform’s infrastructure, which is more demanding than the KGC baseline alone. The six-tier loyalty program, running from Blue through to Privé, requires cookies to track years of accumulated points and tier progression for long-term players. And the daily Bonus Wheel and ongoing promotional calendar create a marketing cookie environment built around frequent, time-sensitive offers.
The four cookie categories at Ruby Fortune
| Category | Purpose | Rejectable? |
|---|---|---|
| Strictly necessary | Session authentication, security, jurisdictional checks, consent record | No — required for platform function |
| Functional | Language, interface settings, loyalty tier display, bonus tracking | Yes — preferences reset on each visit |
| Analytics | Game engagement, session performance, bonus completion rates | Yes — limits data collection |
| Marketing | Retargeting, Bonus Wheel campaign tracking, SMS/email attribution | Yes — limits promotional reach |
Because Ruby Fortune’s MGA licence requires GDPR-aligned consent standards, the cookie consent mechanism Canadian players encounter likely offers more granular per-category control than at KGC-only platforms — a genuine practical benefit of this particular licensing combination.
Strictly necessary cookies: the operational core
- Session authentication tokens — maintaining your logged-in state across the casino lobby and Evolution-powered live dealer section
- Security cookies — CSRF protection and account action verification, supported by Cloudflare encryption infrastructure
- Jurisdictional verification — confirming whether your account falls under KGC or AGCO regulation based on location, given the dual-framework structure
- Cookie consent record — storing preference selections persistently
- Fraud prevention flags — real-time transaction monitoring across the platform
- Loyalty program session integrity — verifying point accumulation accuracy during active play sessions
The jurisdictional verification function is more involved at Ruby Fortune than at single-licence platforms. Because Ontario players fall under AGCO regulation while players in other provinces fall under KGC, the platform’s geolocation cookies serve a dual classification function — determining which regulatory framework and consumer protection set applies to a given account.
Functional cookies: the six-tier loyalty program and bonus tracking
- Language and interface preference storage
- Game lobby settings — hot and cold filters, recently played, favourited titles across 500-plus games
- Loyalty tier display — showing current status across the six tiers from Blue to Privé and accumulated points
- Welcome bonus wagering progress — tracking completion toward the wagering requirement across three deposit stages
- Daily Bonus Wheel cooldown tracking — recording when the wheel was last spun and when it becomes available again
- Responsible gambling display — ensuring configured limits appear consistently
Analytics cookies: two decades of behavioural data
| What is measured | Operational purpose |
|---|---|
| Game engagement by provider (Games Global, Evolution, Stormcraft, Rabcat) | Library curation across 500-plus titles |
| Welcome bonus completion rates across three deposit stages | Evaluating the wagering structure’s effectiveness |
| Loyalty tier progression timelines | Six-tier program development, including Privé qualification patterns |
| Daily Bonus Wheel engagement frequency | Recurring engagement mechanic effectiveness |
| Session length distribution | Responsible gambling monitoring baseline |
| Mobile app vs browser usage | Platform investment priorities |
Marketing cookies: SMS, email, and retargeting
- Retargeting — promotional content on external sites after casino visits
- Bonus Wheel campaign attribution — measuring engagement with daily spin promotions
- SMS campaign tracking — separate from email, given Ruby Fortune’s active SMS promotional channel
- Email campaign attribution — tracking the calendar of offers viewable from the account menu
- Affiliate attribution — recording referral sources
Rejecting marketing cookies limits retargeting and reduces personalisation of promotional communications, though it doesn’t automatically opt you out of SMS or email — those require separate consent management in account settings.
Managing cookie preferences
- Interact with the cookie consent mechanism on first visit — the MGA licence means this should offer granular per-category controls
- Adjust preferences anytime through privacy or account settings
- Manage browser-level cookie controls in Chrome, Firefox, Safari, or Edge
- Separately manage SMS and email marketing consent in account settings, as these are distinct from cookie-based marketing tracking
