Legal

Privacy

orra runs on your computer. This page tells what stays there, what goes over the network, and what this website and the payment service keep.

What stays on your computer

• Agents, conversations, queues, attachments, memories, routines, channels and settings. They live in a local database in the app data folder and in the agent workspaces under ~/Orra.
• The data of the built-in browser: tabs, cookies and sign-ins.
• API keys, provider tokens and Vault items. orra encrypts them with the operating system's secret store before it saves them.
• Your account. orra has a local account on this computer. There is no account service, no sign-in with an email code and no cloud relay.

What orra sends over the network

The app sends no telemetry, analytics or crash reports. The network traffic comes from the things you set up:

• Model providers. The providers you connect (for example Claude, Codex, Grok or a custom endpoint) receive your prompts, the files agents read and the tool results. That provider's own terms and privacy policy apply.
• Provider and tool downloads. When you choose Download, orra gets a pinned provider CLI from its publisher and checks its digest. Voice models come from Hugging Face.
• The built-in browser. Pages that you or an agent open connect to their sites.
• MCP servers, plugins and connectors. A server or plugin you add connects to its own service.
• Servers you join or publish. Team data goes to the members of that server only.

Diagnostics

A diagnostics export stays a local file until you send it yourself. orra removes secrets from logs and exports.

This website

This site sets no cookies and runs no analytics.

Buying a pack

When you pay for a pack, the payment service keeps the contact you enter (an email or a Telegram handle) and the order: the pack, the exact amount, the time and the transaction once it arrives. The contact goes only to the person who hands over the pack. The payment itself is a USDT transfer on the TRON network, which is public by design.