Privacy

The formal policy is being finalised. What is below is an accurate description of what the service stores today, written from the code rather than from a template. A reviewed policy will replace it before the first account is billed. Anything you need in the meantime: info@torinagi.com.

What is stored

• Your sign-in identity — email and name, held by Clerk, our authentication provider. We do not store passwords, because we never receive one.
• Wallet addresses you register. These are public by nature. A signature proving you control one is stored alongside it.
• Agents, their limits, and every decision made about them — allowed, held and refused, each with its reason and timestamp. This is the product, and it is deliberately durable: a refusal you cannot look up later is a refusal you cannot explain to anyone.
• API requests, for troubleshooting and for the audit trail.

What is not stored

• Private keys. Not encrypted, not briefly, not at all — the software has no path that could receive one.
• Card or bank details. Nothing is charged yet, and when it is, payment details will sit with the payment processor rather than with us.

Sub-processors

Clerk (authentication), Railway (hosting and database), Vercel (this website), Cloudflare (DNS). Adding one that touches your data will be reflected here before it happens.

Deleting your data

Write to info@torinagi.com and it is deleted. One caveat worth stating plainly: records of decisions we made about your agents are what let either of us reconstruct what happened, so if you ask for those to go, they go — and neither of us can answer that question afterwards.

Last updated 6 August 2026 · This page will be replaced by a reviewed policy before billing begins.