Xerith Blog

Privacy notice

Information handled by comments, private messages and website delivery.

Updated September 18, 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. Simply typing or filtering articles does not store search terms in our application database. Sending a question is a separate action described below. 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 cookies. It stores your analytics cookie choice in local storage. Google Analytics cookies are used only if you choose Allow analytics. 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.

Audience measurement

With your permission, Google Analytics 4 measures visits, pages viewed, engagement and traffic sources. Google processes device and browser information and uses first-party cookies to distinguish visits. We load Google Analytics only after you select Allow analytics. You can decline without losing access to any article and can change or withdraw your choice using Cookie settings in the footer. Analytics cookies are set with a 90-day lifetime, renewed with activity. Withdrawal stops future collection and removes this site's accessible Google Analytics cookies; it does not automatically erase data already processed.

We exclude contact forms, private receipt pages and the publisher dashboard from analytics. We remove query strings and address fragments from the page address sent to Analytics, limit referrer information to the referring origin, and do not send comment text or private messages. Google signals and advertising personalization are disabled. Learn how Google uses information from sites that use its services. Use our contact form for questions or deletion requests.

Advertising

AdSense is not currently active. Ownership-verification tags identify the site to Google but do not themselves load ads. We will update this notice before introducing advertising.

Reader questions and AI answers

When you choose to send a question and confirm the notice, we store your question, answer when available, source links, timestamps, review notes and any resulting article link. These are available to the publisher for editorial review. Answers can be reused for the same question; a reviewed question may inform a public article. Do not include names, contact details or other sensitive personal information.

When instant AI answers are enabled, the question is sent to OpenAI for generation and web research. The application requests that the API response not be stored as an OpenAI response object; this does not override the provider's own security or retention practices. No contact messages, comments or publisher secrets are included in that request. Questions are not sent to Google Analytics. Immediate answers are AI-generated and are not published articles.

We keep questions and review records until removed by the publisher. A changing keyed network identifier and request timestamps are stored separately to limit abuse; raw network addresses are not stored in these tables. Use the private contact form to request removal and identify the question without sending sensitive details.