Jump to any public page from mobile without losing the side-rail structure on desktop.
This page states the current reader-privacy posture plainly: public reading without mandatory accounts, no third-party trackers on the public site, and separate treatment for any sensitive intake route.
These pages exist to make the publication model legible instead of burying legal and trust information in a dark corner.
Public investigations and stories are designed to be read without creating an account or triggering a mandatory identity layer. That boundary matters because a publication about power and retaliation should not casually force readers or potential sources into extra data exposure.
The operations page says no analytics or third-party trackers are bundled into the public site. The goal is to let readers inspect reporting without silently becoming another behavioral dataset. That promise is part of the product, not a decorative policy sentence.
If public secure intake is enabled, the handling model belongs to that route and its underlying storage protections. If intake is paused, that page should say so plainly. The privacy promise here is therefore limited and explicit: public reading is separate from any future source-submission workflow.
If the site later adds saved pages, export presets, notifications, or a reader account layer, those changes should show up here and in the operations page with a visible review date. Privacy language that never changes while the product changes underneath it is not trustworthy.