logo Sign Up

Cookies Policy

Cookies Policy for National Lottery Casino
Introduction

This Cookies Policy explains how National Lottery Casino uses cookies and similar browser storage technologies to support session handling, authentication, analytics, performance, user preferences and other browsing functionality. The aim is to describe practical effects, the options available to manage these technologies, and how they support a secure and reliable experience across web and app platforms.

What cookies and similar technologies are

Cookies are small text files stored by your browser or device that help a website remember information about your visit. Related technologies include localStorage, sessionStorage and indexed databases (sometimes called IndexedDB). These stores let a site keep small amounts of information on your device to maintain session state, remember preferences, or optimize content delivery. Tokens kept in secure device storage inside native apps serve a similar purpose for mobile sessions and persistent logins.

Why these technologies are used

They make everyday site functions possible and convenient: keeping you signed in during a browsing session, remembering language or accessibility preferences, collecting aggregated performance data to improve reliability, and protecting account integrity. They allow the platform to restore your session after a short interruption, keep interface settings intact between visits, and help engineers diagnose and fix issues without exposing personal details.

Types of cookies and related uses

Essential cookies

Essential cookies are necessary to operate core features. They support login sessions, confirm authentication tokens, protect the integrity of the session and enable checkout or purchase flows. These cookies are typically marked secure and HttpOnly, and they expire at the end of the browsing session or after a short configured period.

Example behaviors:

  • Maintaining an authenticated session while you navigate pages.
  • Storing non-sensitive routing or session identifiers needed by the server.
  • Preventing cross-site request forgery by carrying short-lived anti-forgery tokens.

Session cookies

Session cookies exist only for the duration of your browser session and are removed when the browser is closed. They are commonly used to preserve in-session state such as open pages, temporary choices and active form data. For users with active sessions, an automatic reality-check or session timer can be driven by session-cookie activity to remind about time spent.

Typical lifespan: until browser close (or app session end). Default session timeout: configured to balance security and convenience (example: 60 minutes of activity with an in-session warning).

Persistent cookies

Persistent cookies remain on your device for a set period to remember preferences and support login persistence between visits. These are used when you choose “remember me,” to keep language choices, or to allow a safer single sign-on user experience.

Typical lifespans:

  • Short-term persistent cookies: 7–30 days (for “remember me” or preference continuity).
  • Mid-term cookies: 90–180 days (for device recognition or feature opt-ins).
  • Long-term cookies: up to 24 months (for preference storage or aggregated analytics where allowed).

Functional cookies

Functional cookies enable features you request such as saved favourites, dark mode settings, one-tap game launch preferences or a personalized quick-access menu. They do not profile you for advertising and are focused on your experience and convenience.

Analytics and performance cookies

Analytics cookies collect aggregated, anonymised information about how the site and app are used. These cookies help measure page load times, error rates, session lengths, device types, browser performance and feature usage so teams can prioritise reliability and speed improvements.

How this helps:

  • Identify slow pages or broken flows so they can be fixed.
  • Measure average load time on typical network conditions (for example, 4G vs 3G).
  • Produce aggregated dashboards used to make the product faster and more stable.

Analytics providers may set cookies for aggregated measurement. Data is used in non-identifying form unless you choose to link a browser session to your account through a consenting login flow.

Preference and language settings

Cookies and local storage are used to persist language, accessibility choices, and UI preferences (for example, dark mode and layout selections). When you set a preference, the value is stored so the site displays consistently on return visits across devices where you are signed in.

Login and session continuity

Login persistence is implemented with secure, short-lived tokens stored in cookies or in app-secure storage. These tokens allow a session to continue across pages and, where permitted, across visits (remember-me). For mobile apps, a device token or secure key is used in place of cookies to maintain continuity and to allow biometric re-entry (Face ID / fingerprint) in a protected manner.

Security measures used with these tokens:

  • Secure and SameSite cookie attributes to reduce cross-site exposure.
  • HttpOnly flags to prevent direct access from client-side scripts.
  • Short lifespans for active sessions with re-authentication required for sensitive actions.

Device recognition

Cookies and local storage values may hold non-personal device identifiers to detect familiar devices. Device recognition helps to present appropriate account security steps, reduce friction for trusted devices, and spot unusual sign-in attempts that may prompt additional verification.

Security-related cookies

Cookies used for security monitor session integrity and support fraud detection and abuse prevention. These cookies help flag unusual behaviour and may be combined with server-side signals to trigger protective actions (for example, requiring re‑authentication or temporary session suspension). Security cookies are focused on improving account safety rather than marketing or profiling.

