Privacy Policy
The short version: the dashboard knows your email, your license, and aggregate usage counts — not what you ran. rootuno itself talks straight to the model provider and never proxies your commands through our servers.
Last updated: September 9, 2026
1. What we collect
This section covers the rootuno dashboard (dashboard.rootuno.com), which handles accounts, licensing, and billing.
- Account information — the email address you sign up with, and a securely hashed version of your password (we never store it in plain text).
- Verification & session data — short-lived, hashed codes used for email verification, two-factor login, and password resets, plus session tokens that keep you signed in.
- License and plan data — the license keys issued to your account, your current plan (free, paid, or unlimited), and aggregate usage counts (token and request totals per day) used to enforce plan limits. We do not log the content of your commands, prompts, or command output.
- Billing data — for paid plans, Mollie processes your payment and shares back a customer and subscription reference; we don't receive or store your full card details.
2. What the rootuno CLI does not send us
The rootuno CLI is not a proxy. You activate it with a license key; the CLI exchanges that key with the dashboard once for rootuno's pooled key, caches it locally (encrypted at rest with AES-256-GCM) so brief dashboard outages don't interrupt you, and from then on your prompts, commands, and command output go directly from your host to the model provider's API — none of it passes through rootuno's infrastructure, and we have no visibility into it. Activation itself only transmits your license key and basic client metadata needed to authenticate the request.
3. Third parties we rely on
- Our model provider — processes the prompts and tool calls rootuno sends while it's running, under that provider's own data-use terms.
- Mollie — handles payment processing for paid plans.
- Resend — delivers transactional email (verification codes, password resets, account notifications). We don't send marketing email through it.
- Reoon — optionally validates that a signup email address is real and not disposable, where enabled. It sees the email address only, not your password or usage data.
We don't sell your data, and we don't share it with third parties beyond what's needed to operate the Service as described above.
4. Cookies & local storage
The dashboard uses a session cookie to keep you signed in. We don't use advertising or cross-site tracking cookies. On your own host, the rootuno CLI stores its cached pooled key and config under ~/.config/rootuno/, readable only by the user running it.
5. Data retention
We keep account and usage data for as long as your account is active, plus a reasonable period afterward for billing records and abuse prevention. Verification codes and session tokens expire automatically and are not kept long-term.
6. Your rights
You can ask us to access, correct, export, or delete the personal data we hold about you by emailing [email protected]. We'll respond and act on verified requests within a reasonable time. Deleting your account revokes any active license keys issued to it.
7. Security
Passwords and verification codes are stored hashed, never in plain text. The pooled key is encrypted at rest, both on the dashboard's database and in the CLI's local cache. Sensitive configuration is kept out of version control and supplied to the dashboard service via environment variables at deploy time.
8. Children's privacy
The Service is intended for system administrators and developers, not children, and we don't knowingly collect data from anyone under 16.
9. Changes to this policy
We'll post material changes here with an updated date above. Continued use of the Service after a change constitutes acceptance of the revised policy.
10. Contact
Questions or requests about this policy can be sent to [email protected].
See also our Terms of Service.