Privacy

No accounts

Silent Dossier is an anonymous-read, account-free site. Reading an article never requires creating an account, signing in, or providing your name, email address, or any other personal information.

Analytics

Silent Dossier uses Google Analytics 4 to understand aggregate audience trends -- for example, which articles are read, roughly which country or region readers come from, and how visitors move through the site. To do this, Google Analytics sets first-party cookies (such as _ga) in your browser and sends usage data to Google, which processes it on our behalf under Google’s own privacy terms. We use it only for aggregate audience measurement and to improve our coverage, and we never sell your data.

Readers in the European Union, the European Economic Area, the United Kingdom and Switzerland are asked first. Google Analytics loads, and sets its cookies, only after you choose Accept in the cookie notice; if you choose Reject, it does not load. Your choice is kept in your browser’s local storage, not in a cookie. You can change it at any time with Cookie settings at the foot of every page; rejecting also deletes the _ga cookies already set.

Advertising

Silent Dossier may display advertising served by third-party vendors, including Google. These vendors use cookies to serve ads based on your prior visits to this website or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet.

You may opt out of personalized advertising by visiting Google Ads Settings, or opt out of some third-party vendors’ use of cookies for personalized advertising at www.aboutads.info. Learn more in how Google uses information from sites that use its services. Advertising has no influence on editorial decisions.

What the site does apply

To keep the site available, requests are rate-limited by route class (for example, search requests are limited separately from ordinary reads); the limiter tracks only request counts within a short time window, not any per-visitor identity. Standard security response headers are applied to every response, including a strict Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and a Cross-Origin-Opener-Policy. Article, search, login, staff, preview, and API responses are non-cacheable. Public institutional pages may be stored only with mandatory revalidation, so a cache must confirm freshness before reuse. None of this involves collecting or storing personal data about a reader.