Xerith Blog
Privacy notice
Information handled by comments, private messages and website delivery.
Updated September 16, 2026
Who handles messages
Xerith Blog's publisher administers this website. Use the private contact form for questions, correction requests or requests to remove a comment or message. Do not send identity documents, payment details, medical records or other sensitive personal information.
Comments
We store the display name, comment, submission date and moderation status you provide. New comments are private to the publisher until approved. If approved, the display name, comment and date appear publicly beneath the article. Moderation records identify the signed-in publisher who made the decision. Comments remain until removed; there is no automatic expiration.
Private contact messages
The form collects a subject, message category and message text. No email address or account is required. Messages, replies, status and timestamps are stored for handling your inquiry. They are visible to the publisher and anyone who has your private receipt link. They are not listed publicly.
A random receipt token protects access to your message. Only a hash of that token is stored with the record. The link's secret is kept in the address fragment, which the browser does not send in the page request. Keep the link private. If you lose it, the site does not provide automatic recovery.
Messages remain until the publisher deletes them. You can request deletion through the contact form, including the message ID and enough information to identify the request. Do not publish your secret receipt link in a comment.
Spam prevention
The site creates a changing keyed identifier from a network address to limit repeated submissions. The raw address is not stored in the comments or contact-message database. These identifiers and timestamps are retained with submissions until their records are removed. The identifier is not displayed to readers.
Search, sharing and storage on your device
Article search filters text in your browser. We do not store search terms in an application database. A term in the page address may appear in browser history or hosting records. Sharing copies a link or attributed excerpt, or opens your device's share controls. It does not automatically post elsewhere.
The application does not set advertising or analytics cookies. It does not use browser storage to track readers. Form text stays in the open page while you write; it is not a saved draft until submission succeeds. A receipt link may remain in your browser history.
Publisher sign-in and technical delivery
The publisher dashboard uses ChatGPT sign-in and restricts access to the site owner's configured account. That sign-in service has its own privacy and session practices. Reading articles, submitting comments and contacting the publisher do not require sign-in.
Hosting and network providers process technical information, such as IP addresses and requested pages, to deliver and secure the website. This notice does not claim that infrastructure providers keep no logs. Article images are served from this site. Links to sources open websites with their own privacy practices.
Advertising and measurement
AdSense and audience analytics are not currently active. Ownership-verification tags, when configured, identify the site to Google but do not themselves load ads or audience analytics. We will update this notice and configure applicable consent controls before introducing advertising or analytics.
