Please enter an email address
Required

Cookie policy

Like many other websites, LeoVegas Gaming plc (“We”) and its partners (e.g. third-party service providers, advertising and marketing partners, etc.) may use cookies and pixels when you visit https://www.leovegas.com (“Website”) or access the services provided on Our Website.

The aim of this Cookies Policy is to provide the Website users (“You” or “User”) with clarity and transparency on how We collect and use cookies (“Policy”).

1. What are cookies?

Cookies are small text files that are placed on your computer or mobile device when you access websites on the internet.

Cookies help Users navigate around our website and allow Us to tailor the content of our site to fit the needs and preferences of Users.

None of the cookies We use collect your personal information (e.g. names, addresses, telephone numbers, email addresses) and they can’t be used to identify You as an individual. They typically collect anonymous identifiers associated with your device, browser, referring site URLs, time or usage information, Website preferences and settings, etc. (as further provided in this Policy).

You can find more information about cookies at http://www.allaboutcookies.org

2. Types of Cookies we use

We use the following types of cookies on our Website:

Essential Cookies

These are cookies which are:

• Used only to make our website work properly; OR
• Strictly necessary for us to provide the services expected by our users

Leobtag

- Purpose: Unique tag to identify affiliate for Netrefer
- Content: Unique tag to identify affiliate for Netrefer
- Type: Persistent
- Lifespan: 45 days - First-party
- International transfers: No

Leonrpid

- Purpose: Marketing source ID for Netrefer - Content: Marketing source ID for Netrefer - Type: Persistent - Lifespan: 45 days - First-party
- International transfers: No

Leonrbid

- Purpose: Banner ID for Netrefer
- Content: Banner ID for Netrefer
- Type: Persistent - Lifespan: 45 days
- First-party
- International transfers: No

Leonrmeta

- Purpose: Used in post backs to help affiliates to identify/connect the referral to their user database
- Content: Additional IDs
- Type: Persistent
- Lifespan: 45 days
- First-party
- International transfers: No

“SessionStorage” -Reality check limit for UK players

- Purpose: At login in order to store the timeout to display info
- Content: Integer value in seconds for the limit set by user
- Type: Session
- Lifespan: -
- First party
- International transfers: No

Key betslip

- Purpose: If any odds are added to the betslip this field is used to retain information on stakes, odds (“outcomes”) etc. so the betslip can be repopulated for returning users.
- Content: Example: {"stakes":[],"couponType":"KambiBC-state-single","outcomes":[]} - Type: Local Storage
- Lifespan: - - Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
- International transfers: No

Key retain betslip selection

- Purpose: To control whether the betslip should be repopulated for returning users within same session – if customer moves around site. - Content: Example: {"retainBetslipSelection":false}
- Type: LocalStorage
- Lifespan: -
- Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
- International transfers: No

Key selected outcomes

- Purpose: Similar to keybetslip but only stores the actual outcomes.
- Content: Example: {"outcomeIds":[]}
- Type: LocalStorage
- Lifespan: -
-Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
-_International transfers: No

Key user setting

-Purpose: Stores user settings such as odds format, whether to accept odds changes and so forth. Tied to the browser, not a specific user ID.
-Content: Example: {"oddsFormat":"decimal","showOddsChangeOptions":false,"showConfirmationBox":false,"settingsOddsChangeAction":"oddsChangeReject","oddsChangeAction":"oddsChangeReject","selectedLanguage":"enGB","eventListSort":"sortByTime"}
-Type: LocalStorage
-Lifespan: -
-Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
-_International transfers: No

Kambi-localstorage

-Purpose: Probably to be able to limit which entries to retain, default value is “all”.
-Content: “all” or empty
-Type: localStorage -Lifespan: -
-Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
-International transfers: No

Kambi-localstorage-all

-Purpose: an escaped list of all localStorage items. -Content: Example: {"id":"all","keybetslip":"{\"stakes\":[],\"couponType\":\"KambiBC-state-single\",\"outcomes\":[]}","keyselectedoutcomes":"{\"outcomeIds\":[]}","keyretainbetslipselection":"{\"retainBetslipSelection\":false}","keyusersetting":"{\"oddsFormat\":\"decimal\",\"showOddsChangeOptions\":false,\"showConfirmationBox\":false,\"settingsOddsChangeAction\":\"oddsChangeReject\",\"oddsChangeAction\":\"oddsChangeReject\",\"selectedLanguage\":\"enGB\",\"eventListSort\":\"sortByTime\"}","keyfavourites":"[]"}
-Type: localStorage -Lifespan: -
-Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
-International transfers: No

