Legal

Data Use

Last updated July 26, 2026

This page is a plain-language summary of how Digitorn uses your data. For the full legal detail, see the Privacy Policy; for our practices, see Security.

The one rule: we don’t train on your data

We do not use your prompts, code, conversations or files to train models, ours or anyone’s. We contractually require the providers we route to through Gateway not to train on your content either. Your data is used to fulfil the request you made, and nothing else.

What we use to run the product

Account. Your email, name and avatar from Google or Microsoft sign-in, plus a rotating session token, so you can log in.

Request content. When an agent runs, the relevant context is sent to the model you chose so it can answer. On Digitorn Cloud we also store the conversation so you can come back to it; in the local setups it stays on your machine.

Hub activity. If you install or publish a package, we record the action and package ID so the marketplace can show counts and your publishing history.

Product analytics. Aggregate, non-content usage (which features are used, errors) to improve the product. This never includes the content of your prompts or files.

What reaches model providers

To answer a request, the context an agent needs is sent to the model you selected with brain.model. Through Gateway, Digitorn proxies that call to the provider; with your own keys (BYOK) it goes directly and we don’t see it. You choose the model, and you can switch it any time with /model.

Retention

Cloud conversations and project data are kept until you delete them or close your account. Aggregate analytics are retained in de-identified form. In the local setups, retention is entirely up to you. The data lives in your own files.

Your controls

You can delete a conversation, a project, or your whole account from your settings. You can run Digitorn locally so your data never leaves your machine, bring your own keys to talk to providers directly, or self-host the open-source stack end to end.

Questions

Reach us at privacy@digitorn.ai.

What we use to run the product

Account. Your email, name and avatar from Google or Microsoft sign-in, plus a rotating session token, so you can log in.

Hub activity. If you install or publish a package, we record the action and package ID so the marketplace can show counts and your publishing history.

Product analytics. Aggregate, non-content usage (which features are used, errors) to improve the product. This never includes the content of your prompts or files.