Privacy
We collect as little as a website can. Last updated 20 August 2026.
No accounts
There is no sign up, no login and no profile. Nothing on this site asks you who you are, and there is no user record to leak because there are no users.
No tracking cookies, no analytics
The site sets no cookies for tracking. There is no analytics script, no tag manager, no pixel, no session recording and no advertising network. Nothing on the page reports your behaviour to us or to anyone else.
Server logs
The web server keeps standard access logs, which is what any web server does by default. A log line records your IP address, the time, the page you asked for, the response status, and the user agent and referrer your browser sent. The logs exist to debug errors and spot abuse. They are not joined to anything else and they are not sold or shared.
Operator note: if you run this site, state your real retention here. The deployment in the README uses nginx with its default access log and whatever rotation your distribution ships (on Debian and Ubuntu that is logrotate, daily, keeping 14 days). Confirm what your server does and replace this paragraph with the number.
What is stored in your browser
The site uses localStorage for exactly two things, both of which stay on your device and are never sent anywhere:
- A cache of Nostr profile metadata (kind 0 events: names, avatars, NIP-05 addresses) for the reviewers whose reviews you have looked at. This saves re-querying relays on every page. Entries expire, and the cache is capped and evicted oldest first.
- Interface preferences, so the site behaves the same way next time.
Clearing your browser's site data removes both. Nothing breaks, the profile lookups just run again.
What your browser talks to
Loading a page connects your browser to a few places besides this site. That is how a site with no server-side tracking still reads live data:
- Public Nostr relays, over WebSocket, to read reviews and reviewer profiles. The relay sees your IP and what you asked for, as any server you connect to does. The relays are listed on the about page.
- Reviewer avatar images, loaded from wherever the reviewer's profile points. These are sent with a no-referrer policy, so the host does not learn which page you were on.
Publishing a review
Writing a review happens in your browser, not on our server. The event is signed by your NIP-07 extension (Alby, nos2x or similar) and broadcast from your browser straight to the relays. Your private key never leaves the extension and this site never sees it. We do not build custom key management and we never ask for a key or a seed phrase.
Anything you publish to Nostr is public and permanent
This is the part worth reading twice. A review is a signed event on public relays. Once it is out, it is out:
- Anyone can read it, now and later, using any Nostr client. It is not "public on Cashumints.space", it is public on the network.
- It is permanently linked to your Nostr public key, alongside everything else that key has ever published.
- Deleting it is a request, not a command. You can publish a deletion event and some relays will honour it, but a relay is free to ignore it and anyone who already copied the event still has it. Treat a published review as permanent.
- We cannot delete it for you. We can stop displaying it here; that changes nothing on the relays.
If you want to review a mint without that being tied to your main identity, use a separate Nostr key. Note that a key with no other activity is shown as such on harsh reviews, because a brand new key writing a one star review is a pattern readers deserve to see.
Questions
The site is open source: if you want to check any of the above, read the code at GitHub. Questions and corrections can go in an issue there.