Privacy

The site is hosted on Cloudflare Workers Static Assets. Normal web requests may be processed by Cloudflare to deliver pages, protect the service, and operate the network. Hello Charlie does not add its own visitor tracking on top of that hosting layer today.

The desktop navigation can remember whether the side rail is collapsed for the current browser tab. Title search runs locally in your browser against public post titles; it is not sent to a search service.

Advertising is inactive today. Reserved advertising areas, where shown, do not load ad provider code while advertising is disabled.

Comments are available on public posts unless disabled for an individual post. The first page of comments loads when an article opens; additional pages load only when requested.

Comment information

The form asks for a nickname, an optional password for that comment, and the comment itself. It does not ask for an email or load an avatar service. The nickname, comment, and time may become public after moderation. If you set a password, a hash, not the original password, is stored to check later edit and delete requests. A keyed IP hash is used for request limits. Hosting providers may still process IP addresses and other technical information in their infrastructure logs.

New and edited comments wait for review before appearing. After approval, use your comment’s Edit or delete action with its password. Comments submitted without a password can only be managed by Charlie. The form does not save passwords, drafts or comment IDs in browser storage. A lost password cannot be reset through an email account. Deletion removes the comment text and name while preserving replies; backups may retain older data. Image upload, account login, reactions, and advertising or analytics integrations are not part of the initial comment setup.

Hosting and retention

The blog is hosted by Cloudflare. The comment server uses Waline software hosted on Vercel, with comment data in a Neon PostgreSQL database configured in Sydney. This does not mean all infrastructure processing occurs in Australia. Guest comments do not use social login, an avatar service, or email notifications.

Comments and their password hashes have no automatic expiry: they remain until deleted by their author or removed by Charlie. This includes comments awaiting review or marked as spam. Author deletion replaces the text and nickname with a deleted marker and removes the password hash; comment IDs, timestamps, and reply relationships remain. Rate-limit records are cleaned on subsequent requests once they are more than about an hour old, so they can remain longer when the service is idle.

Provider recovery history and any protected database backup can contain older data after a deletion. Deletion from the active database does not immediately erase those copies. Provider processing is described in the privacy notices ofCloudflare,Vercel, andNeon. If you email a privacy request, your email address and message are also processed by Gmail and Charlie to handle that request.

Reports and privacy requests

To report a comment or request access, correction, or deletion of your information, emailyesimnoh@gmail.com. Include the post URL and comment ID, if available, so Charlie can identify the comment. Do not send your comment password or administrator credentials. A nickname alone does not establish ownership; a request may need additional verification. This email address is a contact channel, not a way to reset a lost comment password.