Private by default. Clear by design.

Workspace chats, projects and operational state live in a local SQLite database on the host computer. A connected device can access that host with your authorization. Optional Orutta account features store profile information, private usage aggregates and saved Inbox recaps in our account database on PostgreSQL/Supabase, accessed through our Cloudflare API. These saved account records are separate from product analytics.

In the hosted app at app.orutta.com, your workspace runs in a cloud workspace we operate on Google Cloud. Your account, organization membership, encrypted connector tokens and a copy of your cloud chats are stored in our control-plane database, and files you attach or that a connector fetches for you are stored in our Google Cloud Storage bucket under your account.

The host computer connects directly to the provider you chose — Claude, Codex, OpenCode, Cursor, Antigravity, Grok, Droid, and so on — using your own existing logins. That provider receives the prompts and code needed for the session, governed by their privacy terms. Orutta does not proxy normal provider requests through its own model service. For managed remote connections, Cloudflare transports chat and file traffic between your approved device and the host before the host contacts the provider.

Local desktop use does not require a Orutta account. Signing in enables account features and managed device connections. Authentication uses WorkOS; the hosted app at app.orutta.com uses Google sign-in. The account API and managed tunnels use Cloudflare. Approved devices can access the selected host, including its chats and files, through that connection. You can revoke device access. Information you choose to publish on your profile is public; saved Inbox recaps are private.

You can also connect your own Google Drive, Gmail and GitHub accounts as connectors. Each person connects their own accounts; nobody else's connection is shared with you, and no one connects an account on your behalf. How we handle data from Google is described in Google user data.

Orutta asks for access to your Google account when you sign in to the hosted app with Google, and when you connect Google Drive or Gmail in Orutta's connector settings. You choose which connectors to connect, and you can disconnect them at any time.

• Google sign-in (openid, email, profile): your name, email address, profile photo and, for Google Workspace accounts, your organization's domain, used to create your account and add you to your organization. Members of your organization can see your name, email and photo.
• Google Drive (https://www.googleapis.com/auth/drive): so the agent can search and read your files, read and edit Google Sheets, and, when you ask, create, upload, update, share or move files to the trash in your Drive.
• Gmail (https://www.googleapis.com/auth/gmail.modify): so the agent can search and read your email and attachments and, when you ask, draft, send, label or move messages to the trash. Orutta cannot permanently delete email.
• Basic profile (openid, email): for the Drive and Gmail connectors only, to show which Google account is connected.

How we use it. Google data is used only to provide the features you request. Orutta does not copy or index your whole Drive or mailbox; it fetches only the items a request needs. When you ask the agent for something that needs Drive or Gmail, it calls Google at that moment with your own connection, so Google decides what you can see. The agent changes or sends something only when you asked for it.

Storage and security. Your Google access and refresh tokens are encrypted at rest; Orutta refuses to store them at all when encryption is not configured. What a connector returns for a request becomes part of that chat, which is stored with your chat history (in the hosted app, also in our control-plane copy of your cloud chats). Drive files (such as PDFs, Office documents and images) and Gmail attachments the agent opens are kept as your attachment in our storage and copied into your cloud workspace so the agent can read them and you can download them.

Sharing. We do not sell Google user data and do not use it for advertising, to build user profiles, or to train AI models. When your request needs Google data, the agent passes the relevant content to the AI provider you chose and connected with your own account (for example Anthropic for Claude or OpenAI for Codex) so it can answer, governed by that provider's terms. We also transfer it to people you choose, when you ask the agent to share a Drive file or send an email, or when you share a file or chat with colleagues in Orutta. Otherwise we transfer it only to service providers that run Orutta for you (such as Google Cloud hosting), when required by law, or as part of a merger or acquisition with notice to you.

Human access. No person at Orutta reads your Google data unless you give us permission (for example in a support request), it is necessary for security purposes such as investigating abuse, or it is required to comply with applicable law.

Revoking access and deletion. Disconnect Google Drive or Gmail in Orutta's connector settings: Orutta deletes the stored tokens and revokes its access with Google (if both connectors use the same Google account, access is revoked when you disconnect the second). You can also remove Orutta at myaccount.google.com/permissions. To have chats, stored attachments or your account deleted, email privacy@orutta.com.

Orutta's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Desktop Stable, Beta and the native mobile apps can send limited product events to our Cloudflare service when you enable Share product analytics in Settings. Consent is local to each installation, off by default, and independent of your account or another connected device. The random installation identifier allows events from that consenting installation to be grouped; it is not your account identity.

Events are stored in a separate Cloudflare D1 table with a 30-day raw-data retention policy and an authenticated dashboard. Turning collection off clears unsent events, cancels uploads where possible and removes the local analytics identifier. It cannot retract events already received. Re-enabling creates a new identifier. Usage counters are best-effort observations, not billing records or complete account usage totals.

Orutta Beta sends crash, error, release-health and daily usage diagnostics automatically. These may include bounded, redacted error stacks, log excerpts and recent diagnostic context. Stable does not send Beta diagnostics. Product analytics consent does not control this separate Beta path, whose retention policy is independent of the 30-day product-event policy. See the diagnostics documentation for its field allowlist and storage details.

The in-app Feedback Orutta dialog sends only when you press Submit. It includes the text you wrote, app version, operating system, provider and model, runtime modes, and session/turn status so we can understand the conditions around a problem.

Feedback context excludes chat messages, prompts, project paths, repository contents, session logs and screenshots. Feedback reports are delivered through our website and email provider to the Orutta maintainer for support and product improvement, rather than being added to an analytics profile.

Orutta is open source under the MIT license. If a sentence on this page isn't enough, you can verify every claim yourself — read the code on GitHub.

This marketing site (the page you're reading) uses privacy- friendly Cloudflare Web Analytics for anonymous, aggregate visit counts. No cookies, no cross-site tracking, no selling of data.