Briskmail Privacy Policy
Last updated: September 30, 2026
Briskmail is a native macOS mail client for Gmail. This policy describes what Briskmail does with your Google data.
What Briskmail accesses
Briskmail asks for three Google OAuth scopes:
gmail.modify, which lets it read, compose and send email on your behalf and manage message state (labels, read/unread) in the Gmail account you sign in with.pubsub, which lets the app receive an instant new-mail notification instead of checking for mail on a timer (see "Where your data lives" below for exactly what that notification contains).gmail.settings.basic, which lets you create, list and delete Gmail filters from inside the app. Briskmail changes a filter or any other Gmail setting only when you ask it to.
It does not ask for access to any other Google product.
Where your data lives
Briskmail is a local application. Your email (subjects, bodies, attachments, contacts, search) is fetched from the Gmail API directly to your Mac and processed on your Mac. Briskmail does not run a server that stores your mailbox, and it does not copy your mail to a database we operate.
The one exception is push notifications: to tell you about new mail without constantly polling, Briskmail asks Gmail to publish a small notification (your account identifier and a historyId marking what changed, never a message subject or body) to a Google Cloud Pub/Sub topic we operate. Your own signed-in session then retrieves that notification directly with the pubsub permission above, which tells the app to go fetch the new message directly from Gmail to your Mac; the notification's own content is discarded after telling the app to refresh. We do not persist a log of these notifications.
What we don't do
- We do not sell your data.
- We do not use your data, or any content from your Gmail account, to serve ads.
- We do not use your data to train generalized AI or machine-learning models.
- No human at Briskmail reads your email unless you have specifically asked us to look at something to help you (for example, a support request), and only with your explicit agreement at that time.
Limited Use disclosure
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Data retention and deletion
Your Google OAuth token is stored locally on your Mac, in the macOS Keychain, and is never transmitted anywhere except to Google's own token endpoints. Signing out revokes that token with Google immediately and deletes it and any locally cached data for that account. If Google can't be reached at that moment, Briskmail still deletes everything it stored for that account on your Mac, and you can remove its access yourself at myaccount.google.com/connections. There is nothing left on our servers to delete, because nothing of yours was ever stored there: the Pub/Sub relay above sees only an account identifier and a change marker, never message content, and keeps no log.
Changes to this policy
We'll update the date at the top of this page when this policy changes and will not reduce your rights under this policy without your consent for data already collected.