Browser storage technologies beyond cookies

Modern web apps may use:

  • localStorage for persistent non-sensitive preferences.
  • sessionStorage for short-lived state tied to a single browser tab.
  • IndexedDB for larger client-side caches or offline resources.These mechanisms complement cookies and are subject to the same browser controls described below.

Third‑party integrations

Certain third-party services such as analytics providers, content delivery networks, payment processors and support tools may place cookies when their code runs on a page. Examples include analytics services that help with site performance and CDN providers that improve load times. Third parties operate under their own policies; you can manage many of these via cookie preference settings or directly through third-party opt-outs.

Marketing or communication preferences

When you opt in to marketing communications, a small set of cookies may be set to remember consent and tailor the communications you receive. Opting out prevents further marketing-oriented cookies from being set, although it does not remove essential or functional cookies required for site operation.

Consent, control and cookie management
Cookie consent management

National Lottery Casino provides a cookie preference interface where you can choose which categories to allow: essential, functional, analytics, and marketing. Essential cookies remain active for site operation. Choice changes take effect immediately for newly set cookies; removing consent may require a page reload or sign-out to complete.

Browser cookie controls

Most browsers allow you to view and control cookie settings. You can:

  • Block third-party cookies.
  • Delete individual cookies or clear all cookies.
  • Set the browser to ask you before storing cookies.Mobile browsers provide similar controls; app-level settings for persistent tokens are available inside account settings.

If you prefer not to store non-essential cookies, adjust settings in your browser or use the site cookie preferences tool. For native apps, you can manage app permissions and clear app data via your device settings.

How to clear or disable cookies

Clearing cookies is usually done through the browser’s Settings or Privacy section. Steps vary by browser, but typically involve:

  • Opening Settings > Privacy & Security.
  • Selecting “Clear browsing data” or “Cookies and other site data.”
  • Choosing the time range and clearing cookies.Clearing cookies will sign you out and reset saved preferences. In mobile apps, clearing app storage or uninstalling the app removes stored tokens and cached data.

Site functionality when cookies are disabled

Disabling cookies or blocking storage can affect how National Lottery Casino works:

  • You will be signed out more frequently and may not be able to use features that require authentication.
  • Preferences such as language, dark mode and favourites will not persist between visits.
  • Some pages may fail to load correctly, or interactive features (one-tap game launch, quick-access menus) may be unavailable.
  • Aggregated analytics and performance diagnostics will be reduced, making it harder to optimise your experience.

If you wish to minimise tracking but keep full functionality, allow essential and functional cookies while disabling analytics and marketing cookies in the cookie preferences.

Technical diagnostics, performance optimisation and aggregated analytics
Role of cookies in diagnostics and optimisation

Performance cookies and related storage capture aggregated timing, error and load data to identify regressions and improve responsiveness. This enables product teams to prioritise fixes (for example, image optimisation that reduces bandwidth). The data used for such work excludes personally identifying details unless you have explicitly consented and linked that session to an account.

Aggregated analytics information

Reports derived from analytics are aggregated and used to improve navigation flows, reduce page load times, and refine prioritisation of mobile and web features. Insights include device type distribution, common error pages, and average session lengths. These aggregated insights guide product decisions and do not target individuals.

Additional operational notes
Retention of cookie data

Retention periods vary by cookie category. Essential session cookies are short-lived; persistent cookies that store preferences or consent typically remain for months to allow convenience; analytics cookies may persist for longer but are used in aggregate. You may review exact cookie lifespans via your browser’s developer tools or the cookie preference panel.

Mobile apps and native storage

Native iOS and Android apps use secure device storage for tokens and preferences rather than standard browser cookies. App settings include options to clear local data and revoke persistent login tokens. Biometric sign-in stores a device-scoped token in secure hardware-backed storage; removing app storage or uninstalling the app will invalidate those tokens.

Changes to this policy

As technologies and services evolve, cookie practices are periodically reviewed and may be updated. Changes will be reflected on this page and, where required, you will be asked to review or renew your cookie preferences.

How to contact us about cookies

For questions about cookie practices, to request details on cookies set in your browser, or to ask for a record of the persistent identifiers used for your account sessions, please use the contact options provided within the National Lottery Casino platform.

If you need to act immediately:

  • Open the cookie preferences panel on any National Lottery Casino page.
  • Use browser settings to manage or clear cookies.
  • For app-related tokens, clear app data or sign out and remove stored credentials from device settings.

National Lottery Casino aims to balance a smooth, personalised experience with clear, manageable controls. Adjust settings anytime to match your comfort level with cookies and local storage.