Cookies Policy

How BPL Stadium uses cookies and similar technologies. This Policy explains how and why we place cookies, localStorage and sessionStorage entries, SDK identifiers and pixels across bplstadium.com and related sub-domains. It is aligned with the UK GDPR and PECR, and mirrors EU GDPR / ePrivacy expectations.

Last updated: 22 May 2026 · Effective date: 22 May 2026 · Version 5.0

1. Overview

This Cookies Policy explains how BPL Stadium uses cookies and similar technologies (including localStorage, sessionStorage, SDK identifiers and pixels) across bplstadium.com and related sub-domains (the “Service”). It complements our Privacy Policy and sits alongside in-game currency top-ups, the player dashboard and any other authenticated feature.

By interacting with the cookie banner or preferences centre — when one is introduced — you will be able to manage consent for every non-essential category. Strictly-necessary entries remain active at all times so the simulator can stay secure and functional.

Controller: the publisher of BPL Stadium (demonstration / portfolio project).
Contact: privacy@bplstadium.com
Scope: the football simulator, in-game currency ledger, Predictions interface, pitchside-advertising feature, Account dashboard and supporting pages.

2. What are cookies (and similar technologies)?

Cookies are small text files placed on your device to enable secure sessions, remember preferences and measure performance. Similar technologies include:

• localStorage / sessionStorage keys — used for in-browser UI state and offline persistence of the Account record.
• SDK identifiers — used by mobile or native components in apps. The current build of the Service does not use any such identifiers.
• Pixels — tiny image requests typically used for analytics or attribution. The current build does not use any pixels.

Within BPL Stadium, these technologies help with authentication, session security, localisation (language and interface preferences), dashboard filters, abuse / fraud monitoring and — where you opt in — analytics. They never load advertising trackers in the current build.

3. Categories we use

We group cookies and similar technologies into the following categories. Only the Necessary category runs without consent; every other category waits for your explicit choice once a consent banner is introduced.

4. Typical cookies & storage keys

Specific names, providers and lifetimes may change as we update the Service. The definitive, live list will be available in the Cookie Settings panel once it is introduced. The table below describes the keys the current build writes to your device, plus a few illustrative future entries marked accordingly.

5. Consent & lawful basis

5.1 Strictly necessary. Necessary cookies and storage keys rely on the “performance of a contract” lawful basis under the UK GDPR, because they are required to run your Account, secure your session and deliver the simulator you have asked for.

5.2 Functional, analytics and marketing. Functional, Analytics and Marketing categories rely on consent under the UK GDPR and PECR. We will not set entries in these categories without your prior, freely given, specific, informed and unambiguous opt-in.

5.3 Privacy-first analytics under legitimate interests. If we deploy a strictly server-side, IP-truncated, no-cross-site analytics tool with short retention and aggregated reporting, we may rely on legitimate interests for that specific component. Where we do so, the entry will be explicitly labelled in this Policy and in the Cookie Settings panel.

5.4 Security / anti-abuse. Security technologies rely on the legitimate interests of keeping the Service safe for you and other users.

6. How we record and retain consent

When a consent banner is introduced and you save your cookie choices, we will log:

• the categories you accepted and rejected;
• the version of this Policy in force at that moment;
• the timestamp of your decision;
• technical metadata (IP address, user-agent string) for evidential and security purposes.

Consent records will be retained for at least 24 months and up to 6 years where required for regulatory enquiries or dispute resolution, consistent with the retention schedule set out in our Privacy Policy.

7. Third parties & international transfers

The Service relies on a small number of third parties for hosting infrastructure, fonts and the open-source 3D-rendering library. Some of these providers may be located outside the UK / EEA. Where transfers of personal data occur, we rely on:

• UK adequacy regulations, where the destination country has been recognised as providing an adequate level of protection;
• the UK or EU Standard Contractual Clauses (SCCs); and
• supplementary technical and organisational controls such as encryption, access controls and data minimisation.

Once a Cookie Settings panel is introduced, it will list the third-party vendors currently in scope. The Service does not engage third-party advertising networks, marketing-attribution SDKs or social-media plug-ins in the current build.

8. Managing or withdrawing consent

When a banner is introduced, you will be able to accept, reject or customise non-essential categories from:

• the banner shown on first visit;
• a persistent “Cookie Settings” link placed in the footer of the Service.

Your latest choice will apply going forward and will not affect processing that already took place on the basis of your earlier choice. You may withdraw consent at any time without making the Service materially harder to use.

You can also clear cookies and storage keys directly through your browser, or use the browser’s private / incognito mode. Blocking strictly-necessary entries will prevent the Service from working — in particular, sign-in, Balance display and Prediction placement will not be available.

9. Do Not Track / Global Privacy Controls

If your browser sends a Global Privacy Control (GPC) signal, or similar “Do Not Track” preference, we treat it as an opt-out from non-essential cookies wherever technically feasible under applicable law.

Standards differ across browsers and operating systems, and not every environment exposes a reliable signal, so we cannot guarantee universal honouring in legacy browsers. We will continue to keep our implementation aligned with the latest guidance from the UK Information Commissioner’s Office and the European Data Protection Board.

10. Changes to this Policy

We may update this Cookies Policy when we add new integrations, analytics tools, payment partners (if real-money payments are introduced in the future) or when legal requirements change. Material updates will be announced via an in-product notice, banner and / or email to registered users.

The “Last updated” date at the top of this Policy always reflects the latest version. Changes apply prospectively.

11. Contact

Questions about cookies or this Policy can be directed to:

• Email: privacy@bplstadium.com
• Postal: BPL Stadium (Demo), Demo Lane 4, London, United Kingdom

For broader data-processing details please see our Privacy Policy and our Terms & Conditions.