A short and literal privacy note
Meridian is built to be read without an account, a cookie banner, or a visitor profile.
What we store
The publication does not operate a database of readers, visitors, or fingerprints. There are no reader accounts, no marketing cookies, and no personal archives. The only editorial content kept by the service is the current edition and the preceding few hours, held in memory so that pages remain available across an hourly change.
The site also sets a few static platform cookies so that the installation looks ordinary to automated scanners. Those values are identical for every request, contain no request data, and cannot be used to recognise or track a reader.
Server logs
The web server produces short-lived operational logs for availability, security, and debugging. These logs are emitted to the runtime environment and are not used to build advertising profiles. Standard request metadata, including the requested path and a user-agent string, may be present in those logs.
Security and fraud prevention
When a security script is enabled, it collects technical signals about the browser session and connection and sends them to the visitor-event endpoint on this site. Those event bodies are stored in daily JSON files for fraud-prevention testing and are not used to personalise editorial content. The script does not set advertising cookies.
Forms
The contact form deliberately does not persist its submission. Messages are not written to a database, mailing list, or customer record. The form exists so that automated and human traffic can be distinguished during security testing.
Changes
This note describes the current configuration of the service. If the deployment changes, the note should be updated with it. Questions can be sent to the editorial desk.