Privacy notice, in plain language.
What this editorial publication collects and what it does not. Server logs kept for 30 days; no advertising trackers; no third-party data sharing.
Privacy notice.
This publication does not collect personal data from readers beyond what is necessary to operate the website. The notice below describes what is collected, what is not, and how long records are kept. The publication does not run advertising trackers and does not pass reader data to third parties.
What is collected
Standard server logs: IP address, browser type and requested URL. The logs are kept for 30 days for security and capacity planning. After 30 days, the logs are deleted.
What is not collected
The publication does not use third-party advertising trackers. It does not set tracking cookies. It does not collect contact details without the reader's explicit action (a corrections email, for example).
Cookies
The publication sets a single functional cookie to remember the open/closed state of the mobile drawer. The cookie is not used for analytics or advertising.
Disclosure
Editorial disclosure is described on the disclosure page.
Contact
Privacy questions: [email protected]. Response within 5 working days.
Read this notice the same way you'd read a magazine.
This publication is not in the business of tracking readers. We do not set advertising cookies. We do not share data with third-party trackers. We do not run an analytics service that follows readers across the open web. We do not aggregate readership data for sale to marketing networks.
What we do
We keep standard server logs (IP, browser, requested URL) for 30 days for security and capacity planning. We set one functional cookie for the mobile drawer state. We log inbound referrals with no personally identifying payload. We retain these logs only as long as the audit-and-capacity window requires.
Why this is short
The notice is short because what we collect is short. A long privacy notice would describe a long list of collected data points; we collect a short list, so the notice is short.
What the notice covers, end to end.
The privacy notice covers the data this publication collects, the data it does not, the retention timeline, the cookies it uses, the disclosure it relies on and the contact channel for privacy questions. The notice is written in plain English so a reader without a privacy background can read it once and understand the data posture.
Data collected
This publication collects standard server logs: the IP address of the request, the browser type making the request and the URL requested. The logs are kept for 30 days for security and capacity planning; after 30 days, the logs are deleted. The logs are not aggregated across readers; each log line is a separate entry that expires independently.
Data not collected
The publication does not use third-party advertising trackers. It does not set tracking cookies. It does not collect contact details without the reader's explicit action. It does not aggregate reader behaviour into long-form profiles. It does not share reader data with any third party other than the server operator (which only retains the logs as described above).
Cookies
The publication sets one functional cookie: purewin-drawer-state. The cookie remembers whether the mobile drawer is open or closed between page reloads. The cookie has a 24-hour lifetime. The cookie does not contain any personally identifying data and is not shared with any third party.
Disclosure
The publication includes a disclosed first-party route to a separately-operated platform. The route is described in the disclosure page; the relationship is editorial, not commercial beyond the disclosed fee. The route uses standard link-click analytics on the platform side, not on the publication side; the publication does not see which readers click through.
Data subject rights
A reader can request a copy of any data the publication holds about them. The publication holds server logs which are anonymous per request; the publication cannot tie the logs to a specific reader's identity without the cooperation of the reader's network. A reader who wants the logs checked can send a privacy email to the contact below; the publication will respond within 5 working days.
Contact
Privacy questions: [email protected]. Response within 5 working days.
A short note on the contact channel.
Privacy questions are sent to the editorial email at [email protected]. The desk confirms receipt within 24 hours. The desk reviews the question against the publication's data posture. The desk responds within 5 working days with a description of what data the publication collects, what it does not and how the question applies.
What the desk does not have access to
The desk does not have access to per-reader logs; the standard server logs are anonymous per request and expire 30 days after collection. The desk does not have access to cookie data beyond the single functional cookie. The desk does not have access to any reader's interaction history because no such history is collected.
What the desk will tell you
The desk will tell you which public sources the publication cites for the affected content. The desk will tell you what data the publication collects. The desk will tell you how long the data is retained and how to request deletion. The desk will not provide data the publication does not hold, because the publication does not hold it.
This is the answer most privacy questions receive. A short answer is a sign that the publication's data posture is short, not a sign of evasion.