What we collect, and what we don’t

You can browse the feed, every product page, every release and the search results without signing in. Doing so sets no cookie and stores nothing about you in our database.

We measure aggregate traffic with Vercel Web Analytics and Vercel Speed Insights. Both are cookieless and neither builds a profile across sites. Search terms are stripped before anything leaves your browser — the address bar carries your query while you type, and it is removed from every URL and every event we send. Nothing we record contains text you typed.

Signing in is optional and exists to unlock three things: following products, a personal feed, and commenting. We support Google, GitHub and Steam, and we ask each for the minimum identity scope.

From the provider we store your name, email address, and avatar URL. Steam does not return an email at all, so a Steam sign-in gets a synthetic unusable address instead. We also store the session itself — its expiry, the IP address it was created from, and the browser’s user-agent string — which is what lets you stay signed in and lets a session be revoked.

The provider also hands us OAuth tokens, which we store because the authentication library’s schema declares them. Nothing in this app reads them.We never call a provider’s API on your behalf, and we never post anywhere as you.

We do not use passwords, we do not send marketing email, and we do not sell or share any of this.

Comments are public. Anyone who can read the page can read what you wrote, along with the display name and avatar shown beside it.

Your display name is separate from the name your provider gave us, and you control it. Google in particular returns legal names, so we default your public name to it but let you change it at any time on your account page. Your email address is never shown on the site.

Comment threads are deliberately not indexed by search engines and are not included in our sitemap, RSS feed or machine-readable exports. They load only for a reader who opens the page.

Following a product is private. Nothing on a product page reveals who follows it, or how many people do.

Posting a comment or suggesting a product is rate-limited per account and per network. To count requests from one network without keeping addresses, we store a salted one-way hash of the IP address and never the address itself. The hash is a counting key: it is never displayed, never joined to your account, and never written to a log.

New comments are checked automatically for the patterns that characterise spam. A comment that trips one is held for a human to look at rather than deleted — nothing on this site is removed by an automated decision alone.

We use Vercel BotID on the two endpoints that accept public writes, to tell a browser from a script.

We run on other people’s infrastructure, and these are all of them:

• Vercel — hosting, plus the analytics described above.
• Neon — the Postgres database everything is stored in.
• Google, GitHub and Steam — only the one you chose to sign in with, and only at the moment you sign in.
• Anthropic— the text of a comment may be sent to Anthropic’s API to be classified as spam or not. This is the only place user-written text leaves our infrastructure. It is not used to train a model.
• Resend — email delivery. The only mail this site sends goes to its own operator: a notice when someone suggests a product, and alerts when the data pipeline breaks. We do not email you.

Server logs record what the site did, not what you said. A refused comment logs a reason code and a length; a search logs an outcome. Text you typed never becomes a log field, and neither does the salted network hash.

Your account page has a delete button, and it is a real delete rather than a deactivation. It removes your account row and, with it, your sessions, your linked provider identities, your subscriptions, your comments and any reports you filed. There is no copy kept behind it and no restore.

You can also delete a single comment yourself. A deleted comment keeps its place in the thread as a marker so replies to it still make sense, but its text is erased.

Anonymous product suggestions are keyed to a browser cookie rather than an account, so they are not attached to you and cannot be individually identified for deletion. Clearing your cookies for this site disconnects your browser from them.

Account data and comments stay until you delete them. Sessions expire on their own. The rate-limit hashes are only ever read for a window of an hour or a day, and are removed with the rows that carry them.

This site is run by one person. If something here is unclear, or you want data removed and the delete button did not cover it, get in touch through Jeff Mixon’s site.

If this policy changes in a way that affects what we collect or who sees it, the change will be described here rather than made quietly.