Key Favourites

-Purpose: Used to store favourite events on certain list pages.
-Content: Example: []
-Type: localStorage -Lifespan: -
-Third party, Kambi, Privacy Policy: https://www.kambi.com/privacy-policy
-International transfers: No

__cfduid

-Purpose: Zendesk chat – keeps track of who the player is – links to player ID – customer support to help with requests
-Content: At the time of writing: d5368cdfa48ad7e40c03e9af517a4b66e1516265792
-Type: Persistent
-Lifespan: 1 year
-Third party, Zendesk, Privacy Policy: https://www.zendesk.com/company/customers-partners/privacy-policy/
-International transfers: The cookie is set by a server in the United States

3pc

-Purpose: A check if customer accepts third party cookies
-Content: None
-Type: Session
-Lifespan: -
-Third-party. It’s set by us from another domain
-International transfers: No

Non-Essential cookies

These are cookies which are not required for our website to function or behave as the user would expect it to.

These include cookies relating to:

• Marketing, which gather information about the user’s browsing patterns and behaviour to target them with advertisements which would be more likely to interest them

• Analytics/ Statistics, which help website owners gather information about users on their website, such as when they first visited the website and/or how often they access it and at what particular time. These also include cookies that log how the user came across the website, using which search engine or other link.

leo_opt

Purpose: To track give user a unique identifier to recognize them from our promo pages and also to have an ID for split testing Content: A random unique sequence of alfa-numeric characters and dashes. Type: Persistent Lifespan: 60 days International Transfers: No

leo_act

