Privacy Policy

Summary

SendGuard helps prevent accidental sends in Gmail by checking compose UI state in your browser. We do not operate a backend, perform remote mail analysis, or connect to Gmail via API or OAuth.

What SendGuard does not store

• Email body content
• Recipient email addresses
• Send history or analytics about your mail

What is stored locally

• Extension settings in chrome.storage.sync (company domains, word lists, rule toggles, theme, thresholds) — synced with Chrome profile when sync is enabled
• Gmail UI state checks in chrome.storage.local (device only)

How checks work

When you click Send (or use Ctrl/Cmd+Enter or scheduled send), SendGuard reads the visible Gmail compose DOM in your open tab and runs rules locally. No email content is uploaded to developer servers.

What we do not collect

• No Gmail API / OAuth / account linking
• No remote analysis of mail content
• No SendGuard account or subscription billing

Permissions

SendGuard may request access to mail.google.com to inject compose helpers and intercept send actions, plus storage for settings. See the Chrome Web Store listing for the exact permission set.

Data retention and deletion

Local data remains until you:

• Reset options in the extension
• Remove SendGuard, or
• Clear extension data in Chrome

Changes

We may update this policy. The “Last updated” date will change when we do.