Legal & support
Cookie notice
This notice explains how Lightning TV stores or reads information on your browser or device. It covers cookies, local storage and session storage. Our Privacy notice explains how we use personal information associated with them.
It applies only to the Lightning TV streaming service operated by Milton Keynes Ice Hockey Club Ltd. The main Milton Keynes Lightning website, merchandise shop, Stripe checkout and other external services may use their own cookies under their own notices.
What we use
Cookies are small text files stored by a website in your browser. Local storage and session storage are similar browser features. The values listed below do not contain your password, postal address, full payment-card details or a broadcast-access token, although an identifier may be linked to information held securely on our servers.
Scroll horizontally to read every column if needed.
| Name | Type | Purpose | Typical duration |
|---|---|---|---|
mkltv_beta_session | First-party cookie | Keeps you signed in, connects requests to your server-side session and preserves the service state you ask us to remember, including an applied discount code while you review and complete that purchase. | Up to 14 days, or until you sign out or clear it. |
mkltv_beta_csrf | First-party cookie | Protects forms and account actions against cross-site request forgery. | Up to 364 days. |
mkltv-playback-device-v1 | Local storage | Creates a random browser identifier so the one-active-device rule can distinguish this browser. It may be linked to device counts and access investigations held securely on our servers, but it does not store a playback secret. | Until you clear site data or the browser removes it. |
mkltv-playback-tab-v1 | Session storage | Creates a random identifier for the current tab so playback sessions and takeovers can be managed safely. | Until the tab or its browser session closes. |
mkltv-boundary-* | Session storage | Records that this tab has already refreshed at a fixture or video countdown boundary, preventing a repeated refresh loop. It contains a fixture identifier and scheduled timestamp, not a playback token. | Until the tab or its browser session closes. |
| Amazon IVS playback service worker | Browser service-worker registration and code | Helps compatible browsers, including native iPhone and iPad players, process protected live-stream requests. It is scoped to the site's game pages and is not an advertising or offline-download feature. | The browser may retain the registration and code until you clear site data or the browser removes them. |
These technologies are strictly necessary to provide account security, checkout protection and the protected playback service you request. They are not used for advertising or cross-site profiling, so we do not ask you to accept an optional-cookie banner.
Third-party services
When you choose to pay, you leave Lightning TV for Stripe’s hosted checkout. Stripe may use its own cookies or similar technologies for payment, fraud prevention and service operation under its own notices. When you play or cast a broadcast, your device connects to the configured streaming and casting providers, such as Amazon IVS or Google Cast. Those providers may receive technical connection information needed to deliver the feature.
Google Cast and AirPlay media use short-lived same-origin relay links. These links carry random receiver authorization and opaque media references; they do not set an additional receiver cookie or reveal the protected upstream playback address. The controller still uses the strictly necessary session and playback identifiers above to request the handoff.
Draft, subject to legal and organisational approval. The /tv sign-in fallback uses the existing strictly necessary session cookie to bind a TV's code to that browser. The phone retains its own account sign-in. After approval, the TV session holds access to one selected broadcast and expires after six hours by default; it does not become a full account or staff login. Blocking session cookies prevents TV pairing. Use Disconnect on a shared TV or clear that browser's site data when finished. The QR image is generated on this site and is not sent to an external QR service. Normal protected-playback device and tab identifiers are also used for TV video.
Following an external link may also allow that separate site to set its own cookies. We do not control another organisation’s storage technologies.
Optional cookies
Lightning TV pages do not currently set advertising or optional analytics cookies. If that changes, we will update this notice and provide a clear choice before setting a technology that requires consent. Refusing an optional technology will not block the core service.
Your controls
Draft, subject to legal and organisational approval. Protected playback may register an Amazon IVS service worker on this site. Blocking service workers can prevent video from starting on browsers that need this component. Clearing site data removes its registration; visiting a stream again may register it again.
You can delete or block cookies and site data through your browser settings. Blocking mkltv_beta_session or mkltv_beta_csrf will prevent sign-in, checkout or protected account actions from working. Clearing the playback identifiers may make this browser appear to be a new device and may require you to restart or take back the viewing session.
An authorised technical-preview launch also uses the first-party session cookie to bind a time-limited, view-only preview to the browser that consumes its single-use link. It does not sign that browser in as the staff member who created the preview.
Browser “do not track” settings do not change these strictly necessary technologies. Because we do not use advertising or optional analytics cookies, there is currently no separate preference to withdraw on Lightning TV.
Changes and contact
We will update the version and date above when our use of cookies or browser storage changes. Email [email protected] if you have a question about this notice.
Draft, subject to legal and organisational approval. Redeeming a one-time goal judge code uses the existing first-party session cookie to remember the assigned fixture and rink end on that phone. This grants only goal judge controls, not a staff account or viewing pass. Phone access ends 24 hours after code issue or earlier when revoked or the fixture ends. Clearing the cookie requires a new code from match staff.
Coach report sign-in
Draft, subject to legal and organisational approval. Opening a coach report uses the necessary first-party session and form-protection cookies listed above. The server-side session remembers the approved fixture, password revision and expiry for up to twelve hours after coach sign-in; it does not store the coach password in your browser. Lock report removes that fixture's approval from the session. Staff changing or revoking the password invalidates existing approvals when the report next checks access. Coach reports add no advertising cookies or local-storage identifiers. Blocking the necessary cookies prevents password sign-in.
Commentator report sign-in
Draft, subject to legal and organisational approval. Commentator reports use the necessary first-party session and form-protection cookies described above. The server-side session holds a separate fixture approval, password revision and expiry for up to twelve hours after sign-in, without storing the password in the browser. Lock report removes that commentator approval. Coach approvals are separate. Staff password changes and revocation invalidate existing approvals when access is next checked. Pause updates keeps access checks running while holding the displayed figures. No report preferences are saved in local storage and no advertising cookies are added.
Draft, subject to legal and organisational approval. The commentator live connection uses the same necessary first-party session cookie as the report page. Live access checks reload the server-side fixture approval; reconnecting does not extend its expiry. View, search and filter selections use the page URL, and unfinished field text is held only in the current page during live refreshes. The report adds no browser-storage preference for these controls.