Privacy

What Phase 1 collects

Nothing. The current build collects no personal data, sets no cookies, and stores no information about visitors. The newsletter and push UI elements visible on the site are placeholders — they are disabled and do not transmit, store, or process any input.

What is not on this site

• • No analytics provider (no Google Analytics, Plausible, Fathom, or similar).
• • No tracking pixels (no Facebook Pixel, no LinkedIn Insight Tag, no TikTok pixel).
• • No advertising. No ad code. No ad-network sniff scripts.
• • No third-party fonts loaded at runtime. No third-party iframes (no embedded YouTube, no embedded Twitter timelines).
• • No first-party cookies and no local-storage usage by the site code.

Future features that will require opt-in

Some planned features will collect data when (and only when) they are explicitly enabled in a later phase. Each requires an opt-in and a clear unsubscribe path:

• Newsletter (Phase 6)

  Stores the email address you provide, plus the subscription timestamp. Double opt-in via a confirmation email. One-click unsubscribe in every issue. No third-party sharing. No tracking pixels in the email.

• Web push (Phase 7)

  Browser push subscriptions store an opaque endpoint identifier issued by the browser. We never request the browser permission prompt without an explicit user action. Rate-limited to one push per day. Unsubscribe is one click in your browser's site settings or a button inside the site.

• Server logs (whenever public)

  When the site is publicly deployed in a later phase, the server may log standard request data (IP address, user agent, requested path, timestamp) for security and operational reasons, retained for a short, bounded period. No first-party analytics is planned.

Contact

See the Contact page for how to reach the editorial team about privacy questions, data requests, and corrections.