Soft Send
← Back to site
Privacy Policy
Last updated: 2026-07-28
Soft Send processes only the data needed to delay and send messages you choose to queue. No server operated by Soft Send receives Google user data. Queued message data is processed in the extension and transmitted to Google's Gmail API at your request.
Google user data we access and how we use it
| Data accessed | Where it is processed or stored | Purpose |
|---|---|---|
| Recipients, subject, and HTML body of a message you choose to queue | Processed by the extension, stored temporarily in chrome.storage.local, and transmitted over HTTPS only to the Google Gmail API as a draft in your Gmail account | To create the draft, hold it for your selected delay, and ask Gmail to send or delete it when you choose |
| Gmail draft and message identifiers returned by the Gmail API | chrome.storage.local on your device | To send or delete the correct Gmail draft |
Draft identifier, thread identifier, Subject, In-Reply-To, and References headers of a reply you choose to queue | Retrieved temporarily from the Gmail Drafts API in metadata-only format and processed in extension memory | To keep the queued reply in its original Gmail conversation; this metadata is not retained separately |
| OAuth access token | Requested and managed by Chrome's identity API | To authorize the draft create, reply metadata lookup, send, and delete requests made to the Gmail API |
| Addresses used in messages sent through Soft Send | chrome.storage.local on your device | To determine whether a recipient is new |
| Daily counters (sent / saved) | chrome.storage.local on your device | Shown in the popup |
| Your settings, including any high-risk addresses or domains you enter | chrome.storage.sync, which Google may sync through your Chrome profile when Chrome Sync is enabled | To apply your preferences across Chrome browsers where you are signed in |
Soft Send does not list or read your inbox messages. When you choose to queue a reply, it briefly lists recent Gmail drafts and retrieves metadata for candidate drafts to identify the matching conversation. It uses only the draft identifier, thread identifier, Subject, In-Reply-To, and References headers. The API request uses metadata-only format and does not return the draft body.
Sharing, transfer, and disclosure
Soft Send discloses Google user data only as follows:
- Google Gmail API: recipients, subject, body, and the resulting Gmail draft identifiers are transmitted to Google only to create, send, or delete the queued draft in your Gmail account. For a reply, Soft Send also retrieves the metadata described above to preserve the Gmail conversation.
- Google Chrome Sync: if you enable Chrome Sync, Google may sync your Soft Send settings, including high-risk addresses or domains that you enter, through your Chrome profile.
- No other third parties: Soft Send does not share, transfer, or disclose Google user data to ExtensionPay, Stripe, advertisers, analytics providers, data brokers, information resellers, or any other third party.
ExtensionPay and Stripe process the optional Pro purchase. Soft Send receives and stores only a paid or unpaid status. They do not receive Gmail message content, recipients, Gmail identifiers, contact history, settings, or OAuth tokens from Soft Send.
There is no Soft Send server, email relay, advertising service, or analytics endpoint. No Soft Send employee or contractor has access to Google user data because that data is not sent to infrastructure operated by Soft Send.
For ExtensionPay's own handling of payment data, see their privacy policy at https://extensionpay.com/privacy.
Data protection and security
- All Gmail API requests use HTTPS/TLS encryption in transit.
- OAuth tokens are obtained and cached by Chrome's
identityAPI. Soft Send does not write tokens to extension storage, include them in logs, or transmit them anywhere except to Google's Gmail API in the authorization header. - Queued data is kept in Chrome extension storage associated with the user's browser profile. Soft Send does not copy it to a developer-controlled server.
- The extension requests only the
gmail.composescope and calls only the Gmail draft endpoints required to create, find reply metadata, send, and delete Soft Send drafts. - All executable code is packaged with the extension. A Manifest V3 Content Security Policy restricts extension pages to scripts included in the installed package and blocks remote executable code.
- Access is limited by Chrome's extension permission model. Users should also protect their device and Chrome profile with appropriate operating-system access controls.
Soft Send does not separately encrypt data stored in the local Chrome profile. The strongest protection is data minimization: no Google user data is copied to a Soft Send server, and queued message data is removed from the local queue when it is sent or cancelled.
Limited Use compliance
Soft Send's use of information received from Google Workspace APIs adheres to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
Google user data is used only to provide the visible delayed-send, cancellation, editing, risk-warning, and send features requested by the user. It is never sold, used for advertising, used to determine creditworthiness, provided to data brokers or information resellers, or used to train general-purpose artificial intelligence or machine-learning models.
Permissions and why they're needed
storage: persists the queue, contact history, stats, and settings locally.identity: obtains an OAuth token so the Gmail API can act on your mailbox.alarms: wakes the service worker every 30s to process the queue.notifications: tells you if an email failed to send.host_permissions: https://www.googleapis.com/*: calls the Gmail API.host_permissions: https://extensionpay.com/*: processes the optional Pro upgrade and checks paid status (no email content is ever sent there).- Content script on
https://mail.google.com/*: intercepts the Send button and renders the queue banner inside Gmail.
Gmail API scope
Soft Send requests a single scope: https://www.googleapis.com/auth/gmail.compose. This is required to create, list, retrieve metadata for, send, and delete drafts. Soft Send uses this permission only for messages you explicitly queue through the extension. It does not list or read inbox messages. For replies, it retrieves metadata-only draft responses as described above and does not retrieve draft bodies.
Data retention and deletion
- A queue entry, including recipients, subject, body, timing data, risk warnings, and Gmail draft identifiers, remains in local Chrome storage until the message is sent or cancelled. A paused message remains until you resume or cancel it.
- When a queued message is sent or cancelled, Soft Send deletes its local queue entry. Cancelling also asks Gmail to delete the associated draft.
- If sending fails after the built-in retry, Soft Send removes the local queue entry but leaves the message as a draft in your Gmail account so you do not lose it. You can edit or delete that draft in Gmail.
- Recipient history, counters, and settings remain in Chrome extension storage until you clear the extension's storage or remove the extension. Synced settings are also subject to your Google Chrome Sync settings.
- Removing Soft Send or clearing its extension storage deletes data stored locally by Soft Send. Soft Send has no server-side copy to delete.
- To revoke Gmail API access, remove Soft Send from your Google Account connections. Revoking access does not itself delete drafts already stored in Gmail; those can be deleted from Gmail.
Contact
For privacy questions or help deleting locally stored Soft Send data, contact softsend.review@gmail.com.