Cookies notice, in plain language.
One functional cookie for the mobile drawer state. No advertising, no analytics, no third-party sharing.
Cookies notice.
This publication sets a single functional cookie to remember the open/closed state of the mobile drawer across reloads. The cookie is not used for analytics, advertising or third-party data sharing.
The functional cookie
Name: purewin-drawer-state. Lifetime: 24 hours. Purpose: remember whether the mobile drawer is open between page reloads. No personal data is captured.
What the publication does not use
- No advertising trackers.
- No analytics cookies.
- No third-party sharing.
- No session replay or fingerprinting.
How to disable
Most browsers allow cookies to be disabled or cleared. Disabling this publication's single functional cookie means the mobile drawer state may not be remembered on reload, which is a small UX trade-off and no data impact.
The cookie notice is short because there is only one cookie.
The publication sets exactly one functional cookie. The cookie stores whether the mobile drawer was open at the last reload. The cookie expires in 24 hours. The cookie does not contain any personally identifying data. The cookie is not shared with any third party.
Disabling the cookie
Most browsers allow the reader to disable or delete cookies. Disabling this publication's single functional cookie means the mobile drawer state will not be remembered on reload; the reader will need to open the drawer manually on each visit. No data is lost; the trade-off is a small UX step.
Why a one-cookie notice is honest.
This publication does not track readers across the open web. It does not share data with third-party analytics services. It does not embed third-party advertising scripts. The one cookie it does set is a functional cookie for the mobile drawer state — it does not advertise, it does not profile, it does not aggregate.
Cookie hygiene in practice
The single cookie is set at the moment the reader interacts with the mobile drawer. It expires after 24 hours. It does not contain any personally identifying data. It does not identify the reader across multiple visits; it identifies only the last-known state of the mobile drawer.
Where third-party cookies might appear
The publication does not embed third-party cookies. The fonts referenced from fonts.googleapis.com and fonts.gstatic.com may set their own cookies for their own purposes; those cookies are outside the publication's control. The reader who wants to disable third-party cookies should consult the browser's privacy settings.
What the browser's privacy settings do.
Modern browsers offer privacy settings that block cookies, limit third-party cookies and clear cookies on close. The reader who wants to disable all cookies should consult the browser's privacy settings. The reader who wants to allow only the publication's single functional cookie should add an exception for the publication's domain.
What to expect when you block cookies
The publication's content does not require cookies to render. The cookie only affects the mobile drawer state: without the cookie, the drawer will be in its default state (closed) at each new session. The reader's reading experience is otherwise identical.
What to expect when you clear cookies
Clearing cookies resets the mobile drawer state to its default. The reader's reading experience is otherwise identical. The publication does not store any reader-identifiable state in cookies; clearing the cookies only resets the drawer state.
A note on browser fingerprinting.
Browser fingerprinting is a technique used by some tracking scripts to identify the reader across visits without cookies. Fingerprinting combines browser properties (user agent, fonts, screen size) into a near-unique signature. The publication does not use fingerprinting.
The publication does not embed third-party scripts that fingerprint. The fonts referenced from Google's font service do not fingerprint. The reader who wants to disable fingerprinting should consult the browser's privacy settings; some browsers offer a "resist fingerprinting" option.
What this publication does not do
The publication does not share data with any third party. The publication does not aggregate reader behaviour into long-form profiles. The publication does not sell, rent or trade reader data.
What the reader can do
The reader can use a privacy-focused browser, install a script blocker, disable third-party cookies in the browser's settings, or use the browser's "private window" feature. None of these will affect the publication's reading experience beyond the mobile drawer state.
What is loaded from third parties.
The publication references fonts from fonts.googleapis.com (the Google Fonts service) and from fonts.gstatic.com (the Google Fonts stylesheet host). These third-party services may set their own cookies for their own purposes; the publication does not control those cookies and does not include them in the publication's cookie notice.
The reader who wants to disable the third-party cookies should consult the browser's privacy settings. The cookies from the font service are typically used for performance and analytics; the reader can block them without affecting the publication's reading experience.
What the publication does not load
The publication does not load third-party advertising scripts. The publication does not load third-party analytics scripts. The publication does not load social media widgets. The publication does not embed third-party video players.
What this publication does
The publication loads its own CSS and JS from its own domain. The publication loads fonts from Google's font service. The publication does not load any other third-party resources.