Trust

Security & privacy

SendPermit touches one of your most sensitive surfaces: email. This page states what we access, why, and what we avoid.

Gmail access

We connect with Google OAuth. For the product described in our public materials, that includes permissions to read and modify labels/messages and manage basic settings so we can install the single routing filter the product relies on. Exact scopes appear in the Google consent screen when you connect.

Google may require app verification for sensitive Gmail scopes. That process exists to protect users; we submit for review as required.

Data minimization

Our design goal is to route mail using metadata (e.g. sender, subject, headers) and keep message bodies and attachments in Gmail — not copied onto SendPermit infrastructure for storage. Payment activity is handled by our payments provider; we retain only what we need to operate billing.

What we store

• Account and settings needed to run the product.
• Allowlist / verification state for sender addresses.
• Operational logs as required for security and reliability (not a copy of your mailbox).

Sender challenge mail

Challenge messages are sent from [email protected] so your personal “Sent” folder and reputation are not burdened by automated notices.

Your controls

• Disconnect Gmail and revoke OAuth access from your Google Account at any time.
• Contact [email protected] for privacy requests.

This page is a plain-language summary. The Privacy Policy and Terms govern legally.