Cookies Policy
Cookies, browser local storage and payment-service technology on Red Half Lab, with the current inventory and your choices.
Draft last checked:
1. Who we are and what this policy covers
This Cookies Policy is provided by Pumpkin Active LTD, 27 Old Gloucester Street, London WC1N 3AX, England, for redhalflab.com. Questions and requests can be sent to contact@redhalflab.com. Read this together with our Privacy Policy and Terms of use.
Review draft, updated on 24 October 2026. This policy describes the reviewed website code and identifies the production checks still required. It does not claim that a cookie scan of the final domain, hosting service or live Stripe checkout has been completed. The service is intended for adults aged 18 or over in the UK, US and EU.
2. Cookies and similar technologies
A cookie is a small record that a website or service can store in your browser and send with later requests under the cookie’s rules. Session and persistent cookies can have different lifetimes. Local storage is a separate browser mechanism that can retain an entry between visits; it is not automatically sent with every HTTP request like a cookie.
Both cookies and local storage can hold information that identifies someone or can be connected to other information. Rules about storing or accessing information on a device can apply even when an entry does not contain a person’s name. Calling something “functional” or “local” does not, by itself, decide whether consent is needed.
First-party technology is associated with the site you are visiting. A third-party service, such as a hosted payment service, can operate its own storage. A statement about our own code cannot establish every third party’s live settings.
3. The current first-party inventory
The reviewed visitor-facing site code explicitly uses the following persistent browser storage:
| Item and provider | Purpose and contents | Lifetime and control |
|---|---|---|
ask-reds-play-v2-* — Red Half Lab, first-party local storage |
Remembers the selected match-challenge answers, the current question and which answers were revealed. The suffix identifies the relevant challenge. | No expiry is set by the code. Remains until removed by you or the browser. Clear this site’s local storage to remove it. |
An older match-specific entry with the same prefix can still be read for compatibility, and is not automatically removed when a new fixture arrives. The information is read by the challenge code in that browser. The current saving mechanism does not upload those saved choices to an account server or synchronise them between devices.
The reviewed page code does not explicitly set a sign-in cookie, a language-preference cookie, an advertising identifier or a third-party audience-analytics cookie. The current site has no account sign-in. English and Chinese are selected through their page URLs rather than a stored language-preference cookie in the reviewed implementation.
This is an inventory of identified application behaviour, not an assurance that a host, proxy, development environment or payment service never adds a cookie. Production response headers and browser storage still need checking.
4. What is optional and what must be assessed
Remembering challenge progress is a functionality purpose. Reading articles and browsing REDS answers does not depend on storing a challenge selection. If your browser blocks this storage, the challenge can work during the current visit but saved progress may not survive a reload.
We do not assume this persistence is exempt from consent merely because it is useful. The required assessment depends on the actual purpose, whether the user has requested that function and the applicable UK or EU storage rules. Where prior consent is required, it must be obtained before the relevant access or storage, and withdrawal must be available as required.
The current interface does not provide a dedicated cookie-preference dialog or an implemented consent-recording system. This document does not substitute for one. The production release check must settle the applicable exception or implement the necessary consent and control before enabling any use that requires it. No analytics or advertising integration is introduced by this policy.
5. Stripe and optional payment checkout
Selecting support asks this site’s server to create a Stripe Checkout session. The current site sends you to Stripe’s hosted checkout rather than embedding a card form or adding Stripe’s browser payment library to every content page.
Stripe’s checkout and related payment functions may use cookies or similar technologies for payment, fraud prevention, authentication and other purposes described in Stripe’s own notices. Their actual names, domains, durations and available choices depend on the payment flow and configuration. We have not verified those values for the live merchant account and do not present example cookie names as cookies proven to be installed on this site.
Read Stripe’s Cookie Policy and Privacy Policy. Any choices presented by Stripe apply to its service; they are not an implemented Red Half Lab cookie-settings panel. You can browse our content without initiating payment.
The checkout-session identifier in the return URL is a transaction reference, not a first-party challenge cookie. Keep it private. Removing cookies or local storage does not cancel a payment, refund it or erase Stripe’s transaction records.
6. Logs, URLs and information outside browser storage
Server logs and payment-request limits are different from cookies. The current checkout limiter keeps connection-address keys and request timestamps in server process memory. It counts activity over 60 seconds; there is no timed cleanup of all inactive keys. The 60-second window is not a cookie lifetime or a promise to delete an address after 60 seconds.
Search text is transmitted in a request URL parameter. Content identifiers can appear in the page URL and browser history. Clearing cookies alone may not clear browser history, server logs or payment references. See the Privacy Policy for the adopted server-side retention rule and the remaining configuration checks.
7. Advertising, analytics, embeds and preferences
The reviewed site code includes no advertising integration, third-party audience-analytics system, cross-site advertising tracker or visitor-fingerprinting feature. The other project operated by the company has its own configuration; its references to Google Analytics, remarketing or account cookies are not imported as facts about Red Half Lab.
Following an external link takes you to another service’s practices. A social link does not by itself establish that we have embedded that provider’s tracking widget. If new analytics, advertising or embedded services are added, we must assess them, update the inventory and provide the choices or consent required before the new use starts.
8. How to inspect, block or remove stored information
Use your browser’s controls for site permissions, cookies and stored site data. Locate redhalflab.com, select the relevant stored data and remove it. If you use the local preview on another host or port, that preview has its own browser-storage origin and must be cleared separately.
For the challenge entries, deleting only cookies may be insufficient: select local storage or all stored site data as appropriate. Developer tools can also show entries starting with ask-reds-play-v2- for removal. The browser’s normal settings are sufficient; using developer tools is not required.
Official browser instructions are available for Chrome, Microsoft Edge, Firefox and Safari. Menu names and the effect of private browsing can vary by browser and version.
You can block storage using those browser controls, but a setting that blocks cookies does not necessarily block all local storage. Consult the control’s actual description. Saved progress will be lost when its entry is removed; clearing one browser does not clear another device. Removing stored data does not prevent the site from storing a new entry on a later interaction if that storage remains enabled.
9. Do Not Track, Global Privacy Control and requests
The current site does not claim a technical integration that records Do Not Track or Global Privacy Control signals. The reviewed code also does not operate a data-selling, cross-context advertising or targeted-advertising programme. Those facts are distinct: the absence of a tracker is not a claim that every privacy signal has been implemented.
If an applicable US law gives you an opt-out or signal-based right, it remains applicable. You can email contact@redhalflab.com with an opt-out or privacy request. Before introducing covered advertising or sale/sharing activities, the relevant signal and choice handling must be assessed and implemented as required.
10. Production checks and changes
Before final publication, verify the actual domain and subdomains, hosting and proxy response headers, all storage names and purposes, third-party recipients and locations, retention settings, and any required consent controls. A professional template from another site supplies a framework, not a completed scan of this site’s deployment.
We will revise this policy and its date when the storage inventory or use changes materially. An update or continued browsing is not blanket consent to optional technologies. Requests and complaints use the contact details in section 1; personal-information rights are explained in the Privacy Policy.
The English version of this Cookies Policy is authoritative; the Chinese version is a translation. The effective date will be set at public launch. The revision date above does not announce launch.