SendLock Privacy Policy

Last updated: November 2025

We take your privacy seriously. Here's the plain-English truth about what SendLock does (and doesn't) do with your data.

1. What We Collect

We keep it lean. SendLock only stores the bare minimum to make the magic happen:

• User preferences — your chosen delay duration, trial/license status, and simple UI settings.
• Edit counts — how many times you tweak an email before hitting send (because progress matters).

What we DO NOT collect:

• The actual content of your emails.
• Your contacts' names or addresses.

We NEVER read, collect, or store any of your emails (or anything in gmail.) We take privacy seriously.

2. Where It Lives

All settings are stored with chrome.storage.sync so your preferences follow you on any Chrome profile you're signed into.

No shady servers. No mysterious data lakes. Just your browser.

3. Why We Need Permissions

Some Chrome permissions sound scary, so here's why we use them:

• Storage — so your delay setting and license info don't vanish every time you close Chrome.
• Identity (if used) — only for secure sign-in and license verification.
• Host permission (https://mail.google.com/*) — so we can gently step between you and the "Send" button, give you that 60-second safety net, and pop up a cancel/confirm banner.

We don't ask for anything we don't need, and we never sell your data.

4. What We Share

Short answer: Nothing.

Long answer: We don't sell, rent, trade, or "accidentally leak" your information. The only time data leaves your browser is if it's absolutely required for license verification or if the law says we have to (hello, court order).

5. Security

We use industry-standard security practices. Translation: if hackers want your SendLock settings, they'll be bored to tears.

6. Changes to This Policy

If we ever change what we collect or how we handle it, we'll update this page and you'll see a new "Last Updated" date up top. No sneaky changes.

7. Data Retention & Deletion

SendLock does not store, retain, or transmit any Gmail message content or Google user data to our servers.

All email processing occurs locally within the user's browser.

SendLock does not collect or store:

• Email bodies
• Inbox messages
• Attachments
• Subject lines
• Metadata
• Recipient information
• Any Gmail content of any kind

SendLock stores one simple, anonymous usage metric:

How many times SendLock has helped the user by delaying an email they edited or canceled.

This metric contains no email content, no message details, and no personally identifiable Gmail data.

It exists only so the user can see how many times SendLock has protected them from sending mistakes.

Users can revoke SendLock's access at any time at:

https://myaccount.google.com/permissions

If a user uninstalls SendLock or revokes access, all OAuth tokens and extension data stored locally are immediately removed or invalidated.

Because SendLock does not store Gmail message content or Google user data on its servers, there is no retained Google data to delete.