1. What cookies do
Cookies are small files or browser records used to remember preferences and support website functions. Krenvel uses a restrained approach because the platform is editorial rather than a shop.
For example, a typical retail website might use dozens of cookies to track baskets, personalised recommendations and advertising, whereas krenvel.info uses only a small number of records because there is no checkout, account system or product catalogue to support. In practice, this means most visitors will encounter just one meaningful storage item, described in section 2, plus a short-lived technical identifier described in section 3. An edge case worth noting is that "cookie" is used here as shorthand for any similar browser storage technology, including local storage values, since modern browsers increasingly use these interchangeably for the same purpose of remembering a choice between visits. Under the Privacy and Electronic Communications Regulations (PECR), as enforced in the UK by the Information Commissioner's Office, only cookies that are strictly necessary may be set without prior consent, and Krenvel's approach is designed to stay within that strictly necessary category wherever possible. A further consequence is that this policy is reviewed alongside the site's privacy policy so that the two documents remain consistent with one another, since cookie use and general data handling are closely related topics under UK GDPR and PECR. Where a future feature would require a cookie outside the strictly necessary category, such as a preference toggle for article font size, that cookie would be added to section 4 and would only activate after a visitor's affirmative consent through the banner described in section 5. This restrained approach also means krenvel.info does not currently use any cross-site tracking pixels, social media embed cookies or third-party advertising identifiers of any kind.
- (a) This policy is reviewed alongside the privacy policy to keep both documents consistent with UK GDPR and PECR requirements.
- (b) Any future non-essential cookie, such as a display preference, would be added to section 4 and gated behind affirmative consent.
- (c) No cross-site tracking pixels, social embed cookies or third-party advertising identifiers are currently used on this site.
2. Essential storage
The cookieChoice local browser value records whether a visitor selected Accept All or Reject. It is used to prevent the consent prompt returning on every page. It remains until cleared by the visitor.
For example, a first-time visitor who clicks Accept All will have cookieChoice set to a value such as "accepted", and on their next page view within the same browser the banner will not reappear because that stored value is checked first. In practice, choosing Reject still stores a cookieChoice value, just set to "rejected" instead, because the site still needs to remember that a choice was made in order to avoid repeatedly interrupting the reader with the same prompt. An edge case is browsing in a private or incognito window, where browser storage is typically cleared automatically when the window is closed, meaning the banner will appear again the next time a private session is started, even for a returning visitor. Because this value is strictly necessary to operate the consent mechanism itself, it is set regardless of the choice made and does not require separate consent under PECR guidance from the ICO. A related practical detail is that cookieChoice stores only the decision itself, such as "accepted" or "rejected", and no other information about the visitor, meaning it cannot be used to identify a specific person or link their visits together across different devices. Clearing browser storage for krenvel.info, whether manually or through a browser's "clear browsing data" function, removes cookieChoice immediately and causes the consent banner to reappear on the next page load, exactly as if the site were being visited for the first time. An edge case is a visitor using multiple browsers or devices, such as a phone and a laptop; because cookieChoice is stored locally per browser, the decision made on one device does not transfer to another, so the banner may appear separately on each.
- (a) cookieChoice stores only the accepted/rejected decision and no personally identifying information.
- (b) Manually clearing browsing data for krenvel.info removes cookieChoice and causes the banner to reappear on the next visit.
- (c) The decision is stored per browser and per device, so it does not automatically transfer between a visitor's phone, tablet or computer.
| Name | Purpose | Lifespan |
|---|---|---|
| cookieChoice | Remembers the Accept All / Reject decision | Until cleared by the visitor |
3. Session technology
Hosting infrastructure may use short-lived session identifiers for security and delivery. These normally expire when the browsing session ends or within 24 hours.
For example, when a visitor loads a page on krenvel.info, the hosting platform may briefly assign a technical session identifier to help route the request correctly and detect unusual traffic patterns that could indicate misuse. In practice, this identifier is not linked to a reader's name, email address or newsletter subscription, and it is not used to build a profile of browsing behaviour across visits. An edge case is a visitor who keeps a browser tab open for an extended period; in that scenario, the identifier may expire and be silently reissued in the background without any visible change to the reader's experience of the site. These identifiers fall within the strictly necessary category under PECR because the website could not be delivered securely without some form of short-lived session handling at the infrastructure level. A practical consequence is that these identifiers are managed by Krenvel's hosting provider as part of standard web delivery infrastructure and are not accessible to, or used by, the Krenvel editorial team for any analytics, marketing or profiling purpose. An edge case is a visitor connecting through a shared network, such as public Wi-Fi in a café; the session identifier issued in that scenario is still tied to the individual browser session rather than the shared network address, so it does not link separate visitors on the same network together. These records are kept only for the short window described in the table below and are not retained afterwards for any secondary purpose such as traffic analysis or audience measurement.
- (a) Hosting-level session identifiers are managed by the infrastructure provider and are not used by the Krenvel editorial team for analytics or marketing.
- (b) A session identifier is tied to an individual browser session, not to a shared network address, even on public or shared Wi-Fi.
- (c) These identifiers are not retained beyond the stated lifespan for any secondary analytical purpose.
| Name | Purpose | Lifespan |
|---|---|---|
| Session identifier (hosting-level) | Security and page delivery | End of session, or up to 24 hours |
4. Optional measurement
If measurement tools are introduced, they will be enabled only after consent and described here by name, purpose and lifespan. At present the site does not require advertising cookies.
For example, if Krenvel later adopts a privacy-focused analytics tool to understand which articles are most read, that tool would be listed in this table with its exact cookie name, the data it collects and how long each record is kept, and it would only load after a visitor clicks Accept All. In practice, choosing Reject would mean that optional measurement tool never loads at all for that visitor, and only the essential items in sections 2 and 3 would remain active. An edge case is a visitor who accepts cookies and later changes their mind; in that situation, clearing the cookieChoice value or using the cookie settings link in the banner will stop future optional cookies from loading, though any measurement events already recorded before the change cannot be retroactively un-recorded. Krenvel does not currently use any advertising, retargeting or cross-site tracking cookies, and no such technology will be introduced without a corresponding update to this section. A further practical point is that any measurement tool considered for future use would be assessed for compatibility with UK GDPR and PECR before deployment, favouring providers that offer data minimisation options such as IP address truncation or cookieless measurement modes where available. Should such a tool be adopted, the retention period for any collected data would be stated explicitly in this section and would typically not exceed twenty-six months, consistent with common analytics retention practice referenced by the ICO. The consent choice recorded through cookieChoice would continue to govern whether any such optional tool is permitted to load for a given visitor.
- (a) Any future measurement tool would be assessed for UK GDPR and PECR compatibility, favouring data-minimising configurations where available.
- (b) Retention for any future analytics data would typically not exceed twenty-six months and would be stated explicitly in this section.
- (c) The existing cookieChoice consent record would continue to determine whether any future optional tool is permitted to load.
5. Browser controls
Most browsers allow cookies to be blocked or removed. Blocking essential storage may mean the banner appears again, but the editorial pages remain available.
For example, in most desktop browsers, cookie controls can be found under the privacy or security settings menu, where a visitor can view, delete or block cookies from specific sites including krenvel.info. In practice, blocking or deleting the cookieChoice value simply resets the consent decision, so the banner will reappear on the next visit and ask the reader to choose again; it does not prevent access to any article or page on the site. An edge case is a browser configured to block all storage by default, including strictly necessary cookies; in that case the consent banner may appear on every single page load, which can be mildly inconvenient but does not stop the underlying editorial content from being read. Browser extensions and built-in tracking protection features, such as those found in many modern browsers, can also be used by readers who want an additional layer of control beyond the choices offered directly on krenvel.info. A further consequence is that some browsers offer a "do not track" signal or similar global privacy setting; Krenvel does not currently have automated systems that read and respond to that signal directly, since the site's own cookie banner already provides an equivalent choice for the small number of records it uses. An edge case is a visitor using a browser profile shared with other household members; because cookieChoice and the session identifier are stored at the browser-profile level rather than per individual person, a decision made by one user of a shared profile will apply to anyone else using that same profile until it is changed or cleared. Readers who want a completely clean state can use their browser's private or incognito mode, which typically discards all site storage, including cookieChoice, once the private window is closed.
- (a) Krenvel's cookie banner is intended as the primary consent mechanism and does not currently process browser-level "do not track" signals separately.
- (b) Cookie storage applies at the browser-profile level, so a shared household profile will reflect one shared consent decision.
- (c) Private or incognito browsing typically clears all site storage, including cookieChoice, once the session window is closed.
6. Contact and changes
Questions can be sent to [email protected]. This policy was reviewed on 24 September 2026 and may be updated when the site changes.
For example, a reader wanting to know exactly what cookieChoice currently stores in their own browser can ask via [email protected], and we can explain how to inspect that value using their browser's developer tools. In practice, we aim to respond to cookie-related questions within five working days, consistent with the response approach described in the privacy policy. An edge case is a change to hosting provider or infrastructure that alters the technical session identifier described in section 3; such a change would be reflected here with an updated review date even if the practical effect on readers is minimal. Any future introduction of an optional measurement or analytics cookie will trigger a dated update to this page, listing the new item in the table in section 4 before it is switched on for any visitor. A further practical point is that material changes to this policy, such as the introduction of a new cookie category, will also be reflected in the change references maintained on the privacy policy page, so readers checking either document will see a consistent, dated account of what has changed. Where a query raised at [email protected] cannot be resolved within the initial five working days, for example because it requires checking historical technical records, we will send an interim response confirming receipt and a revised expected timeframe, generally no longer than a further ten working days. Readers who remain unsatisfied with how a cookie-related query has been handled retain the right to raise the matter with the Information Commissioner's Office as the UK's independent supervisory authority for data protection and electronic communications matters.
- (a) Material changes to this policy are reflected consistently in the dated change references maintained alongside the privacy policy.
- (b) Complex queries that cannot be resolved within five working days receive an interim response and a revised timeframe, typically within a further ten working days.
- (c) Readers unsatisfied with the handling of a cookie-related query may raise the matter with the Information Commissioner's Office.