Purpose: To reactivate users in split tests if they leave the site temporarily or refresh the page. Content: Test name and user attributes. For example {"split-test":{"COUNTRY":"en","PLATFORM":"mobile" Type: Persistent Lifespan: 30 minutes International Transfers: No

TDID

Purpose: To track users within registration, first deposit, returning deposit, retargeting
Content: TDID (Trade Desk ID) is the main cookie and ID used to recognize web-browser profiles over time across sites.
Type: Persistent
Lifespan: 365 days
International Transfers: No

TDCPM

Purpose: To track users within registration, first deposit, returning deposit, retargeting
Content: TDCPM (Trade Desk Cookie Partner Mapping) records which partners The Trade Desk has matched IDs with in order to prevent redundant matching calls.
Type: Persistent
Lifespan: 365 days
International Transfers: No

TTDOptOut

Purpose: To track users within registration, first deposit, returning deposit, retargeting
Content: TTDOptOut stores a static value recording the user's choice to opt out. It should be exclusive of the other cookies, so The Trade Desk will not have an ID on the browser when the TTDOptOut cookie is present.
Type: Persistent
Lifespan: 5 years
International Transfers: No

CJUUID

Purpose: Used in order for BI to track the acquisition funnel

Link: Yes, to player Uid

Lifespan: 365 Days

Third Party: No

International Transfers: Stored in EU

uuid2

Purpose: This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices. It is matched against information – such as advertising interest segments and histories of ads shown in the browser or device – provided by clients or other third parties and stored on the Platform. This information is used by clients to select advertisements for delivery by the Platform, and to measure the performance of, and attribute payment for, those advertisements. In addition, to enable clients to use non-PII they collect outside the Platform or acquire from other third parties, this cookie is sometimes matched to clients’ or other third parties’ cookies that contain such non-PII. For more information about information collected and used on the Appnexus Platform, see the Appnexus platform privacy page.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 days

Third Party: AppNexus

International Transfers: "Information related to the user ID contained within this cookie is stored securely by Appnexus and shared via SSL with MiQ for purposes of Interest Based Advertising, user counting, frequency capping and attribution.

Data is activated via Appnexus' secure segmentation APIs."

Sub-Processors: AppNexus



uuid2 (opt out):

Purpose: When a user opts out of having the Platform used to select ads based on online behavior, the unique value in uuid2 is deleted and replaced with the non-unique value “-1”.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



sess:

Purpose: The sess cookie contains a single non-unique value: “1”. It is used by the Platform to test whether a browser is configured to accept cookies from AppNexus.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



icu

Purpose: The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



anj

Purpose: The anj cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Appnexus Platform on the Platform. (See the Appnexus platform privacy page for more info.)

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



token

Purpose: Cookies that start with token are helper cookies used as a security measure with industry opt-out pages. They contain a unique value only to verify the origin of opt-out requests.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



acb

Purpose: Cookies that begin with acb have a value unique to a particular ad and are used to indicate to the Platform which ad to show and to record the fact that such ad was shown, for purposes such as billing and reporting.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



icu

Purpose: The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



anj

Purpose: The anj cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Appnexus Platform on the Platform. (See the Appnexus platform privacy page for more info.)

Link: We link to IAS. IAS pool suspicious IP addresses from across their monitoring and add these to their NHT blacklist to help their clients & the industry to prevent fraudulent ad buying

Session: Persistent

Lifespan: 90 Days

Third Party: AppNexus

International Transfers: Information stored within the cookie is passed to an Appnexus server via SSL each time a related pixel/tag URL is loaded.

Sub-Processors: AppNexus



FL_inst

Purpose: Determine if user has flash installed in case of flash creatives

Link: no

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no



PCC2

Purpose: Reporting and attribution.

Link: no

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no



PVC2

Purpose: Reporting and attribution.

Link: no

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no



TRC

Purpose: Reporting and attribution.

Link: no

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no



TUUID

Purpose: User matching, Targeting and optimization, Reporting and attribution

Link: Yes, segment IDs

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no



Ad2

Purpose: Reporting and attribution.

Link: no

Lifespan: 730 Days

Third Party: Platform161

International Transfers: no

"LocalStorage" - User Favorites

-Purpose: Stores a list of favourites selected by the user.
-Content: Array containing favourite paths
-Type: Persistent
-Lifespan: Does not expire* -First party
-International transfers: No

“LocalStorage” -User info

-Purpose: At login, user info + username/email is stored
-Content: Time for login, username/email
-Type: Persistent
-Lifespan: Gets overwritten by new login
-First party
-International transfers: No

“LocalStorage” -Danish players

-Purpose: Store list of emails identified with NemID for UI purposes
-Content: Array containing emails
-Type: Persistent
-Lifespan: Does not expire* -First party
-International transfers: No

Facebook

-Purpose: Being able to target better has to do with marketing, it allows us to choose who we want to show our ads to. Thus, leading to us showing them to a more relevant audience.
-Content: The user’s activity on our website -We track what people do, did they visit the sports page? Or did they complete an NDC? They are entered into different categories for our marketing purposes depending on their activity. Someone who has completed an NDC is excluded from receiving any new customer offers as an example.
Most information is gathered, or possible to gather. We mainly focus on the sign-up steps.
-Type: Persistent
-Lifespan: 180 days
-Third Party, Facebook, Privacy Policy: https://www.facebook.com/policy.php
-International transfers: Yes

Twitter

-Purpose: Being able to target better has to do with marketing, it allows us to choose who we want to show our ads to. Thus, leading to us showing it to a more relevant audience.
-Content: The user’s activity on our website -We track what people do, did they visit the sports page? Or did they complete an NDC? They are entered into different categories for our marketing purposes depending on their activity. Someone who has completed an NDC is excluded from receiving any new customer offers as an example.
Most info is gathered, or possible to gather. We mainly focus on the sign-up steps.
-Type: Persistent
-Lifespan: 180 days
-Third Party, Twitter, Privacy Policy: https://www.facebook.com/policy.php
-International transfers: Yes

leo:latest-games

-Purpose: Store latest played games for a player to display it more user friendly on the site. -Content: Name of game + timestamp for the 11 latest games
-Type: localStorage
-Lifespan: -
-International transfers: No

Google Adwords

-Purpose: Analytics -Content: User ID, Search, History, Gender, Age, Interests, Visits, Actions on website – deposits, sign ups
-Type: -
-Lifespan: -
-Third party
-International transfers: No

Google Analytics

-Purpose: Analytics
-Content: Player ID, Username, Email address, Admin rights, Name, Language, Location, Browser & OS, Network, Device, Channels, Source, Medium, Campaigns, Pages visit, Payment provider, Clicked postcard, Search queries, Games clicked, Scroll depth, Medic verification, deposits
-Type: 1 session, 1 user
-Lifespan: Session cookie expire after 30 minutes. User cookie after 2 years
-Third Party
-International transfers: No

Google Adform Store latest

-Purpose: Analytics
-Content: Player ID, Deposit Value, IP Address, Cookies ID, Deposit currency -Type: -
-Lifespan: -
-Third Party
-International transfers: No

WideSpace Conversion Tag

-Purpose: Campaign Optimization
-Content: Customer Behaviour – which ads the user viewed and interacted with
-Type: Persistent
-Lifespan: 1 year -Third party
-International transfers: No

Appsflyer

-Purpose: Attribution and Analytics for the apps (tracking where the user is coming from and understanding behaviour on app) -Content: platform, click time, install time, media source, country code, city, IP address, Wi-Fi or data, language, device name, device type, OS version, event name and time, operator, advertising ID, device brand and model, keywords searched
-Type: Persistent
-Lifespan: 30 days -Third party
-International transfers: Yes, Appsflyer is based in Israel

Abuuid

-Purpose: Unique tag that identifies if you shall be provided with new fresh features on the website before anyone else
-Content: Unique tag to identify which feature cohort you belong to
-Type: Persistent
-Lifespan: 365 days - First-party
-International transfers: No

3. How we use cookies

We use cookies for a number of reasons, including, but not limited to:

• to assist new customers during the sign-up process,
• to allow customers set Website preferences
• to allow customers to navigate between pages of the Website more efficiently
• to run the functionality of the Website optimally and efficiently
• to activate certain features of the Website
• to gather information about customer/User activity on the Website and to understand how it is used
• to detect and prevent fraudulent use of the Website
• to track how customers/Users, arrive at our Website for marketing purposes and to track referrals
• to deliver more relevant advertising to our customers/Users at the websites and mobile applications they visit
• for research and analytical purposes to see who Users interact with the Website in aggregate

We do not, under any circumstance, sell information collected via cookies.

4. Managing Cookies

If you do not want Websites to place cookies on Your computer or mobile device at all, you can adapt your browser settings as such that you will be notified before any cookie is placed. You can likewise adapt the settings as such so that your browser refuses all cookies, or only the third-party cookies.

Likewise, you can remove any of the cookies that have already been placed. Please note that you will have to adapt the settings for each browser on any mobile device and computer You use separately.

Without cookies enabled we can't guarantee that our website and Your experience would be optimal, and in some cases, you may not be able to log in to your account if cookies are disabled.

It is important to note that different browsers offer different ways of configuring your browser’s cookie settings. The following links provide you with steps on how to use, erase or adjust cookie files on your particular browser:

Internet Explorer -https://support.microsoft.com/en-us/help/17442/windows-internet-explorer-delete-manage-cookies

Firefox -https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences

Google Chrome -https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DDesktop&hl=en

Safari -https://support.apple.com/kb/ph21411?locale=en_US

If necessary, consult your browser’s “help” function, or go to your browser’s manual. If you wish to disconnect cookies of specific parties, you can do this through

http://www.youronlinechoices.eu.

Please note that We aren't responsible for the content of external websites.

Deposit and stake £50

For a chance to win a

trip to Lapland

Read more

Proud sponsors of:


LeoVegas Gaming plc is a company registered in accordance with Maltese Law with registration no C59314, Registered office: LeoVegas Gaming plc., Level 7, The Plaza Business Centre, Bisazza Street, SLM 1640, Sliema, Malta. LeoVegas Gaming plc is licensed and regulated by the Malta Gaming Authority and holds the following licences - MGA/CRP/237/2013 issued on the 6th December 2013, offering Type 1 Gaming Services under Approved Service Provider licences MGA/B2B/352/2016, MGA/B2B/187/2010, MGA/B2B/120/2006, MGA/B2B/139/2007, MGA/B2B/109/2004, MGA/B2B/112/2004, MGA/B2B/225/2012, MGA/B2B/137/2007, MGA/B2B/246/2013 and MGA/B2B/230/2012, also Type 2 Gaming Services under Approved Service Provider licences MGA/B2B/185/2010 and MGA/B2B/286/2014LeoVegas.com is operated by LeoVegas Gaming plc. in the UK under casino license from the Gambling Commission - UK Licence Number: 000-039198-R-319450-017 (originally issued November 1st 2014) and a Betting licence from the Gambling Commission - UK Licence Number: 000-039198-R-319450-017 (originally issued April 29th 2016).

LeoVegas has a remote bookmaker’s licence in Ireland awarded by the Revenue Commissioners, licence reference number 1012453, issued on 25th January 2017.
LeoVegas Gaming plc. is operating under casino licence number 15-1660384 issued on the 3rd October 2016 by the Danish Gambling Authority (spillemyndigheden.dk/), who keeps the operation of gambling services under supervision. LeoVegas Gaming plc. also holds a betting licence numbered 17-0700928 in Denmark issued on 29th June 2017 by the Danish Gambling Authority.
Gambling can be addictive. Play responsibly.