Privacy Policy
Last updated: September 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. The control below stores an opt-out choice in this browser.
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.
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.