Privacy Policy
Last updated: 20 October 2026
This policy explains how /dev/YgnizemKamajaya handles information when you visit the site or use comments.
Analytics
When configured, this site uses Umami Analytics for aggregate usage measurements without advertising profiles. When separately enabled, native reading analytics record article paths, depth milestones and estimated active time. No account identity, query strings, article text or cross-visit identifier is collected. A random in-memory visit key is hashed server-side for retry deduplication and becomes eligible for deletion after 24 hours; daily aggregates are retained for 90 days. Scheduled cleanup is bounded and may run later during a backlog. The control below opts out of these analytics systems in this browser; native reading analytics also honor Do Not Track and Global Privacy Control.
GoatCounter traffic (optional)
When enabled, GoatCounter receives public page paths and external referring hostnames. We exclude URL queries, fragments, page titles, search, saved-content and admin/token routes. Requests contain no application credentials or persistent browser identifier; the provider receives your network address and browser user agent and processes visits under its own session and retention policy. Our collector honors the control below, Do Not Track and Global Privacy Control. Our private dashboard serves aggregate provider statistics from a five-minute cache; expired cached aggregates remain in bounded storage until replaced or cleaned up; reading-depth and active-time measurements remain separate.
Public comments and Gravatar
A comment’s display name, plain-text body, locale, time, spoiler state, and email-derived SHA-256 Gravatar hash are public while the comment is visible. The raw email is normalized to derive that hash and is not persisted. A hash is guessable personal data, not anonymization. Displaying an avatar makes a third-party request to Gravatar. Submitted names and emails are not verified identities.
Guest identity, abuse prevention, and Turnstile
The comments service stores a signed guest token in browser storage for up to 30 days. It supports posting, likes, and reports but does not create an account or prove one person. Server-keyed browser and network signals, short-lived counters, and private comment associations are used for rate limiting and abuse response. Comment submission uses Cloudflare Turnstile, which processes browser and network information under Cloudflare’s terms.
Retention and moderation
Visible comments and likes remain until removal or a later approved retention policy. Abuse counters and retry records expire after 24 hours; private comment abuse associations after 30 days. Reports are deleted 30 days after resolution or 90 days after creation. Hidden content becomes eligible for permanent removal after 30 days; content-free moderation audit records expire after 90 days. Removed comments retain only structural placeholders needed for reply continuity.
Signed-in readers and guestbook
When D1 reader Google sign-in is configured, the service stores a provider account identifier, profile name, email and avatar URL. Profile name and avatar may be public with visible submissions; raw reader email is not a field in public comment or note responses. Guestbook posting requires reader sign-in and every note or reply awaits moderator approval. Allowed article comments may publish after screening; suspicious comments are held pending and rejected submissions retain no raw content. Signing out or session expiry does not delete the reader identity; no automatic reader-profile deletion interval is implemented. Use the removal-request contact below.
Attachments and moderation
Supported attachments are stored separately from text and may be reachable by their direct public URL before moderation; this is not private staging. Images can retain EXIF/GPS metadata: avoid uploading private material. Rejecting a guestbook note queues its image for durable deletion; later approval restores text only. Origin deletion is retried after failures and upload-grant expiry; CDN caches and provider backups can outlive the application reference. A removed ancestor may retain only a structural placeholder for approved replies.
Moderators and provider records
Authorized moderators sign in with Google or GitHub. Short-lived OAuth attempts, restricted provider identifiers, sessions, and content-free moderation events are stored for administration. OAuth attempts expire after 5 minutes; sessions last at most 8 hours with a 30-minute idle limit. The application does not retain provider access or refresh tokens.
Storage, transfers, and backups
Comments are processed by the separately hosted comments service and its infrastructure providers. Provider security logs, recovery history, and backups may follow provider-controlled retention, so application deletion schedules cannot promise instant removal from every recovery copy. The site does not sell personal data.
Questions and removal requests
Guests cannot self-edit or self-delete comments. For a privacy question, moderation reconsideration, or removal request, use an established social contact link on the About page and identify the relevant page and comment. Do not post private information publicly; a typed email alone does not prove ownership. See the comment guidelines.