Orbtile watches your coding agents, so it's fair to ask what it sends home. The short answer: counts and settings, never what you or your agents write. Here's the long answer.
What's in a usage summary
Release builds send a small usage summary by default. It covers one day at a time and contains:
- the app version, the operating system and its version, the processor type and the interface language;
- whether a supported keypad was connected, how often Orbtile started and how many minutes it ran;
- for each built-in agent: whether it's on, how many sessions and helper agents it had, the most at once, and its busy minutes;
- the names of the AI models used, with minutes per model;
- which features and settings were used, keypad Allow and Deny counts, and error counts by type.
Our server adds the country the request came from.
What's never in it
No prompts, no transcripts, no source code and no task text. Each summary carries a pseudonymous machine ID instead of anything about you. On a Mac, it's an Orbtile-specific hash of the hardware UUID: it lets us count computers and see how use changes over time, and it can't be turned back into the UUID. On Windows, the same hash is taken of the PC's Windows machine identifier (MachineGuid).
Why we collect it
Orbtile is in beta. The summaries show us which agents people run, which features they use and where errors happen, so we know what to fix and what to build next.
How to turn it off
On a Mac or a Windows PC, open Settings > General > Privacy and turn off Send usage summary. Orbtile stops sending summaries, deletes its local report file and asks our server to delete the reports it already sent, retrying until the server confirms.
The once-a-day beta status check still runs: it tells Orbtile whether a newer version is needed. With usage summaries off, it carries no identifier.
Orbtile Enterprise sends none of this. The full detail, including retention, is in the privacy notice.