Privacy Policy
Last updated 2 November 2026
The short version. Agent Orchestrator runs on your own machine. We never see your source code, prompts, agent output, terminal contents, repository names or file paths, and we never sell or rent data to anyone.
To keep AO stable and to understand how it is used, the desktop app, CLI and mobile app send usage analytics to PostHog. The desktop app, its daemon and AO Mobile send error reports to Sentry. Desktop usage analytics and error reports are on by default, with separate switches in Settings. A paired phone follows the desktop usage analytics switch for its usage analytics and error reports. Reports and usage events are stripped of paths, names and content before they leave your device. Usage events are tied to a random install ID and, when available, to your GitHub username, so they are not anonymous.
Website analytics stay off until you make a choice. If you decline, PostHog records limited cookieless activity counts without a browser identifier. If you voluntarily join a waitlist or send us a testimonial, we use the details you submit only for the purpose described on that form.
What this policy covers
Agent Orchestrator ("AO") is open-source software published by Untrivial, Inc., doing business as Orchestrator.inc. This policy applies to:
- AO Mobile — the companion app for iOS and Android that connects to an AO daemon you run yourself.
- The AO desktop app and CLI — the local orchestrator that supervises coding agents in git worktrees on your computer.
- orchestrator.inc — this website and the documentation hosted on it.
The desktop app and CLI run locally and do not require an Orchestrator Cloud account. Orchestrator Cloud is a separate hosted service with accounts. This policy covers the local app, its telemetry, AO Mobile and this website. It does not describe data handled by the hosted Orchestrator Cloud service. Repositories, worktrees, sessions, terminals and agent output orchestrated locally stay on hardware you control.
The AI coding agents you run inside AO (Claude Code, Codex, Cursor, and others) are separate third-party tools with their own privacy policies. AO launches them locally; it does not intercept, store, or forward what they send to their own providers.
AO Mobile (iOS and Android)
AO Mobile lets you monitor and control an AO daemon that you run yourself, over your local network or a private network such as Tailscale. The app has no backend of its own; it talks only to the server you configure.
Data the app handles
- Server connection details. The host or address and port of your AO server, plus the connection password. The address and port are stored in the app's local storage; the password is stored in the device's secure keychain (iOS Keychain / Android Keystore). Both are sent only to the server you configure, in order to connect.
- Camera (QR pairing). With your permission, the camera is used solely to scan the pairing QR code shown by your server. No photos or video are stored, uploaded, or retained.
- Push notification token. To deliver notifications — for example when an agent is waiting for your input — the app requests a push token from the platform and registers it with your own server, so your server can notify you. The token is not sent anywhere else.
- Device model and OS version. Read on-device to request a valid push token and to render the interface correctly. Not transmitted to us.
- Agent and project data. Sessions, pull-request state, and terminal output are fetched from your own server for display. That data lives on your server; the app displays it and sends it nowhere else.
How notifications work
When your server sends you a notification, it is relayed by the Expo Push Service to Apple Push Notification service (APNs) on iOS or Firebase Cloud Messaging (FCM) on Android, which deliver it to your device. The payload contains only what is needed to display and open the notification — a short title and body, and identifiers such as a session or pull-request reference. No passwords, tokens, or secrets are included. These platform services process the message only to deliver it, under their own privacy policies.
AO Mobile sends usage analytics to PostHog: app opens, pairing and onboarding steps, notification opens, and which features you use, plus the app version and platform. These events are linked to the desktop install you paired with. They never include server addresses, passwords, push tokens, session content, terminal output or pull-request details. AO Mobile contains no advertising SDKs and does not track you across other companies' apps or websites. Turning off Share usage analytics on the paired desktop also stops the phone's events the next time it connects.
Desktop app and CLI
The desktop app and CLI run entirely on your machine. All application state, including projects, worktrees, sessions, terminal history and settings, is written under ~/.ao on your own disk and is never uploaded to us.
Usage analytics (PostHog)
To understand reliability and which features are used, AO sends usage events to PostHog ( privacy policy):
- App activation, screen views grouped into coarse surface names, and coarse UI actions such as creating a task, starting a session or adding a project.
- Operational events from the local daemon: command invocation, session start and failure, waiting-for-input transitions, and updates.
- Usage counts. The number of messages you send in each session, and the number of pull requests linked to and merged by AO agents. These are counts only. They never include message content, pull-request URLs, titles, repositories or branches.
- AO version, release channel, operating system platform and build mode.
What identifies you. Every event carries a random install ID, generated on first run and stored at ~/.ao/data/telemetry_install_id. If AO's GitHub integration is connected, events also carry the GitHub username of your personal account (never an organization or bot), as an event property and a PostHog person property. If you sign in to Orchestrator Cloud, events also carry your Orchestrator Cloud account ID. Usage events do not include your email address as an event property. If you sign in to Orchestrator Cloud, your email address is stored on your PostHog analytics person profile.
Before anything leaves your machine:
- Absolute file paths (
/Users/…,/home/…,C:\…) are replaced with[redacted-local-path]. - Local URLs (
file://,localhost,127.0.0.1) are replaced with[redacted-local-url]. - Project and session identifiers are either one-way hashed (SHA-256) or replaced by a random ID created on your machine. Project names, session names and repository names are never sent.
- Daemon events pass through a strict allowlist, so only known-safe fields are exported.
Approximate location (country, and where available region and city) is derived by PostHog from the connection's IP address when each event is received. AO uses it only in aggregate. AO never resolves or sends precise location and does not store your IP address. Turning usage analytics off stops it along with everything else.
The desktop app does not currently send PostHog session recordings. If a time-boxed investigation ever enables them, local paths, local URLs and network request names are masked before transmission. Recordings would cover the AO interface only: never other applications, never your desktop, and never keystroke content.
Turning it off
Usage analytics and error reports are on by default. You can turn each off at any time in Settings with Share usage analytics and Share error events. Turning one off stops sending straight away and deletes anything still queued on your machine. A choice you made before stays in place after updates.
You can also stop daemon events by setting AO_TELEMETRY_EVENTS=off and AO_TELEMETRY_REMOTE=off in the daemon's environment. Development builds send nothing. Because AO is open source, you can also build it yourself without the analytics or error-reporting keys. See docs/telemetry.md for the full, source-level detail.
If you connect a GitHub account for pull-request and CI awareness, AO uses your existing local GitHub credentials to talk to GitHub directly from your machine. Those credentials stay on your machine and are never sent to us.
Error reports (Sentry)
When something breaks, the desktop app, its local daemon and AO Mobile send an error report to Sentry ( privacy policy) so we can find and fix the bug. Sentry stores the reports in the United States.
What a report contains:
- A fixed error title chosen by AO, such as "HTTP server error", plus an allowlisted error code.
- The type of exception (for example
TypeError) and the names and line numbers of AO's own functions where it happened. - For daemon request failures, the route template (for example
/api/v1/sessions/:id), never the actual IDs. - AO version, release channel (stable or nightly), operating system platform, and a coarse area tag such as git, database, agent or network.
- Your random install ID, so we can tell how many installs a bug affects.
Desktop and daemon reports use these fixed fields. AO Mobile reports cover reportable JavaScript, screen rendering and API failures. They carry fixed safe titles, coarse error codes and operation tags, and the paired desktop install ID when available. AO Mobile does not send native crash reports.
What a report never contains: raw error messages, file paths, project, session, repository or branch names, request bodies, prompts, agent output, terminal contents, or environment variables. AO builds every report from fixed labels and strips everything else before sending.
Sentry derives approximate location, such as country and city, from the connection's IP address when it receives a report.
If the desktop app is offline, reports wait in a small queue under ~/.ao and are sent later. Turning off Share error events in Settings stops sending and deletes that queue. Turning off Share usage analytics on the paired desktop also stops mobile error reports when the phone next connects. Development desktop builds send no error reports.
This website
orchestrator.inc is a static site and displays no third-party ads. Analytics stays off until you make a choice. If you accept the Analytics category, PostHog uses cookies to understand site usage and improve the experience. If you decline, PostHog records limited cookieless pageview and download activity without a browser identifier. No PostHog person profile is created and session recording is disabled on the marketing site. Your Analytics choice, the consent-policy version, and the time of your decision are stored in your browser's local storage.
Use Cookie Settings in the footer to review or withdraw your Analytics choice at any time. Withdrawal stops cookie-based analytics, but limited cookieless counts continue. It does not automatically erase information collected before withdrawal.
Optional waitlists and testimonial submissions are separate from analytics. When you submit one, the details requested by that form are sent to the relevant submission endpoint and stored solely to manage that request. If you accepted Analytics, the Orchestrator Cloud waitlist sends PostHog a signup event with your selected agents, parallel agent count and team size, but no email or social profile. If you declined, it sends no signup event. Submitting a form does not change your Analytics choice. Testimonial submissions include the testimonial, your public LinkedIn profile URL, and any optional public X post URL. We use those details to review and, with the permission granted on the form, publish your testimonial with public attribution on the AO website. Fonts are self-hosted. Other services involved when you browse are:
- GitHub. Your browser requests the public repository's star count and latest release from the GitHub API, which means GitHub sees the request.
- Mux. The product demo is played through an embedded Mux video player, which loads only when the page containing it is viewed.
Our hosting provider may keep standard server logs (IP address, user agent, requested URL) for security and abuse prevention, as any web server does. We do not use those logs to build profiles.
Data we do not collect
- Your source code, diffs, commits or repository contents.
- Your prompts, agent conversations or agent output, including the text of messages you send.
- Terminal contents, command history or environment variables.
- File paths, project names, branch names or repository names.
- Pull-request URLs or titles.
- API keys, tokens, passwords or any other credential.
- Precise GPS or device location.
We do not sell or rent personal data. Service providers process data only for the purposes described in this policy.
Third-party services
AO relies on a small number of services, each only to make a specific feature work:
- PostHog: usage analytics for the desktop app, CLI, mobile app and website ( privacy policy).
- Neon: stores voluntarily submitted Orchestrator Cloud waitlist details.
- Sentry: error reports from the desktop app, its daemon and AO Mobile, stored in the United States ( privacy policy).
- Expo Push Service: relays mobile push notifications ( privacy policy).
- Apple Push Notification service: delivers notifications on iOS ( privacy policy).
- Firebase Cloud Messaging (Google): delivers notifications on Android ( privacy policy).
- GitHub: hosts the source code, releases and this website ( privacy statement).
- Mux: serves the demo video on this site ( privacy policy).
Storage and security
On desktop, all AO state is stored under ~/.ao on your own machine, protected by your operating system's file permissions. On mobile, configuration is stored in app-local storage and the connection password is held in the platform secure keychain rather than in plaintext.
AO Mobile connects over the address and transport (HTTP or HTTPS) you configure. The optional LAN listener that serves the mobile app binds to your network only while you explicitly enable it, and always requires the connection password. Because the server is one you run, you are responsible for securing that machine and the network it is reachable over. We recommend a private network such as Tailscale rather than exposing the daemon to the public internet.
No system is perfectly secure, but because AO holds no central store of your data, there is no AO-side database of user content that could be breached.
Data retention and deletion
- On your devices. Data stays until you delete it. Uninstalling the mobile app, or clearing its data, removes stored settings and the keychain entry and invalidates the push token registered with your server. Deleting
~/.aoremoves all desktop state, including any queued error reports. - Local daemon telemetry. Kept in a local SQLite database for 30 days, then discarded.
- Usage analytics. Kept by PostHog under its standard retention schedule.
- Error reports. Kept by Sentry for 90 days, then deleted automatically.
- Waitlist details. Kept in the waitlist database while needed to notify you about the relevant release, then deleted. You can ask for earlier deletion at the address below.
- Testimonial submissions. Kept while they are reviewed or shown on the AO website, including the public LinkedIn and optional X post URLs you supplied. You can ask for deletion at the address below.
Your rights
Depending on where you live, you may have rights to access, correct, export or delete personal data about you, and to object to certain processing, for example under the GDPR or the CCPA/CPRA.
For users in the EU, UK and EEA, we process usage analytics and error reports on the basis of our legitimate interest in keeping AO reliable and understanding how it is used. That is why they are on by default. You can object at any time by turning them off in Settings, which stops all further collection.
Product data stays in your hands: delete the app, delete ~/.ao, and it is gone. To ask for access to or deletion of analytics or error reports tied to your install ID or GitHub username, or of a waitlist or testimonial submission, email prateek@orchestrator.inc. Including your install ID (from ~/.ao/data/telemetry_install_id) or GitHub username helps us find the right records.
Children
AO is a developer tool intended for professional and hobbyist software developers. It is not directed to children under 13, and we do not knowingly collect personal information from children.
Changes to this policy
We may update this policy as AO evolves. Material changes will be reflected here with a new "last updated" date, and the history of every revision is public in the project's git repository.
Contact
Send privacy requests, or anything you do not want to make public, to prateek@orchestrator.inc. General questions and corrections can also use these public channels:
- Open a GitHub issue — the fastest route, and the one we monitor.
- Join the Discord — for questions that are not a bug report.
Agent Orchestrator is open-source software released under Apache 2.0 and provided as-is. If this policy and the source code ever disagree, the source code is the truth — and you are welcome to read it.