Privacy Policy

You can reach our data protection contact at [email protected]. We answer every request within thirty days and reply in the same channel you used. If you prefer paper mail, write to our editorial contact first and we will route the request. We do not use a chatbot or ticketing wall for privacy requests — a person reads every message.

We collect the minimum data needed to run the site and to measure which pages work.

The web-server log keeps each request for 30 days: the requested URL, the referring page, the user-agent string, and the IP address. We rotate the log every night and purge the 30-day archive on the first of each month. Nobody outside the editorial team has access to the archive, and no part of it leaves the server.

The analytics layer aggregates the same requests into daily and monthly counts: how many people read a page, how long they stayed, which section they left on. The counts are kept for 12 months and then deleted. The analytics does not fingerprint the browser, does not correlate across sites, and does not join requests into a long-term visitor profile.

If you accept the cookie banner, the preference cookie stores your consent choice for 365 days so we do not re-ask on every page load. If you reject marketing cookies, the analytics switches to a sampled mode that does not store any cookie at all. There is no advertising tag, no social-media pixel, no Google Analytics and no Facebook Pixel on editorial pages.

We do not collect your name, your address, your date of birth, your phone number, or any payment data on this site. Those details go directly from your browser to the operator when you register at Donic, and the operator holds them under its own privacy notice, which you should read before you deposit.

Raw web-server logs rotate every night. The latest night sits in the hot log for 24 hours, then moves into the 30-day archive. On the first of each month the 30-day archive is deleted. We keep one anonymised summary per month (page counts, no IPs) in a separate archive for 12 months, then that goes too.

Analytics is aggregated into per-day counts at the moment it is received, so the raw event stream is never written to disk. The daily counts are kept for 12 months and then deleted automatically on the first of the thirteenth month.

Cookies set from this site expire within 395 days of your last visit if we set them; third-party cookies follow the lifetime declared by the vendor. The affiliate-tracking cookie on the operator's domain is governed by the operator's privacy notice, not ours.

If you ask us to delete anything we hold about you — most often a specific IP address, or a specific email you sent us — we act within 30 days and reply to confirm. If a request falls under GDPR (because you are in the EU) or CCPA (because you are in California), the 30-day clock is the statutory maximum and we usually answer faster.

Backups are a separate concern: an encrypted off-site backup of the web-server runs nightly and keeps the last 14 nights. When we delete something from live, the deletion rolls through the backup window over the next 14 days — this is the usual trade-off between a safe recovery point and a strict retention promise.

We use the data we collect for three things: to keep the site running (web-server logs), to understand which pages people read and which ones we should rewrite (aggregated analytics), and to measure which outbound link brought a new account to the operator (affiliate tracking). We do not sell data and we do not share it with the operator beyond the anonymised click-through required by the affiliate program.

Our analytics runs on a small self-hosted install, and we do not embed Google Analytics or Facebook Pixel on editorial pages. The affiliate link does set a tracking cookie, which is required for the operator to attribute a new account to us. If you reject marketing cookies in the banner, the link still works, but the attribution falls back to the operator's own click-through model.

If we change this notice in a way that affects what data we collect or how long we keep it, we update the 'last reviewed' date at the top of the page and post a short line in the site changelog. We do not email visitors about privacy changes because we do not keep an email list. Material changes also trigger a fresh cookie-consent banner the next time you visit.