Privacy

What we collect and what we do not, last updated October 2026.

There are no accounts, no cookies, no trackers and no analytics scripts on this site.

Logs we keep. (1) Our web server access logs record the caller IP address, user agent, referring page, and the request path and query string. If the query string contains a wallet address, a transaction signature, a token mint or a request id, the whole query string is replaced by REDACTED before the line is written, and a referring page that contains one is cut to its host. Our web server error logs may record the caller IP address and the request; such values in the request query string are removed at the daily rotation, so they stay in the raw log for at most about 24 hours. Logs are rotated daily and we keep 90 daily rotations, compressed. In log lines written before 26 September 2026, the same values were removed from query strings on that date. Copies made before that date may remain in our off-server backups until they are deleted. (2) Our payment proxy keeps a separate access log with the request time, host, method, path and status code, but no query string, no IP address and no user agent. It is rotated daily and kept for 30 days. (3) The nsgoods Workbench MCP keeps two logs. Both identify the caller only by a daily keyed hash of the IP that cannot be linked back to the IP after that UTC day, and both are deleted after 30 days. The tool log records, per tool call, only the time, tool name, and argument names and lengths. The connection log records, when a client connects, the user agent, the client name and version it reports and the protocol version it asks for; and when a request to the MCP endpoint fails, the time, the request method, the HTTP status, the JSON-RPC method name, a few request headers (protocol version, accept, content type, and whether a session id was sent) and the start of the error message. Neither log stores argument values, the raw IP or the session id. (4) Daily rate limit counters are kept in temporary files. They hold only the current UTC day's counts, keyed by a daily keyed hash of the caller IP (on the Workbench and on the signals, regime, solar and extractability preview limiters), and are reset on the first request of each new UTC day. The free /feedback endpoint stores the message you send, your user agent and a daily keyed hash of your IP (the same scheme as the rate limit counters), never the raw IP. (5) Our revenue watcher stores on-chain payment records only, which are public blockchain data such as payer address, amount and transaction hash. (6) We keep a log of the emails we send (recipient, subject and date), and if you email us, we keep the correspondence. Entries written before 26 September 2026 that fall outside these limits, including Workbench tool log records in an earlier fuller format, are removed by 26 October 2026. (7) Two of our services keep additional logs that also contain the caller IP address. The screening audit log of our Agent Trust Oracle records, for each call to its screening routes (paid or preview), the time, the route, the address screened and its chain, the verdict and the sources checked, whether the call was paid, the payer address taken from the payment, the signature of our answer, the user agent and the caller IP address. It is rotated daily and kept for 90 days. A shared payment log used by our regime, extractability, solar and trust services records, for requests that carry a payment header, the time, host, path, status and outcome, the user agent and the caller IP address. It is rotated daily and kept for 30 days. (8) Our multi list sanctions screening (/screen-multi and /screen-url) and our settlement verification (/settle) keep a log of calls that carried a verified payment and returned an answer. For each such call it records the time, the route, the input as sent (for /screen-url only the host of the endpoint URL and the payee addresses read from its quote), the verdict, a SHA-256 hash of our signed answer, the payer address when the payment states one, the network and amount, the user agent and a daily keyed hash of the caller IP, never the raw IP. It does not record the settlement transaction. Calls without a payment, previews and errors are not written to it. It is rotated daily and kept for 90 days. We use all of the above only to operate, secure and rate limit the services.

Payments happen on public blockchains. Anything you put on chain is public by the nature of the chain, not because of us.

If you email us, we keep the correspondence. We do not sell or share any data with third parties.

Questions: nikos@nsgoods.org