Skip to main content

MGM Casino cookie policy explained for Ontario players

By Michael J.A. Wohl – Updated June 2026

The MGM-branded platform in Ontario combines a casino and sportsbook under a single account, connects online play to the MGM Rewards loyalty ecosystem shared with MGM’s physical properties, and operates with mandatory AGCO geolocation requirements at every session. Each of these features has cookie implications that go beyond what a simpler, single-product Ontario casino would involve. This guide explains what cookies actually do here, how the dual-parent corporate structure factors in, and what Canadian players can control under PIPEDA and Ontario’s privacy framework.

Why this platform’s cookie environment is more layered than most

Three features create a cookie environment worth examining specifically. First, the combined casino-and-sportsbook model means cookies track both your casino session behaviour and your sports betting activity – which markets you browse, what odds you’ve selected, how the two activities interact within a single account. Second, the MGM Rewards connection means cookies may facilitate data flows linking your online activity here to the broader MGM Resorts loyalty infrastructure used at physical properties. Third, the AGCO’s mandatory geolocation requirement means Ontario presence verification happens through cookies at every single session – a layer that doesn’t exist at offshore platforms.

The four cookie categories

CategoryPurposeRejectable?
Strictly necessarySession authentication, Ontario geolocation, security, consent recordNo – required for platform function
FunctionalLanguage, interface settings, sportsbook preferences, MGM Rewards displayYes – preferences reset on each visit
AnalyticsCasino and sportsbook engagement measurementYes – limits data collection
MarketingRetargeting, MGM Rewards attribution, Entain group campaignsYes – limits promotional reach

Under PIPEDA and Ontario’s privacy framework, non-essential cookies require meaningful consent before activation – the AGCO operating agreement reinforces this as a licensing condition.

Strictly necessary cookies: what can’t be turned off

  • Session authentication tokens – maintaining your logged-in state across casino lobby and sportsbook simultaneously
  • Ontario geolocation verification – confirming physical presence in the province at every real-money session, an AGCO licensing requirement
  • Security cookies – CSRF protection and account action verification
  • Cookie consent record – storing your preference selections
  • Fraud prevention flags – real-time monitoring across casino and sportsbook
  • Sportsbook session integrity – maintaining live in-play betting continuity

The geolocation cookie is worth dwelling on because it’s not optional in any sense – it’s a direct condition of the AGCO licence. Players using VPNs to appear located in Ontario while physically elsewhere are in breach of the platform’s terms, and this is the cookie function that monitors for that.

Functional cookies: MGM Rewards and sportsbook integration

  • Language and interface preferences
  • Casino game lobby settings across the 2,500-plus title library
  • Sportsbook preferences – favourite leagues, odds format, markets followed
  • MGM Rewards tier and points display – showing your status within the loyalty program shared with MGM’s physical properties
  • Responsible gambling display persistence across both casino and sportsbook
  • Demo mode session indicators for slots

The MGM Rewards display function is the most distinctive functional cookie element here. Because your loyalty status connects to an ecosystem extending beyond this single Ontario platform, functional cookies maintain the display of that cross-property status within your account interface. Rejecting functional cookies means losing this display on each visit – not losing the underlying status itself, which is held server-side, but losing the convenient persistent view of it.

Analytics cookies: combined product measurement

What is measuredOperational purpose
Casino game engagement across 2,500+ titlesLibrary curation
Sportsbook market browsing and bet conversionSports product development
Cross-product session transitions (casino to sportsbook and back)Understanding combined platform usage patterns
MGM Grand Millions jackpot engagementJackpot product investment
Responsible gambling tool engagement ratesPlayer protection programme effectiveness
App vs browser session splitMobile development priorities

From my research perspective, the cross-product session transition data is particularly interesting. A player who moves between casino slots and live sports betting within a single session is engaging in a different behavioural pattern than someone who sticks to one product – and platforms that track this transition data are, whether by design or not, building a picture of how combined-product access shapes overall engagement time. This is the kind of data point that’s directly relevant to research on how platform structure influences total time spent gambling, and it feeds into Entain’s player protection monitoring as well as commercial development.

Marketing cookies: the dual-brand promotional ecosystem

  • Casino retargeting – promotional content on external sites after casino visits
  • Sportsbook retargeting – based on sports markets browsed
  • MGM Rewards attribution – connecting online behaviour to the broader MGM loyalty marketing infrastructure
  • Entain group campaign coordination – aligning this platform’s marketing with group-wide infrastructure
  • Affiliate attribution – tracking acquisition source

Marketing cookies require explicit consent under PIPEDA. Rejecting them prevents retargeted advertising – both casino and sportsbook – from following you outside the platform, and limits how your activity here connects to MGM’s broader marketing ecosystem.

Managing your cookie preferences

  1. Interact with the consent mechanism on first visit – accept all, reject non-essential, or configure by category
  2. Adjust preferences anytime through privacy settings
  3. Manage per-site controls through your browser – Chrome, Firefox, Safari, Edge all support this
  4. Clearing cache removes device-stored cookies but not data already sent to the platform’s servers