Privacy and data handling

Accounts

Google or GitHub provides the basic profile information used to create your account. The site stores the provider connection needed for sign-in, but administrative pages do not expose OAuth tokens.

Likes and qualified views

A random, signed, first-party cookie distinguishes an ordinary browser for like toggles and qualified-view deduplication. It contains no name, email, fingerprint, or meaningful personal value. Clearing cookies or using another browser creates another visitor identity.

Views are counted at most once per post and visitor during a calendar 24-hour period. Public pages expose aggregate counts only, and administrators do not receive a per-user reading-history feed.

Comments and contact messages

Comments, likes, and contact submissions are explicit account activity. Contact messages and internal review notes are visible only to administrators. Comment moderation context is limited to moderators and administrators.

If you draft a contact message before signing in, the subject and message remain in same-tab session storage for up to 24 hours. They are not sent to the server until you authenticate, review the restored draft, and explicitly send it.

Retention and requests

Published content, moderation records, audit events, and contact submissions are retained for continuity and abuse prevention until a documented deletion or anonymization process applies. Database backups follow the infrastructure retention policy configured for the production service.

For a data access or deletion request, use the authenticated contact form so the request can be associated with your account.