This is a personal site, not a business, and this page is written to be read rather than to satisfy a checklist. It explains exactly what is stored, why each field is there, and what is deliberately not collected.
Last updated 11 August 2026
There are four things in the database. Three of them exist only because somebody chose to fill in a form.
Your browser does remember, for the length of the tab, that it has already counted a post — so a refresh does not count twice. That flag lives in your own browser, says nothing but "counted", and is gone when the tab closes.
Every comment and testimonial is read before it appears. Rejecting one does not erase it. It sets a status, so the decision stays reversible and I can never quietly lose something I should have published. The practical consequence is worth stating plainly: a rejected comment still exists in the database, with the email address that was submitted alongside it. The same is true of every private message.
That is where it stands today, and it may not stay there. A retention rule, or a way to remove something on request, is a reasonable thing to add later. If it changes, this page changes with it.
The site runs on Cloudflare. Every request to it therefore passes through Cloudflare's network, which sees the IP address it came from, along with the usual technical details of the connection, in order to route the request and to protect the site from attack. This is true of every hosted website in existence, including the ones that claim not to track you, and saying "no tracking" without mentioning it would be the dishonest version of this page.
What I do not do is take any of that and put it in a database, join it to anything, or look at it as a record of who read what. Nothing in this project reads a visitor's IP address.
The forms are protected by Cloudflare Turnstile, which works out whether a submission is coming from a person or a bot. By Cloudflare's own account it looks at a small set of signals from your browser: the IP address, a fingerprint of the encrypted connection, the browser's user-agent string, and which site the check is running on. Those signals are used to answer one question, person or bot, and I never see them. Cloudflare publishes the detail in itsTurnstile Privacy Addendum.
On blog posts the check is not even loaded until you press "Post a comment". Readers who never comment never touch it. That was a deliberate build decision and it is the reason the comment form sits behind a button.
Only me. The moderation area sits behind Cloudflare Access, which means there is no login page and no password stored in this project. Access is granted to one identity and nobody else can reach it. Nothing collected here is sold, shared, published beyond what is described above, or used for any purpose other than the one the form was for.
sumitn.com is the earlier version of this site. It is still live, deliberately, and it is a different thing technically: a set of static files with no database behind them, no forms, no comments and no view counting. It collects nothing at all. It is also hosted on Cloudflare, so the paragraph above about IP addresses applies there in exactly the same way.
The two sites are separate. Nothing links a visit to one with a visit to the other, because there is nothing on either side that could.
The site is a work in progress and this page is the current statement, not a permanent one. Anything written about privacy elsewhere, including in blog posts about how the site is built, is a snapshot of the day it was written. This page is the one that is kept up to date.