Cookie policy and choices

Provisional documents for review. The company details are provisional. These documents do not create a binding contract. Fields awaiting confirmation remain marked.

Version review-2026-09-16-v0.2 · Published 15/09/2026 · No contractual effective date

Current website storage

Secure Supabase sign-in cookies support account access. The rtl_application cookie lasts one hour after application verification. Optional invitation statistics use rtl-invitation-visit for up to 30 minutes only after the choice above. Teaching drafts use session storage in the current tab; programme selection uses local storage until cleared. You can remove these through your browser controls. This site does not add advertising trackers.

The longer policy below is proposed wording. Its inventory must be completed before it becomes a final policy.

L09: Privacy Policies, Cookie Policy and Data Schedules

L09-C. Cookie Policy

1. What this covers

RTL Clubs uses this policy to explain cookies and similar technologies on its website and app, including local storage, pixels, device identifiers and software development kits where used. These technologies can store or read information on a device. The Privacy Policy explains related personal-data use. Contact help@rtlclubs.com about either policy.

2. Necessary and optional uses

Strictly necessary technologies may operate without consent when needed to provide a service you request, for example maintaining a secure sign-in where the actual technology meets the legal exception. Optional technologies that need consent must remain off until you choose them. We will not treat scrolling, continuing to browse or accepting programme terms as cookie consent.

Our proposed default is to ask before optional analytics or advertising technology runs. Some limited uses may qualify for a statutory exception, but only after their actual purpose and conditions have been checked. Where an applicable exception requires a simple way to object, we will provide it and honour the choice. A technology used for several purposes cannot rely on an exception for an unrelated purpose.

3. Your choices

Open your browser settings (no optional analytics or advertising enabled by RTL) to accept optional uses, reject them or change your choices. The intended first-layer controls are "Accept optional cookies", "Reject optional cookies" and "Choose settings", with equally clear access to rejection. Optional categories start off. Refusing optional uses will not prevent the core learning service. Withdrawal is as easy as giving consent and stops future consent-based storage or access; it does not undo earlier lawful processing. Browser controls can also remove stored items but may affect sign-in. App device permissions are separate and do not replace consent where required.

4. Technology list

Before publication complete and verify this inventory for web, app, embedded content and logged-in and logged-out states. Remove technologies not actually used. No fictional cookie names, suppliers or lifetimes are supplied by this draft.

Name/identifier	Provider	Web/app and first/third party	Exact purpose and data	Category and consent/exception	Duration	Recipients/transfers	How to refuse/withdraw
[AUDITED ITEM]	[PROVIDER]	[SURFACE]	[PURPOSE/DATA]	[BASIS]	[VERIFIED DURATION]	[DETAILS]	[CONTROL]

Consent-choice record retention and identifier: [APPROVE PROPORTIONATE DESIGN]. Linked external sites have their own policies. Embedded services must be assessed before loading, not merely linked to an external notice. We will update this list when use changes and obtain fresh consent for materially new consent-based purposes. These are draft operating commitments; verify the controls before publishing them as live behaviour.