Namegarage

Blog comments privacy notice

Version 2.0 · . Read the current notice.

Sign in with Google, GitHub, or Apple using the providers offered on the comment form. We receive an account identifier, name, email address, email verification status, and any profile image supplied by that provider. Better Auth runs on our Cloudflare infrastructure and stores this information in a separate sign-in database. OAuth access and refresh tokens are encrypted in that database; ID tokens are verified during sign-in and are not stored. We do not receive your provider password or request access to your posts, repositories, files, or contacts.

Google sign-in requests only openid, profile, and email. We use the profile data to identify your account, keep you signed in, and attribute your comments. We do not sell sign-in data, use it for advertising, or use it to train AI models. We share it only as needed to provide sign-in, host the service, and moderate comments as described below, or when required by law.

The comment database stores your account identifier, account name, sign-in provider, comment, post, submission identifier, and time. For GitHub sign-ins, it also stores a public profile link derived from your GitHub account identifier. Your email address and sign-in tokens are not published or sent to Telegram.

Comments stay private until the owner approves them in a private Telegram chat. After approval, your account name, sign-in provider, comment, date, and GitHub profile link when available appear publicly. If a provider supplies no name, a generic label such as Apple reader appears. A provider sign-in confirms control of that account; it does not verify a legal identity. Older comments may have an unverified display name. The Author badge identifies replies from the site owner. Commenting does not subscribe you to messages.

Essential cookies keep you signed in for up to seven days and bind a sign-in attempt to your browser. Signing out ends that session. The comment form stores a draft in this browser tab so it can restore your text after sign-in for up to 30 minutes. Submission clears the saved draft. These features do not track your reading for advertising.

Cloudflare hosts the site and databases and checks submissions with Turnstile. It processes connection information for hosting and security. Sign-in sessions store the connecting IP address and browser user agent; expired sessions and sign-in attempts are cleared hourly. Sign-in rate counters are cleared after a day. Comment limits store a keyed hash of the IP address and your account identifier; those counters are cleared once their windows are 48 hours old.

Your chosen provider processes sign-in under its own privacy policy: Google, GitHub, or Apple when offered. Telegram processes the account name, provider, profile link, and comment sent for moderation under its own privacy policy.

Sign-in account records remain until you request their removal. Approved comments remain until removed. Pending comments cannot be approved after 30 days; cleanup clears their name, text, account identifier, provider, and profile link. Rejecting or removing a comment clears the same fields. A minimal submission and moderation record remains to prevent duplicates and record the owner's action. Clearing our database does not erase previously sent Telegram messages, provider backups, or copies other people made while a comment was public.

To request removal of a comment or sign-in account, write to [email protected] and identify the account or comment. A person reviews requests. Nikolay Kolev operates this blog. This notice supplements the site's Privacy Policy.

Comments and sign-in information are never sent to ElevenLabs. Generating narration sends the published article text to ElevenLabs. Playing a saved recording requests audio from this site and Cloudflare, without a playback request to ElevenLabs.