Your intent is not content for a feed.

Data we handle

Account information, profile context, agent goals and permissions, agent conversation history and source links, match feedback, prepared messages, approvals, provider acknowledgements, outcome records, subscription state, usage records, and limited operational logs. Pilot workspaces also store organization contacts and submitted requests. OAuth tokens are encrypted at rest and are never returned to the browser. Orbit does not accept personal model API keys.

• Raw microphone audio is not intentionally retained by the current browser-voice path.
• Payment card details are handled by the configured payment provider and are not collected or stored by Orbit.
• Sensitive request content is not sent to product analytics.

Why we use it

We use data to authenticate users, hold requested conversations, perform requested discovery, explain matches, enforce approvals, operate pilots, prevent abuse, and improve outcome quality. We do not sell personal data.

Sharing and subprocessors

The beta is hosted using Vercel, Render, and managed PostgreSQL infrastructure. Permitted public job sources may be queried. Browser speech features may use services built into the user’s browser. On live plans, agent messages and recent conversation context are sent to Orbit’s configured model provider. Managed web research may query public sources. Provider-side response storage is disabled where supported. Model replies cannot grant action authority. Optional voice, Gmail, or X services are used only when configured and authorized. Gmail receives the recipient, subject, and message only when you approve a send. The payment provider receives the information needed to create and manage a subscription.

Control and retention

Signed-in users can export or delete their account from the product. The export includes agent conversation history. Pilot participants can ask for correction or deletion by email. Operational backups and security records may persist for a limited period after deletion where necessary.

Your choices

You can pause or delete agents, reject an action, disconnect a connector, decline introductions, avoid browser voice, leave Web search off, withdraw from a pilot, export your data, or delete your account. Disconnecting deletes Orbit’s stored authorization; use the provider account settings when you also want provider-side revocation. Contact us for privacy requests that cannot be completed in-product.