Cookie Policy. Small files, clearly explained.

1. What cookies are

Cookies are small text files stored by a browser. They can remember a preference, support a session or help a site understand broad usage. Kaltvel uses a limited approach and does not use cookies to ask readers for private health information. Technically, a cookie is a short piece of text that a website asks a browser to store and then send back on later visits, so the site can recognise a returning visitor without asking them to repeat the same choice each time. Cookies set directly by kaltvel.info are known as first-party cookies, while any cookie set by a service embedded on the page, such as a video player, would be described as a third-party cookie. Kaltvel currently does not embed third-party advertising or social media widgets that would set their own tracking cookies, and this page will be updated if that changes. In addition to cookies, some browsers support similar local storage technologies; Kaltvel's current implementation relies solely on the two cookie types described in this policy and does not use browser local storage, web beacons or device fingerprinting to identify returning readers. Where a future feature, such as an embedded video player, would introduce a third-party cookie, that change would be reflected in an updated version of this page before the feature is switched on for readers, consistent with the change-log approach described at the end of this policy.

• a) First-party cookies are set directly by kaltvel.info and are only readable by this site. They cannot be read or used by any other website a reader later visits.
• b) Kaltvel does not currently use third-party advertising cookies or cross-site tracking technology. No pixel, tag or tracking script from an advertising network is embedded on any page of the site at the time of this update.
• c) No cookie used by Kaltvel is designed to collect or infer information about a reader's health. The two cookies described in this policy relate solely to session handling and a banner preference, and neither is capable of identifying a reader by name.
• d) Where the word "cookie" is used elsewhere on the site, such as in the banner shown to first-time visitors, it refers to the same limited set of files described in this policy rather than to any broader tracking technology.

2. Essential session cookies

Essential cookies support security and basic page operation. They normally last for the browser session and are removed when the session ends. They cannot be switched off through the site without affecting expected functions. A session cookie of this kind might, for example, help the site remember that a form has already been submitted so it is not accidentally processed twice, or help maintain basic protection against automated abuse of the contact form. Because these cookies do not persist beyond the browsing session, closing the browser window is normally sufficient to remove them, and no separate action from the reader is required. Under the UK Privacy and Electronic Communications Regulations, strictly necessary cookies of this kind are exempt from the requirement to obtain prior consent, which is why they are not covered by the cookie banner choice described below. In practical terms, a reader who rejects cookies through the banner will still have these essential files set during their visit, because rejecting the optional preference cookie does not, and legally cannot, disable the strictly necessary functions the site depends on to operate securely. If a browser is configured to block all cookies at a system level, including session-only ones, some parts of the site, such as submitting the contact form, may not behave as expected, and the reader may see an error rather than a confirmation message.

• a) Typical lifespan: for the duration of the browsing session only. The cookie is deleted automatically when the browser is closed, rather than remaining on the device afterwards.
• b) Purpose: basic security, form handling and page functionality, including reducing the risk of automated spam submissions through the contact form.
• c) Consent status: exempt from consent under UK PECR as strictly necessary cookies, meaning no banner interaction is required before these files are set.
• d) Scope: limited to kaltvel.info; these cookies are never shared with, or made visible to, any third-party service.

3. Preference cookie

The cookieChoice value records whether a visitor accepted or rejected the banner. It may remain for 12 months unless the browser removes it earlier. It stores a simple choice rather than a name or contact detail. This cookie exists so that a returning reader is not shown the same banner on every single page load, which would otherwise interrupt the reading experience unnecessarily. The value stored is limited to a short marker indicating "accepted" or "rejected", and it is not linked to any other identifying information collected elsewhere on the site. A reader can change their earlier choice at any time by clearing their browser's site data for kaltvel.info, which will cause the banner to reappear on the next visit. Because the twelve-month lifespan is a maximum rather than a guarantee, browsers configured to clear cookies automatically on closing, or privacy-focused browser modes, may remove this cookie sooner, in which case the banner will simply reappear earlier than the full twelve months. The cookie is stored only on the device used to make the original choice; visiting the site from a different device or browser will show the banner again, since preference cookies are not synchronised across devices by Kaltvel.

• a) Cookie name: cookieChoice. This is the only preference-related cookie set by the site at the time of this update.
• b) Typical lifespan: up to 12 months, or until browser data is cleared, whichever happens first.
• c) Content stored: a simple accepted/rejected marker, with no personal identifiers, contact details or browsing history attached to it.
• d) Device scope: the choice applies only to the browser and device where it was made, and does not transfer automatically to other devices used by the same reader.

4. Analytics

If analytics is enabled in a future release, it will be optional and described here with its provider, purpose and lifespan. The present site does not require analytics for reading articles. Should an analytics service be introduced, it would only be activated after a reader actively accepts the cookie banner, consistent with the consent-based approach already described in this policy, and it would never be enabled by default. Any future analytics cookie would be named, and its approximate lifespan and purpose disclosed, in an updated version of this section rather than being added silently. Kaltvel's current editorial operation is designed to function without needing detailed visitor analytics, which is why no such service is active at the time of this update. Were an analytics provider to be introduced in future, Kaltvel would favour a privacy-conscious configuration, such as IP address truncation and a reasonable data retention limit agreed with the provider, and would identify that provider by name together with a link to its own privacy documentation. Readers are encouraged to check this section periodically, or review the change log below, to see whether an analytics tool has since been added.

5. Managing choices

You can remove cookies through browser settings and can revisit your choice by clearing site data. Blocking essential files may affect navigation or form behaviour. Most modern browsers allow a reader to view, delete or block cookies from a specific site through their privacy or security settings menu, and the exact steps differ slightly between Chrome, Firefox, Safari and Edge. If a reader blocks all cookies at the browser level, including essential ones, some features such as the contact form's abuse protection may not work as intended, though the reader will still be able to read published articles. Readers who want to start with a clean slate can clear all site data for kaltvel.info, which removes the preference cookie and causes the cookie banner to be shown again on the next visit. On most desktop browsers, this option is found under a menu such as "Privacy and security" followed by "Site settings" or "Cookies and site data", where a reader can search for kaltvel.info specifically and remove only the data associated with this site rather than clearing every site's cookies at once. Mobile browsers generally offer a similar, though sometimes more limited, set of controls under their own privacy settings menu, and a reader unfamiliar with these steps on their specific device is welcome to contact us for general guidance, though we cannot provide device-specific technical support beyond what is described in this policy.

6. Contact

Questions about cookies can be sent to [email protected] or posted to 33 Corn Street, Bristol BS1 4ER. We aim to reply to straightforward cookie-related questions within a reasonable time, generally within one calendar month in line with the response times described in our privacy policy. If a reader's question overlaps with a broader data protection request, such as asking what personal information is held about them, we will treat it under the rights described in our privacy policy as well as under this cookie policy. Readers who remain concerned after contacting us directly are free to raise the matter with the Information Commissioner's Office as the UK's independent supervisory authority for data protection matters. When writing to us by post, including a return contact detail such as an email address will help us respond more quickly than a postal reply alone would allow. For general cookie questions that do not involve a request to access, correct or delete personal data, we aim to respond within five working days where possible, reserving the fuller one-month statutory period for more complex data protection requests that require additional verification or investigation. This policy was last reviewed on 24 September 2026; any material change to the cookies described above, such as the introduction of an analytics tool, will be reflected in an updated version of this page with a new review date shown in the page header.