Last Updated: October 26, 2023
Introduction
Dispatch is a Chrome extension designed to help users send personalized bulk email campaigns directly from their own Gmail accounts. This privacy policy explains how we handle your data. Dispatch is built with a privacy-first architecture: your campaign data is stored locally on your device, and we (the developers) do not operate any servers that collect or store your personal information.
Information Handling and Storage
We do not collect, store, or transmit your personal data, recipient lists, or email contents to any developer-owned servers.
All data generated by the extension—including campaign drafts, recipient lists (CSV data), email templates, settings, and your Gmail OAuth tokens—is stored locally on your device using chrome.storage.local.
How Emails Are Sent
Dispatch operates by interfacing directly with your Gmail account.
Gmail API Mode: If you connect via the API, Dispatch uses Google's official OAuth 2.0 system. Your authentication token is stored locally. Dispatch sends requests directly to Google's Gmail API (gmail.googleapis.com) to deliver your emails.
Quick Connect Mode: If you use this mode, Dispatch opens Gmail in a background tab in your browser and uses browser automation to click "Send."
In both cases, your email content and recipient addresses are transmitted directly to Google (Gmail), not to the developer.
Optional Tracking Features (User-Hosted)
Dispatch includes optional open and click tracking features. These features are disabled by default.
If you choose to enable tracking, you must provide the URL and secret key for your own tracking server (e.g., a Cloudflare Worker). If configured, Dispatch will append invisible tracking pixels to your emails and route click links through your server. The data collected by this server is entirely controlled by you, the user. The developer of Dispatch does not have access to your tracking server or the data it collects.
Data Security
All processing happens locally in your browser. No remote code is executed; all scripts and assets are included in the extension package. Because the developer does not host any servers or databases, your data cannot be compromised on our end.
Permissions Justification
Dispatch requests the following permissions to function:
storage: Saves your campaign drafts, recipient lists, and settings locally on your device.
identity: Used to securely authenticate with Google to obtain an OAuth token if you choose the Gmail API sending method.
alarms: Allows the extension to wake up periodically to process scheduled emails and follow-ups.
notifications: Alerts you when a campaign finishes or if a send fails.
tabs: Opens background tabs to send emails via the Gmail web interface (Quick Connect mode).
Host Permissions (mail.google.com, gmail.googleapis.com): Required to inject the Dispatch button into your Gmail compose window, automate the sending process, and communicate directly with Google's API.
User Control and Data Deletion
You have full control over your data. You can pause, delete campaigns, or clear your recipient lists at any time from the Dispatch dashboard. If you uninstall the extension via Chrome's Extensions Manager (chrome://extensions), all locally stored data, including your authentication token and campaign history, is automatically erased from your browser.
Changes to This Policy
Updates to this policy will be posted here with a revised "Last Updated" date. Your continued use of the extension after any changes constitutes your acceptance of the new terms.
Contact
For any questions about this Privacy Policy, please contact us at:dravidjones114@gmail.com]