Who operates Dispatch
Dispatch is operated by Zektek LLC (“Zektek,” “we,” “us,” or “our”). This policy applies to the Dispatch browser extension and our supporting extensions API at extension-api.zektek.com, which handles usage analytics and remote configuration.
Information stored in your browser
Dispatch stores the following extension data:
- your prompt library: folder names and structure, and each prompt’s title, text, tags, favorite status, and use statistics;
- which AI services are enabled and your default destination, any per-prompt destination override, your email signature, and which email services are turned on;
- whether the first-run introduction has been shown and dismissed;
- a copy of the latest remote configuration, described below;
- whether anonymous usage analytics is turned on (on by default); and
- a randomly generated analytics client identifier, plus a short-lived session identifier that expires after 30 minutes of inactivity.
Your prompt library is stored only in Chrome’s local extension storage on each device and does not sync between browsers. Your enabled destinations, default destination, email signature, and email service choices use Chrome’s synchronized extension storage and may sync through your Google account if Chrome sync is enabled. The first-run state, the remote configuration copy, the analytics on/off option, and the analytics client identifier are stored only in Chrome’s local extension storage on each device. The session identifier is stored only in Chrome’s session storage, which clears when the browser closes.
Information processed when you use Dispatch
Inserting a prompt
When you insert a prompt from the side panel, the right-click menu, or the keyboard shortcut, Dispatch inserts the prompt text into the field you have focused on a supported AI chat site. If Dispatch cannot insert directly, for example on an unsupported page, it copies the prompt to your clipboard instead. Dispatch does not read page content beyond finding and writing to that field.
Replying to email
When you run a saved prompt against an open conversation in a supported email service (Gmail, Yahoo Mail, Outlook, iCloud Mail, Proton Mail, or Fastmail), Dispatch reads the visible subject, senders, and message text of that conversation, combines it with your prompt, signature, and any additional context you type, and sends the combined request to the AI service you choose, either by opening a browser tab or, for Claude Desktop, handing it to the installed native app. Dispatch only reads the email you are actively running a prompt against, and only when you take that action.
Outlook, iCloud Mail, Proton Mail, and Fastmail stay off until you turn them on in Dispatch Options. Turning one on asks Chrome to grant Dispatch access to that service’s site, and turning it off gives that access back.
Remote configuration
Dispatch periodically checks extension-api.zektek.com for configuration such as whether support for a particular AI site or email service is temporarily turned off (for example, if that site changes its page in a way that breaks Dispatch). This is a plain request that doesn’t include your analytics identifier, your prompts, or any email content.
Limited usage analytics
When enabled, Dispatch sends anonymous usage events to our own extensions API at extension-api.zektek.com, along with your analytics client identifier, session identifier, the extension version, and which browser it runs in. The gateway adds your approximate country, which it determines from your connection, and then forwards these events to PostHog, our analytics provider. Because this forwarding happens server-side, PostHog receives the event data from our gateway rather than directly from your browser, and does not receive your IP address through this process.
These events can indicate:
- that the extension was installed;
- that the side panel was opened;
- that a prompt was inserted, or could not be inserted, on a supported AI site, which site it was, how you started it (side panel, right click menu, keyboard shortcut, or an email reply), and if it failed, why;
- that Dispatch read, or could not read, an email in a supported email service, and which service;
- that you turned an email service on or off, and whether you granted Chrome’s site access request for it; and
- that you turned usage analytics off.
Sites and services are only ever recorded by name from a fixed list of the ones Dispatch supports; any other page is recorded only as “other.” Dispatch never sends prompt text or titles, folder names, email content, page URLs, or the addresses of sites you visit through these events. You can turn usage analytics off at any time from Dispatch Options; doing so stops future events and deletes your locally stored analytics client identifier.
Importing and exporting prompts
Exporting your library creates a CSV file directly in your browser and offers it as a download; importing reads a CSV file you choose and adds its rows to your local library. Both happen entirely on your device. Dispatch does not upload your prompt library anywhere as part of either action.
Why we process this information
We use this information only to:
- insert and manage your saved prompts;
- read the email conversation you ask Dispatch to reply to;
- remember your destination and signature preferences;
- understand whether core extension features work; and
- diagnose failures and improve supported-site behavior.
We do not sell personal information, use Dispatch data for targeted advertising, or build profiles of the prompts you write or the AI chat sites you use.
Service providers and AI chat sites
Zektek operates the extensions API, which forwards usage events to PostHog, Inc., which stores them in the United States on our behalf, as described above. Dispatch requests access to supported AI chat sites and email services solely to find and write to a message editor, read an open email thread when you ask it to, and open or focus a tab for the AI service you choose.
When you insert a prompt or send an email reply request, Dispatch delivers that text directly to the AI service you selected, in your browser; Zektek does not see or store it. Your use of an AI chat site or email service, including the message that service receives after Dispatch finishes, is governed by that provider’s own terms and privacy policy. Chrome’s handling of synchronized extension options is governed by Google’s terms and privacy policy.
Retention and your choices
Analytics events are retained according to Zektek’s PostHog project settings. Your prompt library, destination, signature and email service preferences, the remote configuration copy, the local analytics client identifier, and the analytics on/off option remain in browser storage until they are deleted, changed, turned off, or the extension is removed. The analytics session identifier expires automatically after 30 minutes of inactivity or 24 hours, whichever comes first.
You can edit or delete individual prompts and folders, change which AI services are enabled and your default destination, update or remove your email signature, and turn anonymous usage analytics on or off from Dispatch Options. Turning analytics off also deletes your locally stored analytics client identifier. You can remove all locally stored extension data by uninstalling Dispatch or clearing the extension’s data in Chrome. You can use Dispatch without a Zektek account because no account is required.
How we use Chrome permissions
Google requires every Chrome extension to state this plainly: we only use the information Chrome’s APIs give us to provide or improve the features described in this policy. We don’t use it for advertising, and we don’t sell it.
Security and children
We use reasonable technical measures to protect information processed by Dispatch. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
Dispatch is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Changes to this policy
We may update this policy as Dispatch changes. We will post the revised policy here and update the effective date above. Material changes will be communicated through the extension or this page when appropriate.
Contact us
For questions, privacy requests, or concerns about Dispatch, please contact Zektek.