Privacy

What this site does not do

• It sets no cookies and stores nothing in your browser.
• It runs no advertising or third-party analytics scripts and loads no social-media widgets. Small scripts served by us power interactive features and the anonymous reading-design comparison described below.
• It loads nothing from other companies. Fonts, styles and images are served from our own server, so reading a page here does not tell any third party that you did.

What is recorded

Like almost every web server, ours keeps an access log. Each request records the time, the address of the page, the IP address the request came from, the browser’s user-agent string and the referring page if the browser sends one. We use these logs to keep the site running, to stop abuse and to count how often pages are read. Log files are rotated daily and deleted after 14 days. We do not sell them, share them or combine them with other data.

The escalation alert list

If you sign up for escalation alerts, we store your email address, the time you signed up, which page you signed up from, and a one-way hash of your IP address (used only to rate-limit abuse; it cannot be turned back into your address). Nothing else.

• The list lives in a database on our own server. There is no third-party mail platform.
• We send through our own mail server. There is no tracking pixel and no click tracking, so we cannot tell whether you opened a message or followed a link, and we do not want to be able to.
• Nothing is sent until you confirm by clicking a link, so nobody can add your address but you.
• Unsubscribing deletes your row. We do not keep a suppression list of former subscribers.
• The list is never sold, rented, shared or handed to anyone.

Email

If you write to us, we keep your message for as long as we need it to deal with your request or to support our reporting. Read the contact page before sending anything sensitive: ordinary email is not a secure channel.

Links to other sites

Our reports link to many outside sources. Those sites have their own privacy practices, and following a link tells that site you arrived from ours.

Reaching this site from places where it is blocked

We serve the site over HTTPS only. We cannot prevent a network operator from seeing that you connected to ww3.press, even though they cannot see which pages you read. If that matters where you are, use a trustworthy VPN or the Tor Browser.

Measuring readership

We want to know how many people read this, and we do it from the server’s own access logs, which exist anyway and are deleted after 14 days. There is no cookie or reader identifier in your browser, so the counts are approximate.

On our press-pool article, a small first-party script randomly chooses a light or dark reading design for that page load. We count visible page loads, clicks to another article, support-link clicks and valid alert-form submissions separately for each design. A support click is not a contribution, and a form submission is not a confirmed subscription.

These experiment requests contain only the experiment name, design and event category. We retain hourly totals without visitor-level records, IP addresses, user-agent strings, referrers, email addresses or other form contents. Request access logging is disabled for this endpoint. The choice lives only in the open page: we do not store it in your browser or connect your activity across pages or visits. Counts therefore describe page loads, not unique people or returning readers.

Explicit design previews, browsers signalling Global Privacy Control or Do Not Track, and recognised automated clients are excluded from the comparison. Closing or reloading a page may change the assigned design. Email messages still have no tracking pixels or click tracking.

Contributions

Contribution buttons take you to a payment page hosted by Stripe. No Stripe code loads while you read this site. On that payment page, Stripe collects the payment and contact details needed to process your contribution under its privacy policy.

We can see contribution amounts, status and the contact information Stripe supplies for receipts and support. We do not receive your full card details. Contribution records are used for payment administration and reporting totals, not to add you to the alert list. Monthly contributors can manage or cancel through the link on the support page.

Changes

If we ever add analytics, a payment processor or anything else that changes what is collected, this page will be updated before it goes live, not after.