29 October 2026. This document is a working structure and is not final, pending the operator’s own terms or a lawyer’s adaptation.
Cookie Categories at a Glance
1.1 The following table outlines the classifications of cookies deployed across the platform and the operational consequences of restricting them.
| Category | What it does | Can you switch it off | What breaks if you do |
|---|---|---|---|
| Strictly necessary | Enables core platform operation, account authentication, and security. | No | Sign-in fails and active sessions are terminated. |
| Functional | Remembers user preferences such as layout and currency choice. | Yes | Resets currency choice and catalogue filters to default. |
| Analytics | Measures visitor traffic and interaction with platform features. | Yes | Changes nothing a visitor can see. |
| Advertising | Tracks browsing activity to deliver targeted promotional material. | Yes | Changes nothing a visitor can see. |
1.2 The platform employs cookies and similar tracking technologies to facilitate the operation of the website, ensure security during the login process, and collect information regarding user interaction. 1.3 This document serves to explain the categorisation of these technologies, the specific purposes they fulfil, and the rights afforded to users concerning their deployment, in accordance with the Privacy and Electronic Communications Regulations (PECR) and guidance issued by the Information Commissioner’s Office (ICO). 1.4 A cookie constitutes a small text file downloaded to a user’s device upon accessing the platform. 1.5 The data retrieved through these files may pertain to the user, the device utilised, or specific preferences established during previous visits. 1.6 While strictly necessary cookies are deployed automatically to ensure the fundamental provision of requested services, all other categories require explicit, prior consent before they are written to a device. 1.7 The refusal of functional, analytical, or advertising cookies shall not prevent the user from accessing the platform, though it may require the manual re-entry of preferences during subsequent visits. 1.8 Users maintain the right to review and modify their consent preferences at any time, without detriment to their account standing or the general provision of services. 1.9 The classification system adopted herein reflects industry standards for data transparency, ensuring that users are presented with clear, unambiguous choices regarding the processing of non-essential tracking data. 1.10 The deployment of strictly necessary cookies relies upon the exemption provided within PECR, which permits the storage of information where it is strictly necessary for the provision of an information society service requested by the subscriber or user. 1.11 The deployment of all other categories relies exclusively upon the user’s provision of active, informed consent. 1.12 The Information Commissioner’s Office (ICO) acts as the supervisory authority governing these electronic communications and the associated processing of user data.
The Cookies on This Site
2.1 The platform maintains a detailed inventory of all cookies currently deployed, categorised by their specific function, origin, and retention period. 2.2 This inventory is subject to regular audits to ensure continued compliance with data protection requirements and to guarantee that no unapproved tracking technologies are introduced to the platform environment. 2.3 The table below represents a structural placeholder detailing the required format for the final cookie inventory, which shall be reconciled against the live production environment prior to final implementation. 2.4 Each entry within the finalised inventory must specify the exact technical name of the cookie, the overarching category to which it belongs, the specific operational purpose it serves, the duration for which it remains active on the user’s device, and the entity responsible for setting it.
| Cookie name | Category | Purpose | Lifetime | Who sets it |
|---|---|---|---|---|
| Strictly necessary | This site | |||
| Functional | This site | |||
| Analytics | Third-party service | |||
| Advertising | Third-party service |
2.5 Cookies set directly by the platform are designated as first-party cookies, whereas those deployed by approved service providers are designated as third-party cookies. 2.6 The retention periods, or lifetimes, of these files vary fundamentally based on their operational necessity. 2.7 Session cookies are designed to expire and be automatically deleted the moment the user closes their browser interface. 2.8 Persistent cookies, conversely, remain stored on the user’s device until they reach a predefined expiration date or are manually purged by the user. 2.9 The accurate disclosure of these lifetimes is a mandatory compliance requirement. 2.10 Any functional discrepancies identified between this published inventory and the active platform deployment shall be rectified promptly to maintain exact alignment with the user consent records. 2.11 The classification of a cookie purpose must be unambiguous. 2.12 Where a single cookie serves multiple purposes, it shall be classified according to its most intrusive function, and consent shall be obtained accordingly. 2.13 The platform strictly prohibits the use of analytics or advertising cookies disguised as strictly necessary operational files. 2.14 The inventory above shall serve as the definitive reference point for users seeking to understand the exact technical footprint left upon their devices.
Managing Your Choices
3.1 Users possess full control over the deployment of non-essential cookies and may exercise this control through multiple distinct mechanisms. 3.2 The primary mechanism for managing these preferences is the consent management interface provided directly on the platform. 3.3 Upon their initial visit, users are presented with a consent dialog allowing them to accept all cookies, reject all non-essential cookies, or configure granular preferences by specific category. 3.4 These selections can be modified at any subsequent time by accessing the cookie preference centre linked within the platform’s footer. 3.5 In addition to the platform’s own consent management tools, users may restrict or delete cookies through the configuration settings of their chosen web browser. 3.6 In Google Chrome, users must navigate to ‘Settings’, select ‘Privacy and security’, and access the ‘Cookies and other site data’ menu to clear existing files or block future deployments. 3.7 In Apple Safari, these controls are located within ‘Preferences’ under the ‘Privacy’ tab, where users may select ‘Prevent cross-site tracking’ or ‘Block all cookies’. 3.8 Mozilla Firefox users can manage these files by navigating to ‘Settings’, selecting ‘Privacy & Security’, and adjusting the parameters within the ‘Enhanced Tracking Protection’ section. 3.9 It is a critical distinction that deleting cookies via browser settings and withdrawing consent via the platform interface are separate operational actions. 3.10 Deleting cookies within a browser environment removes the physical files from that specific device but does not automatically withdraw the consent preference previously recorded on the platform’s service side. 3.11 Conversely, withdrawing consent through the platform’s interface ceases the future deployment of non-essential cookies from the service, but it does not proactively delete the historical cookie files already stored within the user’s browser. 3.12 To achieve a complete cessation of tracking and the removal of all associated files, the user must therefore both withdraw their consent through the platform interface and execute a manual deletion of existing cookies via their browser configuration settings. 3.13 The platform bears no responsibility for tracking files deployed by external websites that the user may visit independently. 3.14 Furthermore, it must be noted that configuring a browser to block all cookies, including strictly necessary categories, will severely impede the functionality of the platform. 3.15 Under such strict browser configurations, users will be unable to authenticate their accounts, maintain a logged-in state across different pages, or execute secure financial transactions. 3.16 For optimal platform performance while maintaining privacy, users are advised to manage non-essential tracking through the platform’s dedicated consent interface rather than relying on blanket browser-level restrictions.