Privacy policy
Almost everything works without an account. Here is what we collect, and what we don't.
- Last updated2026-10-01
If you never sign in
This is the whole of it. None of it identifies a person, and none of it is joined to anything that does.
| What | Why | Kept for |
|---|---|---|
| Usage events — which page or tool was used, a short sanitised argument, how long it took, and a random session identifier | To see which parts of the directory answer questions and which return nothing, which is how the index gets better | Indefinitely, in aggregate. It contains nothing that identifies a person. |
| For requests to the MCP server and the public API (exports, badges, Preflight, the x402 endpoints and similar): the client's user-agent, a keyed one-way hash of the IP address, the country from our host's geolocation header, and the response status, size and timing. The IP address itself is never stored | To tell monitors, scanners and mirrors apart from real clients, and to count distinct callers without knowing who they are. Most traffic to these endpoints is automated, and we would otherwise be measuring nothing. The hash lets us see that two requests came from the same network; it cannot be turned back into the address without a server-side secret | Indefinitely |
| Aggregate page analytics from Vercel — cookieless, no cross-site identifier | Traffic volume and page speed | Per Vercel's retention |
If you sign in or send us something
Only what the thing you asked for actually needs.
| What | Why | Kept for |
|---|---|---|
| An account record: a Privy user id, and whichever of an email address or wallet address you signed in with | So a listing you claimed, an agent passport you registered, or credits you bought are still yours next time | Until you ask us to delete it |
| A listing claim: the domain you proved, the method, and the corrections you submitted | To apply your corrections and to show you what is queued | Until you ask us to delete it |
| An agent passport: whatever you typed into the registration form | It is a public profile — that is the point of registering | Until you ask us to delist it |
| An email address, if you subscribe to the newsletter, contact support, or ask to watch a Preflight target | To send the newsletter, to reply, or to tell you when a watched target's verdict changes | Until you unsubscribe or ask us to delete it |
What we never do
- ✕Sell or rent personal data. There is no advertising on this site and no data brokerage.
- ✕Set tracking cookies, or use cross-site advertising identifiers.
- ✕Store IP addresses. Requests carry a keyed one-way hash instead (see above).
- ✕Take custody of funds, hold a private key, or ask for a seed phrase.
- ✕Require an account to read anything. The directory, the wiki, the exports and the MCP server are all public and unauthenticated.
- ✕Train models on your data.
Who else sees any of it
The services that run the site. Each has its own policy.
The MCP server specifically
Every tool at /api/mcp needs no key, and most of them are read-only. 4 can change state on Sato Hub, and say so in their annotations: watch (stores the email address you give it, to tell you when a verdict changes), submit_project, register_agent, and swap, which returns a quote or an unsigned transaction and never signs, holds a key or broadcasts. We record which tool was called, a short sanitised version of the arguments, how long it took, the calling client's user-agent, and the keyed IP hash and country described above. We do not record who you are, because we do not know and do not ask.
Your data, on request
Ask and we will tell you what we hold about you, correct it, or delete it. There is no form to fill in and no waiting period we will hide behind — email satohub88@gmail.com. If you registered an agent passport or claimed a listing, note that both are deliberately public; deleting the account removes the private record, and delisting removes the public one.
Changes
When what we collect changes, this page changes in the same release. A privacy policy that has drifted from the product is a false statement, not merely an old one.
Security posture and how to report an issue: satohub.ai/security