What This Cookie Policy Covers
Cookies are small text files a website stores on your device to remember information between visits. AllyBet places cookies when you load any page, sign into an account, or interact with the sportsbook and casino interface. This policy explains what those files do, why we use them, and how you can limit or remove them.
A cookie itself cannot access files on your hard drive or run programs. It typically holds a unique identifier and a handful of settings, nothing more. Browsers send that identifier back to the originating server on each request, which lets a site recognize a returning visitor rather than treating them as brand new every time.
Beyond classic cookies, we and our technology partners use related storage methods: local storage objects, session storage, and pixel tags embedded in emails or pages. Where this policy refers to "cookies," it covers those related technologies unless stated otherwise. Full detail on how personal data collected through cookies is handled sits in our privacy policy, which this page complements rather than replaces.
Why Does AllyBet Use Cookies?
Cookies keep a betting session usable. Without them, a bet slip would empty itself between pages and a login would expire on every click. AllyBet relies on cookies for four broad jobs: keeping you signed in securely, remembering display choices, measuring how pages perform, and, where you have agreed to it, tailoring promotional messages.
None of those jobs require selling personal data to outside advertisers, and AllyBet does not do that. Cookies set here support the operation of the site you are already using, plus a small set of analytics and marketing integrations disclosed further down this page.
What Categories of Cookies Are Set?
Strictly Necessary and Functional Cookies
Strictly necessary cookies keep the account system, bet slip, and cashier working. They cannot be switched off through a preference toggle because the site cannot function securely without them — blocking them at the browser level will break login and checkout rather than just muting a feature.
- Session and authentication tokens: confirm you are logged in and protect against cross-site request forgery on every page load.
- Load balancing markers: route your traffic to the correct server during high-volume periods, such as major match kickoffs.
- Age-gate and geolocation flags: record that you confirmed eligibility to view wagering content in your province.
Functional cookies are not strictly required but improve day-to-day use. They remember odds format (decimal, fractional, or American), preferred language, dark or light interface mode, and which sports you follow most often.
Analytics and Marketing Cookies
Analytics cookies tell us which pages load slowly, which betting markets get the most traffic, and where visitors abandon a registration form. The data is aggregated; it helps engineering teams fix friction points rather than identify a specific bettor by name.
Marketing cookies, used only where local consent rules allow, measure whether a promotional campaign led to a completed signup and prevent the same offer banner from repeating endlessly once you have already seen it. They can also cap how often a re-engagement message appears to a lapsed account holder.
Categories map loosely to typical browser consent tools: necessary, functional, analytics, and advertising. You can accept some categories and decline others through your browser settings, described later on this page.
Which Specific Cookies Run on This Site?
The table below lists representative cookie names, their purpose, and typical lifespan. Exact identifiers can change as the platform is updated, but the categories and retention windows stay consistent.
| Cookie Name | Category | Purpose | Typical Duration |
|---|
| ab_session | Strictly Necessary | Keeps you authenticated between page requests | Session (deleted on logout/browser close) |
| ab_csrf | Strictly Necessary | Blocks forged form submissions on account and cashier pages | Session |
| ab_geo | Strictly Necessary | Confirms provincial eligibility for wagering content | 24 hours |
| ab_odds_format | Functional | Remembers decimal, fractional, or American odds display | 12 months |
| ab_lang | Functional | Stores interface language preference | 12 months |
| _ga / _gid | Analytics | Aggregated traffic and page-performance measurement | Up to 24 months |
| ab_ref | Marketing | Attributes a signup to the referring promotional source | 30 days |
Payment cookies are handled separately by our processors during an active deposit or withdrawal — see the third-party section below for how those integrations work alongside our payment methods.
Do Third Parties Set Cookies on AllyBet Pages?
Yes, a limited set of vetted partners set their own cookies when their service is active on a page. Analytics vendors log anonymized usage patterns; payment gateways set short-lived cookies solely while a deposit or withdrawal form is open, to prevent duplicate submissions and fraud.
Odds-feed and live-scoring widgets, including the in-play data shown on our live betting pages, may also load a small cookie to keep a match view synchronized without reloading the entire page. None of these partners are permitted to use AllyBet visitor data for purposes unrelated to the service they provide us.
We do not control third-party cookie policies directly. Each vendor publishes its own retention and processing terms, and those terms govern any data the cookie itself captures once it leaves our systems.
How Does Cookie Use Relate to Gambling Safeguards?
Certain cookies exist specifically to support responsible play rather than marketing or analytics. When you set a deposit limit, session reminder, or time-out through our responsible gambling tools, a cookie or account-linked flag records that choice so the restriction applies consistently across devices and sessions.
Age and location cookies serve a similar protective role: they stop underage or out-of-jurisdiction visitors from reaching wagering markets, and they refresh regularly so a changed location is detected quickly rather than assumed indefinitely from a single earlier check.
Disabling cookies broadly, including the necessary category, can interfere with these safeguards by preventing the platform from remembering a self-imposed limit. Bettors who want strict privacy controls should adjust analytics and marketing cookies first, and speak with support before blocking safeguard-related cookies outright.
How Can I Control or Delete Cookies?
1 1. Use Your Browser's Built-In Cookie Settings
Chrome, Firefox, Safari, and Edge each let you view, block, or delete cookies by domain through their privacy or site-settings menu. Searching "[your browser name] clear cookies" brings up current, browser-specific steps, since menu locations shift between versions.
2 2. Adjust Category-Level Consent on First Visit
A consent banner appears on your first visit, letting you accept or decline analytics and marketing categories individually. Strictly necessary cookies are not offered as a toggle because the site cannot authenticate an account or process a cashier request without them.
3 3. Opt Out of Specific Analytics Providers
Major analytics vendors publish dedicated opt-out extensions or pages. Installing one of these stops that vendor from associating future visits with your existing analytics identifier, independent of the browser-level cookie setting.
4 4. Use Private or Incognito Browsing for a Single Session
Private browsing windows discard most cookies once closed, which is useful for a one-off visit from a shared or public device. It does not, however, replace a formal self-exclusion request logged with support for ongoing account restrictions.
