Last updated: 26 October 2026.
This notice covers this website, the Windows waitlist, support email and your local Orbit workspace. Account, licence, payment and other connected services may provide additional privacy information for their own processing.
Who is responsible
Orbit is made by SpacemanCodes LTD, company number 12193639. The company’s details are available on the Companies House register.
SpacemanCodes LTD is responsible for personal information it receives through this website and support email. Contact support@orbitdesktop.com with privacy questions or requests. Your chosen AI host is responsible for its own processing under its terms and privacy policy.
Visiting this website
Cloudflare hosts and delivers this website. Loading a page or downloading a file sends ordinary network request information, including an IP address and browser headers, to the services handling that request. See Cloudflare’s privacy policy for information about its processing.
The main website at orbitdesktop.com uses Pirsch Analytics to understand website usage. Preview versions do not send Pirsch analytics. Pirsch describes its analytics as cookie-free: it uses an IP address, user-agent, date, and a site-specific salt to derive a daily visitor identifier. Its documented statistics include visited paths, referrers, browser and device information, and approximate location. Read Pirsch’s privacy documentation for the provider’s explanation of the data it processes.
If you choose a light or dark theme, the website saves that choice under theme in your browser’s local storage. This lets it remember your preference on your next visit. You can remove it by clearing this site’s browser storage. The website does not ask you to upload your Orbit workspace to browse its pages.
Windows waitlist
If you join the Windows waitlist, we store your email address, signup time and the version of the signup notice in a Cloudflare D1 database. We use your consent to send Windows availability emails. Joining does not subscribe you to a general newsletter or create an Orbit account.
We also send a signup notification containing your email address and signup time to the person managing the Windows launch. Cloudflare handles delivery to their mailbox provider. Internal delivery timestamps are stored with your waitlist entry so failed notifications can be retried.
The signup form uses a hidden spam field and a temporary rate limit based on the request’s IP address. We do not save that IP address in the waitlist. The site records a successful-signup event in Pirsch without your email address or other form contents.
Only authorised people managing the Windows launch can access or export the list. To withdraw consent and remove your address, email support@orbitdesktop.com from that address. We remove waitlist entries when requested, or within three months after the Windows launch notification. If Windows has not launched, we review the list every 12 months and remove entries we no longer need.
Your desktop workspace
Orbit saves projects, tasks, documents, notes, links, uploaded assets, and preferences locally on your Mac. Linked folders remain in their original locations. A Pro activation does not synchronise workspace content between machines. See local storage and offline use and export and import for details and backup boundaries.
Optional Git connections and AI features communicate with the services you configure. An AI client connected through MCP may send tool results to its own model provider under that client’s settings. Review those settings before granting access. MCP does not expose vault secret values or connection credentials; the MCP guide explains the access boundaries.
Support email
When you email support, we receive your email address, the message and any attachments you choose to send. Authorised people handling support use that information to answer your request, troubleshoot the issue and manage follow-up. We use an email inbox, without a separate helpdesk or ticketing service.
Our email routing and mailbox providers process correspondence to deliver and store it. The domain uses Cloudflare Email Routing. Share only what is necessary: do not email passwords, licence keys, provider tokens, recovery codes, secret values or an entire workspace when a short description is enough. See Contact Orbit for reporting guidance.
Why we use personal information
We use website request information to deliver and protect the site, and usage statistics to understand which pages and workflows are useful. Our legitimate interests are keeping the website reliable and secure, maintaining the product and understanding its use. The analytics and local theme preference described above serve those purposes.
We use support correspondence to provide the assistance you request. Where that is necessary to perform a contract with you, that is our basis for processing. For other enquiries and proportionate troubleshooting, we rely on our legitimate interests in answering questions, resolving problems and maintaining the product. We may also retain relevant records where necessary to meet a legal obligation or establish, exercise or defend a legal claim.
You do not need to send us workspace content to browse the public website. If you choose not to provide enough information to investigate a support request, we may be unable to resolve that particular issue.
Retention and deletion
- Support correspondence: we delete or anonymise resolved enquiries within 12 months after resolution, unless particular records are still needed for an active dispute or legal obligation. We retain those records only for the relevant purpose and review the need to keep them.
- Original workspace content: it remains in Orbit until you change or remove it using Orbit’s controls, subject to backups you maintain.
- AI host copies: conversation history and tool results follow the host’s retention and deletion controls. Deleting a note in Orbit does not delete a copy already shared with a host.
- Local website preference: the saved
themepreference remains in your browser until you clear it or change the setting.
Website request and security information is handled by Cloudflare under its service policies. Pirsch uses a site-specific daily identifier; its documentation describes separate user-agent storage for up to three months and controls for deleting analytics data. These provider practices are separate from the 12-month period for support enquiries. We review information we control and remove or anonymise it when no longer needed for the purposes described here.
Providers and international processing
The recipients of information described in this notice include our website hosting, analytics, email routing and mailbox service providers, and authorised people responding to support. We may also disclose necessary information to professional advisers or authorities where required for a legal obligation or a dispute.
These providers, and any AI host you choose to connect, may process information outside the UK or your country. Their linked privacy information explains their processing and locations. Contact us for details of the arrangements and any applicable safeguards for transfers we are responsible for; your AI host’s own terms and privacy controls apply to information you send to that host.
Your choices and rights
You can disconnect optional AI clients, manage original content in Orbit and use the AI host’s own chat and deletion controls. Removing original content in Orbit does not delete copies already shared with another service.
Depending on the information and the applicable law, you may have rights to access or correct it, request erasure or restriction, object to processing based on legitimate interests, or receive certain information in a portable form. If processing relies on consent, you may withdraw that consent. These rights are subject to their applicable conditions and exceptions.
To make a request about information SpacemanCodes LTD holds, email support@orbitdesktop.com. Requests about an AI host’s copies should use that host’s controls or privacy contact; Orbit cannot delete data held by another service.
You can also raise a concern with the UK Information Commissioner’s Office or your local data protection authority. You do not have to contact us first, although we welcome the opportunity to address a concern.
Changes to this notice
We will update this page when these practices change and revise the date at the top. Where required, we will provide additional notice before using personal information for a new purpose.