Core cookies keep BritainPost working
Session and security technologies support website operation, protect forms and maintain requested functionality.
BritainPost uses a small number of cookies and similar technologies to keep the website secure, remember essential session information and provide features you request.
BritainPost is building the next generation of intelligent journalism—bringing together experienced editorial judgement, responsible artificial intelligence and transparent reporting to help readers understand the stories shaping Britain and the world.
Our current public implementation is designed around essential website functions rather than behavioural advertising or cross-site tracking.
Session and security technologies support website operation, protect forms and maintain requested functionality.
Security tokens help protect contact, newsletter and other forms against forged or unauthorised requests.
Limited Nia conversation turns may be associated with your session so follow-up questions can be understood.
BritainPost does not sell session or cookie data to advertising networks, data brokers or other traders.
The current inspected public implementation does not intentionally deploy Google Analytics, Meta Pixel or third-party behavioural advertising cookies.
If optional analytics or advertising technologies are introduced, this policy and any required controls will be updated.
Cookies are commonly stored by a browser when a website needs to remember information or support a particular function.
A cookie is a small text value stored on a computer, phone or other device. A website can later read that value to recognise a session, remember a setting or provide another function.
Cookies may be temporary and expire after a session, or remain for a defined period.
Privacy rules may also apply to other technologies that store information on, or access information from, a device.
These can include local storage, scripts, tags, tracking pixels, link identifiers and device recognition techniques.
The technologies described below support features that readers request or help protect BritainPost and its forms.
A session identifier allows the website to associate consecutive requests with the same temporary browsing session.
Security mechanisms help verify that a form request originated from the BritainPost website and reduce the risk of cross-site request forgery.
Limited reader and assistant conversation turns may be stored in the Laravel session so Nia can understand a dependent follow-up question.
Session and request information may help apply rate limits, diagnose faults, prevent misuse and protect BritainPost infrastructure.
Exact names and expiry periods may vary according to deployment and browser behaviour.
Used to maintain session state across requests and support features that depend on a temporary session.
Category: Essential
Typical duration: Session or configured
session lifetime
Used to help protect forms and state-changing requests against unauthorised cross-site submissions.
Category: Essential
Typical duration: Connected to the
relevant session or security lifecycle
Limited conversation context may be retained within session storage to support coherent follow-up questions.
Category: Requested functionality
Typical duration: Associated with the
browsing session
The exact session-cookie name can depend on application configuration. Browsers may also display framework or security-related names differently.
This policy describes the purpose of the technology rather than relying only on a technical name that may change.
BritainPost distinguishes essential technologies from optional technologies that may require a separate choice.
Technologies may be used without an optional consent choice where they are strictly necessary to provide a service requested by the reader or qualify for another applicable legal exception.
This can include security, session continuity and functionality required to process a form or provide a requested interactive feature.
Optional analytics, personalisation or advertising technologies may require prior consent or another appropriate mechanism before they are activated.
BritainPost will introduce suitable information and controls before intentionally enabling technology that requires them.
The current inspected public implementation does not contain common third-party analytics or advertising tracking integrations.
The inspected public implementation did not contain an active Google Analytics or Google Tag Manager integration.
Social sharing links may open external services, but the inspected implementation did not contain an active Meta Pixel integration.
BritainPost does not currently intend to place third-party behavioural advertising cookies through the inspected public website.
A third-party website may set its own cookies after you follow a link, use a sharing service, make a payment or interact with content controlled by that provider.
Those technologies are governed by the third party's own policies and controls.
Most browsers allow you to inspect, block or delete stored cookies and website data.
You can usually manage cookies through the privacy or security settings in your browser. The available controls depend on the browser and device.
You may also be able to remove website data for BritainPost without clearing data belonging to every website.
Blocking all cookies may prevent contact forms, newsletter subscriptions, Nia conversation context or other session-dependent functionality from working correctly.
Public articles may remain readable even where some interactive functions are unavailable.
Where information connected with a cookie or similar technology identifies or relates to a person, data-protection rules may also apply.
Information associated with sessions, requests, security events and Nia interactions is handled as described in the BritainPost Privacy Policy.
Session data is generally temporary, although limited technical or security records may remain in server logs or operational systems for an appropriate period.
Retention depends on security, service, diagnostic and legal requirements.
We may update this page when BritainPost introduces new features, providers or storage technologies.
Before activating optional technology that requires consent or an objection mechanism, BritainPost will seek to provide appropriate information and controls.
4 August 2026
Please review this page periodically for material changes.
We welcome questions about BritainPost's essential technologies and privacy practices.
Use the contact page and include “Cookie Policy” in the subject line.
Our newsroom is designed around editorial responsibility, transparency and technology that serves readers.
Editorial responsibility remains with people, including review of sensitive and high-risk reporting.
Technology supports research, organisation and reader understanding without replacing editorial judgement.
We aim to make sourcing, attribution and the basis of our reporting clear to readers.
Material errors should be corrected clearly, promptly and with appropriate accountability.
Images and media are selected through governed licensing, attribution and quality controls.
Reader features should be useful, respectful and designed with proportionate data collection.
Explore today’s reporting or ask Nia to explain the stories and signals shaping Britain.