Privacy

toryo runs on your own machine. Your source code, your prompts, and your agents’ output are not sent to us, with one narrow exception: when toryo itself crashes it sends a short error message, and that message is whatever the failing code put in it, so it can quote a fragment of what toryo was processing. Secrets are redacted from it, paths are collapsed, it is capped at 500 characters, and you can turn crash reports off entirely. What we hold otherwise is the small amount of information needed to email you and to license the software, and, only if your team chooses a shared knowledge plane, the knowledge your agents record there.

If you submit the form, we store your email address, which form it came from, and the time you submitted it. Nothing else. There is no account and no password.

The site sets no cookies, runs no analytics, and embeds no third-party trackers. Your IP address is held in memory for a few minutes to rate-limit form submissions and is never written to a database.

If you start a trial or activate a seat, the license service records:

• your email address, and your name if you give one
• your license and seat, including plan, seat count, and status
• an identifier for each machine you activate on, plus when it was first and last seen

Machine identifiers exist so that one seat covers all of your own machines instead of being consumed by the first one. They are not device fingerprints and are not used to track you across anything.

When toryo crashes, it sends us a crash report by default. The report holds toryo’s own stack frames, the error message with paths and anything that looks like a secret stripped out, which app and command failed, the version and platform, and the tenant and user identifiers from your license.

The report is built from a fixed set of fields, and none of them is your email address, your license key, your environment variables, the arguments you ran toryo with, a request or response body, the values in your database, or the signed proof your license is real. That is a fact about the report’s shape rather than something we filter for: sending any of them would mean adding a field to the report first.

The one free-text field is the error message, and it has secrets redacted and paths collapsed before it is sent. That is a filter rather than an absence, so it is worth being precise about it. The message is whatever the failing code put in it, which means it can quote a fragment of what toryo was processing when it broke. What the filter then does is replace anything shaped like a secret and any email address, reduce each path to a label and a filename rather than your directory tree, and cut the whole message to 500 characters.

Reports are processed by Sentry on our behalf. To turn it off, run toryo settings set --telemetry false, use the toggle in the desktop console’s settings, or set TORYO_TELEMETRY=0 in your environment. The desktop console picks the change up the next time you open it.

Your repositories, your prompts, and your agents’ output stay on infrastructure you control. toryo’s execution plane is local by design: an agent working on your code is a process on your own machine, in every configuration of the product.

Model usage goes directly from your machine to your provider under your own credentials. We do not proxy it, see it, or bill for it. That provider’s handling of the traffic is governed by your agreement with them, not by this notice.

One thing does come back to us when toryo itself breaks: the crash report described above. Of what this section describes, the only thing it can carry is whatever the scrubbed error message quotes of what toryo was processing, and you can turn it off.

The memory, library, and code index your agents build up live in a database. By default that database is on your own machine and we hold no copy of it.

A team may instead choose a shared knowledge plane so their agents learn from one another. That is opt-in and off until you configure it, and it is the one choice that places any of this with us. What it then holds is what your agents recorded and what your people authored: memories, library documents, and a code index of file paths, exported symbol names, and the imports between them. It does not hold the contents of your source files. Documents your team authors contain whatever you put in them.

Tenants are isolated at the database level, the store is encrypted at rest, and you can ask us to delete the whole of it. Ending access and destroying data are two separate steps, so we will confirm before doing the irreversible one.

Interest-list addresses are kept until you ask us to remove them. Licensing records are kept for as long as the license is active and for a reasonable period afterwards for accounting purposes.

We do not sell personal information and we do not share it for advertising. It is handled by the infrastructure providers that run this site and the license service, and crash reports are processed by Sentry. All of them act on our instructions.

Write to support@toryo.ai to see what we hold about you, correct it, or have it deleted. Deleting a licensing record ends the license it belongs to, so we will confirm before acting on that one.

If this notice changes in a way that affects you, we will update the date at the top and, where the change is material, tell the people on the list.