FluidBlog collects as little as possible. This page explains what we store and why.
Reading analytics
We count page views and time on page to understand which stories resonate — without cookies, accounts or anything stored on your device. To avoid counting a reload twice, our server combines your IP address and browser name with a secret that changes every day and keeps only the resulting one-way hash; the IP address itself is never stored. Because the secret is deleted daily, visits on different days can't be linked. Crawlers aren't counted, and if your browser sends Do Not Track or Global Privacy Control we record nothing.
Accounts
If you create an account we store your email, display name, optional profile details, comments, reactions, your reading list and whether you want reply notifications. Passwords are stored as salted hashes.
Reading progress (for
If you create an account we store your email, display name, optional profile details, comments and likes. Passwords are stored as salted hashes.
quot;Continue readingIf you create an account we store your email, display name, optional profile details, comments and likes. Passwords are stored as salted hashes.
quot;) and offline copies of pages you read or save are kept only in your browser. You can clear the reading history from your account page.Newsletter
We store your email and subscription status. You confirm before receiving anything and can unsubscribe from any email.
Cookies and local storage
One essential, httpOnly cookie keeps you signed in; analytics use no cookies at all. Reading preferences and saved posts live only in your browser's local storage.