Public browsing
Reading public pages does not create a BTN account. The site’s theme control stores a light or dark preference in your browser’s local storage; that preference is not sent to BTN as a profile. Normal web-server logs may record technical request information such as an IP address, requested URL, user agent, time and response status for security and operations.
Member accounts
BTN reader accounts are optional. For a member, BTN may store an email address and verification state, a display name or avatar URL where present, account status, and account creation, update and last-login timestamps. Connected sign-in identities are stored separately and may include the provider, provider account identifier, username and provider-supplied email needed to associate that identity with the member.
Authentication and cookies
BTN uses a session cookie for authenticated members. Members may also receive a persistent-login or “remember” cookie so a valid sign-in can continue across browser sessions. Authentication cookies are HTTP-only and SameSite=Lax, and are Secure in production. The persistent-login secret is stored server-side only as a hash. BTN may also keep short-lived authentication records for email sign-in and verification. Reader authentication remains separate from private admin sessions and API access controls.
Dossier tracking
Signed-in members can track published dossiers. BTN stores the relationship between the member account and the dossier being tracked so it can show that list on the account page. A member can stop tracking a dossier, which removes that relationship.
Email alerts
Where email alerts are enabled, a member can opt in for a tracked dossier. BTN stores that preference and may create notification-event and delivery records when a relevant public dossier update occurs. Alerts are not assumed to be available at all times.
External identity providers
If a member signs in with or connects an enabled provider such as Google, GitHub or X, BTN stores the identity information needed to associate that provider account with the BTN member. Not every provider is necessarily enabled. The provider’s own privacy terms also apply to the interaction on its service.
Traffic analytics
Ordinary public pages load privacy-focused, self-hosted analytics from stats.oldstackjournal.com and an analytics script from analytics.ahrefs.com. The self-hosted analytics records aggregate usage information such as page URL and title, referring page, browser language and screen size; analytics requests also carry normal connection information such as an IP address and user agent. BTN does not use these scripts to build advertising profiles. Account, sign-in and private admin pages do not load these public analytics scripts.
Contact, retention and deletion
BTN does not publish fixed retention periods or offer a self-service account deletion control. Members can stop tracking dossiers through their account. For account, data or other questions, use the contact page. Information submitted through the contact form—including your name, email address, subject and message—is emailed to BTN so it can respond.
External links and services
Dossiers link to source sites, and the footer links to Google, X, LarsJansen.dev and Old Stack Journal. Following an external link means the destination’s privacy practices apply. The site’s Tabler interface files and BTN brand assets are served locally; the external analytics script is not required for the publication to render or function.
Policy changes
This notice will be updated when BTN makes a materially relevant change to how the site handles data. The updated date at the top will change with it. This page describes current behaviour rather than making a broad legal-compliance claim.