Privacy · Orbi Cloud
Privacy policy
What crosses the hosted-service boundary, and why. This policy describes the data Orbi Cloud uses to sign you in, run deliveries, measure usage, and bill subscriptions.
DATA WE USE
Only the records the service needs
When you connect Cloud, we receive GitHub account information and the repositories you authorize. Even when you sign in without installing the GitHub App, we record your GitHub username and the verified email GitHub returns, so we can reach you if provisioning gets stuck. For those repositories, the service handles repository metadata and delivery records such as Issues, pull requests, commits, and run outcomes. The control plane records tenant and repository configuration in Cloudflare D1, and records delivery usage for quota and billing operations. The website may record anonymous visitor events in its visitor_events table for site measurement: engaged when a visible page has a real interaction and reaches ten seconds, cta_click for tagged CTA clicks, section_view when a page section enters view, and scroll_depth for the maximum 25/50/75/100% scroll band. The browser sends the vid cookie, page path, event kind, and CTA, section, or depth detail; on a page visit it also sends the landing page's query string and the referring page's address, and we record both as they arrived. It does not collect form contents or mouse movements. To enforce the terms of service, we may review the Issue text and repository content involved.
Cloud delivery work temporarily runs on infrastructure we operate. A terminal delivery worktree is destroyed after a 120-minute quiet period; in-flight and recoverable worktrees are kept. Cloudflare D1 account, repository, usage, and visitor records have no automatic expiry and remain until they are no longer needed to operate the service or you request deletion. GitHub remains the source of truth for your Issues, pull requests, and releases.
SERVICE PROVIDERS
Processors that make Cloud work
Stripe processes subscription payments, invoices, and customer-portal actions; Orbi does not receive your full card number. For Cloud subscriptions without a customer-configured model key, the default model is DeepSeek’s deepseek-flash; DeepSeek receives the prompts, relevant repository context, and output needed for a delivery. With a customer-configured key, the selected model provider receives that delivery data instead. Provider retention and processing are governed by that provider’s terms. GitHub receives the GitHub actions Cloud performs through the permissions you grant.
The hosted runner runs on machines operated by Orbi at Vultr and clones the connected repository for the duration of a delivery. After a delivery reaches a terminal outcome, the worktree is destroyed after a 120-minute quiet period.
We do not sell personal information. BYOK model keys used by Cloud are stored encrypted in the control plane and exposed to the runner only when needed.
YOUR CHOICES
Access, deletion, and contact
You can revoke Orbi’s repository access in GitHub. To request deletion of your Orbi account and associated Cloud records, message a group admin privately on Telegram with your GitHub account so we can identify the records. We will explain what was deleted and what must remain in GitHub or Stripe’s systems.
For questions about this policy, deletion requests or stopping these emails, first message a group admin privately on Telegram. If you can’t use Telegram, our backup email is privacy@orbi.build. If you would rather not receive these emails, reply to one of them or write to privacy@orbi.build, and we will delete these records.
This policy describes the current Cloud implementation, including the tenants, repositories, delivery_usage, and visitor_events records. It does not promise deletion of data held independently by GitHub, Stripe, or a model provider.