Skip to content

Privacy Policy

Last updated: October 28, 2026

1. Introduction

EGC Labs ("we", "us", "our") operates Agents Dispatch, including agentsdispatch.com and the desktop and mobile applications (the "Service"). This policy explains what information the Service handles, its uses and recipients, and your choices.

2. Information We Collect and Use

  • Account information: information you provide when registering, including your name and email, authentication credentials and tokens, and optional multi-factor authentication information. We use Supabase to authenticate you, secure your account, and maintain account records.
  • Billing information: subscription, entitlement and customer records used to provide paid features. Stripe processes payment details; we do not store your full card number.
  • AI content: messages, conversation history, model responses, attached images and files, and project code, file contents, tool results, screenshots and agent context accessed during a task. These may include personal information. We process this content to provide the AI features you request and save and restore sessions on your connected host.
  • Voice recordings: audio you record for dictation and its transcript, used to convert speech to text as described below.
  • Usage and diagnostics: session identifiers, timestamps, provider/model selections, platform and app version, feature and quota usage, operational errors, and support information you submit. We use these to operate, secure, troubleshoot and improve the Service, enforce usage limits, and answer support requests.
  • Support reports: when you report a problem from the app, what you write and attach (images, screenshots of the app and files) and the diagnostic details you choose to include: the app and host versions, platform, operating system and device model, connection state, your provider accounts by type and name (never keys or tokens), your default model, the chat you pick (its name, folder, model and last error), recent errors the app showed, and, if you run the host, the last lines of its logs. The app shows each item before sending and lets you turn any of them off, and it removes keys, tokens, passwords and, unless you choose to keep them, email addresses before anything leaves your device. Reports and attachments are stored in Supabase and read by EGC Labs and its AI assistant, which runs on the AI services in section 3 (normally Anthropic's Claude), to investigate and fix the problem. Replies and status changes come back to you in the app and by push notification.
  • Notifications: device delivery tokens and short response, error or permission-message previews used to deliver notifications when enabled. Previews can contain personal information and may appear on a lock screen depending on your device settings.

3. Sharing Content with AI Services

Agents Dispatch sends content through your connected host to the AI services used for your task. Recipients depend on the selected provider, model and configuration: Anthropic (Claude), OpenAI (Codex), Google (Gemini), Moonshot AI (Kimi), MiniMax, DeepSeek, Z.ai, abliteration.ai, xAI (Grok), and Meta Llama API. OpenRouter, OrcaRouter, Hugging Face, OpenCode and custom gateways can route content to additional upstream providers, including providers outside this list. Review your host and router configuration before submitting content.

These services receive messages and relevant conversation or project context, files, images, code, tool results or screenshots to generate responses, edit code and carry out tasks. Multi-agent features may share that context with each participating provider. Prompt rewriting uses the host's Codex configuration; conversation summaries send conversation text to Anthropic.

Automatic titles: when enabled, the first chat prompt is also sent through our Supabase service to OpenAI to generate a short title, even when the chat uses another provider. You can disable automatic titles in Settings.

The updated app presents an AI data-sharing disclosure and asks for express permission before entering the connected workspace. It identifies the data, purposes and recipients, with a separate optional choice for cloud audio. Permission is saved for your account on that device; an account without permission cannot enter the connected workspace.

Provider retention, training, review and international processing depend on the selected service, account and applicable agreement. Relevant information includes OpenAI business privacy, Anthropic API retention, and Google Gemini API policies. Other providers and routers have their own applicable policies. Do not submit content you are not authorized to share.

4. Voice Transcription

Cloud transcription: with your separate cloud-audio permission, recorded audio is sent through our Supabase service to OpenAI to convert speech to text. Audio may include your voice and personal information. Supabase also records usage and rate-limit information. Cloud-audio permission is off by default in the updated app and can be changed in Settings → AI data sharing.

Local transcription: when enabled on a supported host, audio is sent to that host and processed there with a downloaded speech model. It is not sent to OpenAI for transcription, and cloud-audio permission is not needed. A resulting transcript you send in chat is shared with that chat's AI providers.

5. Google Calendar and Other Chief of Staff Connections

The Chief of Staff (called the Personal Assistant in earlier versions of the app) can connect to your Google Calendar, Calendly and email. Each connection is made by you, in the Chief of Staff's settings, and is kept on the computer running your Agents Dispatch host. EGC Labs' servers never receive these credentials or the calendar, booking or email data they give access to.

Google user data

  • What we access: when you choose Sign in with Google, Google asks you to allow three things: your Google account email address, used to tell your connected accounts apart; the list of calendars you are subscribed to, so you can choose which ones the Chief of Staff includes; and the events on your calendars, so the Chief of Staff can read your upcoming events and add, change or delete an event when you ask it to. The Chief of Staff adds or changes events only when you ask and have set it to "Read, add and change events", and it deletes an event only after you approve that deletion in the app. Sign-in happens on Google's own page in your browser; Agents Dispatch never sees your Google password.
  • How we use it: only for features you see: your agenda, the morning brief, answering your questions about your schedule, and adding, changing or deleting events you ask about. We do not use Google user data for advertising, sell it, use it to build profiles, or use it to develop, improve or train generalized artificial intelligence or machine-learning models.
  • Where it is stored: the access tokens Google issues, your connected account addresses and your calendar choices are stored only in the Agents Dispatch data folder on the computer running your host, in a file readable only by your user account where the operating system supports it. Events are read from Google when needed and kept on that computer in the host's memory and in your Chief of Staff chat history. They are shown in the Agents Dispatch apps connected to your host.
  • Who it is shared with: event details the Chief of Staff reads are sent, through your own account with the AI service you chose for the Chief of Staff (see section 3), to answer you and carry out what you ask, and only after you have given AI data-sharing permission in the app. If notifications are on, a short preview of a Chief of Staff reply, which may mention an event, is delivered through our notification service (section 6). Google user data is not shared with anyone else, and no person at EGC Labs reads it unless you ask us to for support, it is needed for security, or the law requires it.
  • Protection: connections to Google use encrypted HTTPS. Sign-in uses Google's installed-app flow with PKCE, so the approval can only be completed by the host that started it.
  • Retention and deletion: a connection stays until you remove it. Disconnect in the Chief of Staff's settings revokes access with Google and deletes the stored tokens and choices from your host. You can also remove access at any time at myaccount.google.com/connections. Event details already in a Chief of Staff chat stay in that chat on your host until you delete it, and copies sent to your AI service follow that service's retention.

Agents Dispatch's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the use of information received from Google Workspace scopes will adhere to the Google Workspace API User Data and Developer Policy.

Calendly

A Calendly personal access token you paste is stored only on your host. The host reads your Calendly bookings (including who booked and their answers) directly from Calendly. The Chief of Staff uses them for your agenda, brief and requests, and shares what it reads with your chosen AI service as described above. Disconnecting removes the stored token from your host; revoke it in Calendly to end access there too.

Email

  • What is accessed: the email accounts you connect in the Chief of Staff's settings, over standard IMAP and SMTP (with an app password, or for Proton Mail the password Proton Mail Bridge shows on your computer). The host reads messages, their attachments and folder names when the Chief of Staff searches or reads, checks your inbox for new mail every few minutes, saves drafts in your Drafts folder, and sends an email only after you approve it on its card in the app. It never sends by itself.
  • How we use it: only for features you see: searching and reading mail when you or the Chief of Staff ask, sorting new mail into what needs you, your morning brief, drafts and replies you approve, and a contacts list (names, addresses and phone numbers found in email signatures and calendar invitations) kept as an editable file in the Chief of Staff's folder. Projects you choose can let their chats read the folders or labels you pick, draft, or propose emails you approve. We do not use your email for advertising, sell it, or use it to train AI models.
  • Where it is stored: account settings and passwords stay only on the computer running your host, passwords encrypted with your operating system's protection where it offers one (Windows data protection or the macOS Keychain). Short excerpts of new mail are kept on that computer until the Chief of Staff has sorted them, a week at most. Attachments the Chief of Staff opens are saved in the host's outputs folder. Nothing about your email is stored on our servers.
  • Who it is shared with: what the Chief of Staff or a project chat reads is sent, through your own account, to the AI service you chose for it (section 3), only after you have given AI data-sharing permission in the app. Push notifications for mail that needs you carry a one-line preview through our notification service (section 6). Email content is treated as information, never as instructions.
  • Retention and deletion: removing an account in the Chief of Staff's settings deletes its stored password and settings from your host; revoke the app password with your provider to end access there too. Contacts and notes stay in the Chief of Staff's folder until you edit or delete them, and mail already in a chat stays there until you delete the chat.

6. Other Service Providers and Security

  • Supabase: authentication, account and service records, and processing of title, cloud-transcription and notification requests.
  • Google Firebase and Apple Push Notification service:device tokens and notification delivery, including short AI response, error or permission-message previews. Apple's service is used on iOS.
  • Stripe: payment and subscription processing.
  • Vercel: hosting the public website.
  • Cloudflare: optional tunnels for remote host access.

Our hosted services use encrypted HTTPS connections, authenticated requests and access controls for account data. Your configured host connection and its security depend on how you deploy it; use a secure connection for remote access. Provider credentials are handled by the host. No transmission or storage method is completely secure.

7. Storage, Retention and Deletion

Session history, project work, scheduled tasks and Chief of Staff connections (section 5) are stored on the machine running your Agents Dispatch host. Archiving a session retains it for restoration; permanent deletion removes its saved session files. Host backups, other feature records and copies already sent to providers may remain separately. Provider retention follows the applicable service and account agreement; we do not promise zero retention.

Support reports, their attachments and replies are kept while they help us support you and recognize the same problem when someone else reports it, and are deleted with your account. Ask us to delete a report sooner.

You can delete your account in Settings or contact us about information we control. Account deletion removes the authentication account and associated account records and requests cancellation of active subscriptions. It does not automatically erase files on a host you control, copies retained by an AI provider or router, or records needed for legal, security or billing obligations. Use the relevant host or provider controls for those copies. We retain account and operational information as needed to provide the Service and meet these obligations.

8. Your Choices

In the updated app, you can decline AI sharing and sign out, or change permission in Settings → AI data sharing. Withdrawing AI permission disconnects this device from its sessions. It does not recall data already sent or stop work already running or scheduled independently on your host; stop or cancel that work on the host separately. Cloud audio permission can be withdrawn without disabling typed chat.

You can disable automatic titles, choose your provider and host, use local transcription, manage notifications in your device settings, choose whether the Chief of Staff may only read your calendar or also add events, disconnect Google Calendar, Calendly or email at any time, turn off any detail in a support report before sending it, and delete sessions or your account. Depending on applicable law, you may request access, correction or deletion of your personal information. Contact us below; we may need to verify your identity.

9. Changes and Contact

We will post policy changes here with an updated date and provide additional notice when required. For privacy questions or requests, email privacy@agentsdispatch.com.