Skip to content
Briskmail
Get early access

Briskmail Legal

Briskmail Privacy Policy

Last updated: November 14, 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.
  • gmail.settings.basic, which lets you create, list and delete Gmail filters, list your verified forwarding addresses so a filter can forward mail, and edit your Gmail signatures from inside the app. Briskmail changes a filter, a signature or any other Gmail setting only when you ask it to.
  • userinfo.profile, your basic Google profile information (your name and profile picture). Briskmail uses it only to show your account's photo in the app's sidebar. The picture is downloaded once a day at most and stored only on your Mac, in that account's own folder, and it is deleted when you remove the account. Your name and picture are never sent anywhere else.

It does not ask for access to any other Google product.

Where your data lives

Briskmail fetches your email (subjects, bodies, attachments, contacts, search) from the Gmail API directly to your Mac and processes it there. If you choose an external AI provider for Triage and consent to the transfer described below, your Mac also sends that provider limited message content and metadata for sorting. Briskmail does not run a server that stores your mailbox, and it does not copy your mail to a database we operate.

Briskmail finds new mail by asking the Gmail API what has changed: every few seconds while you are using the app, and about once a minute while it sits in the background. It does not ask for any Google Cloud permission, and no notification about your mailbox passes through a service we operate.

Contacts on your Mac

Briskmail can show your contacts' photos beside their mail. This is off until you turn on Settings ▸ Appearance ▸ Contact photos; macOS then asks whether Briskmail may read your Contacts. Briskmail looks up each sender's email address in the Contacts app on your Mac and reads only that contact's email addresses and photo. It does not change your contacts, and it does not send them, their photos or the lookup to Google, to us or to anyone else. Photos are kept in memory while the app runs and are never written to disk. If you allow Contacts access, Briskmail may also use it on your Mac to check whether an automatic send from a program you allowed addresses someone already in your contacts. You can turn off access at any time in System Settings ▸ Privacy & Security ▸ Contacts.

Calendar on your Mac

An event card, such as a meeting invite, can show whether its time is free. This is off until you press Check availability on a card and agree to Briskmail's explanation; macOS then asks whether Briskmail may read your Calendar. Briskmail reads the events on that card's day from the Calendar app on your Mac and uses only their titles, to show "No events on this date" or "Conflicts with" and the title of an event that day. It does not add, change or delete events, and it does not send your calendar, its events or the result to Google, to us or to anyone else. The result is shown on the card and is not saved. Add to Calendar does not use this access: it opens the event in the Calendar app, which asks you before adding it. You can turn off access at any time in System Settings ▸ Privacy & Security ▸ Calendars.

Optional AI sorting

Triage can sort Inbox messages into groups. For messages the app cannot sort using rules on your Mac, you may choose an AI provider and connect it with your own key. You can choose a supported preset or enter a compatible provider and endpoint yourself. AI data transfer is off by default and requires your separate consent and enablement; signing in to Google does not turn it on.

Before you consent, Briskmail shows the provider and server destination you chose (or tells you that the endpoint is local). For each message that needs a group decision, your Mac sends the sender address, subject, up to 1,200 characters of visible message text (extracted from HTML when present, otherwise plain text), Gmail category labels, whether you have replied to that sender before, and counts of messages seen and opened from that sender. Unsubscribe headers and URLs stay in the local rules; they are not sent to the AI provider. It does not send attachment bytes, your whole mailbox, or your Google OAuth token. The request also includes your selected model and instructions to return one group identifier. Briskmail accepts only a valid group, not a draft or a mail action. Requests go directly to your selected endpoint over HTTPS, or to a local loopback endpoint; redirects are refused. Briskmail does not receive this content on a developer-operated server.

Your provider key is stored separately for that provider in the macOS Keychain and is sent only to the chosen endpoint to authenticate your request. The provider may retain the request under its disclosed terms; Briskmail does not control that retention. Before enabling transfer, check that your chosen provider's terms or settings prohibit using this data to train AI models; do not enable a provider that permits training on it. Briskmail keeps group and reason metadata locally without storing a second copy of the message for Triage.

You can turn off Triage data transfer in the app. Changing the provider, endpoint or model clears consent and turns transfer off; you must consent again and enable it before another transfer. Turning transfer off stops future requests; it does not delete data the provider has already received, so check that provider's retention and deletion terms.

Command-line access

Briskmail includes an optional command-line tool for programs you choose to run on your Mac. macOS asks whether to let a program control Briskmail through Automation. In Briskmail's Settings ▸ Advanced ▸ Command-line access, the mail-reading and auto-send switches are off by default. These switches cannot be turned on by a command-line or AppleScript command.

  • Window actions: With macOS Automation consent, a program can open a conversation, search or folder in Briskmail, open a prefilled compose or reply window, or check for new mail. The tool returns no mail content from these actions.
  • Mail metadata: If you turn on “Let apps read and organize my mail,” a program can list and search mail and receive message ids, senders, subjects, dates, labels and unread state. These results do not include message bodies or snippets.
  • Mail content: The same switch also permits a program to read message and thread text and attachment details, and to save an attachment to a path it names. Message text is marked as untrusted email content. Removing hidden text reduces risk but cannot make hostile email safe instructions.
  • Organization: The same switch also permits the reversible changes the app's own buttons make: labeling, marking read or unread, starring, archiving, snoozing and saving a draft.
  • Sending without asking: A separate “Let apps send without asking” switch, also off by default, plus a grant you confirm with Touch ID or your login password, permits limited automatic sending. Even then Briskmail sends only to addresses already in the thread, in your Contacts or in your sent mail, holds each message in Undo Send first, sends at most about 20 messages an hour per account, and labels each one “Briskmail/Sent by agent”. A message to anyone else is saved as a draft and you get a notification.
  • Never: The tool has no command to permanently delete mail, create or change filters or forwarding, change account or security settings, or unsubscribe.

Mail returned by the command-line tool goes to the local program that you allowed to control Briskmail. That program's handling of the data depends on the tools and services you allow it to use. Briskmail does not send command-line results to a Briskmail server. Our use of Google data, including data made available through this tool, follows the Google User Data Policy and its Limited Use requirements described below.

Diagnostics reports

When you choose Help ▸ Report a Problem or Help ▸ Export Diagnostics, Briskmail saves a diagnostics report on your Mac. It contains the app and macOS versions, each account's sign-in and sync state (named "account 1", "account 2", never by address), background activity, a log of app events, and a list of recent requests to Google that names only the kind of request and its result. It contains no message subjects, bodies, attachments, contacts, label names or tokens, and anything shaped like an email address is replaced before the report is written.

A report leaves your Mac only if you send it. "Send to Briskmail support…" opens an ordinary message to support@briskmail.app with the report attached, from your own Gmail account. You can read or remove the attachment, and nothing is sent until you click Send. We keep a report you send, and the email it came in, while we work on your problem, and delete both within 90 days after it is resolved. You can ask us to delete it sooner at any time.

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. A Triage provider must also prohibit training on the data it receives.
  • 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.

Purchases and licences

If you buy Briskmail, the payment is processed by Polar, our reseller and merchant of record. We never see your card details. We receive your email address, your order, and the licence key issued to you.

When you activate a licence, Briskmail sends the licence key and your Mac's computer name to Polar, and Polar records the activation so the 3-Mac limit can be enforced; the name is how you tell your Macs apart in Polar's customer portal. About once a week the app sends Polar the key and that activation's identifier to check that the licence is still valid. Deactivating a Mac, in Settings ▸ Licence or in the customer portal, removes its activation. We keep these purchase and activation records to honor your licence, handle refunds and answer disputes. None of this is Gmail data, and none of your mail is involved.

Refunds

If you ask for a refund (see the Terms of Service), Polar issues it and the licence key stops being valid; the next check from your Mac learns that, and Briskmail shows that it is unlicensed. We keep the order and refund record for the same reasons as above. A refund involves no Gmail data.

Visiting briskmail.app

This website uses Google Analytics to count visits, downloads and clicks on the checkout button. In the European Economic Area, the UK and Switzerland, Google Analytics sets cookies only after you choose Accept in the cookie banner. Until you choose, or if you choose Reject, it sets and reads no cookies, and Google receives only a cookieless signal that a page was viewed. Everywhere else, Google Analytics sets its cookies when you open a page. Google receives the page you view, the site that sent you, your browser and device type, and an approximate location; Google Analytics does not store your IP address. We see only totals. This covers the website only: the Briskmail app sends nothing to Google Analytics, and none of your Gmail data is involved.

To opt out, and choose Reject, block cookies for briskmail.app in your browser, or install Google's opt-out add-on (tools.google.com/dlpage/gaoptout). How Google uses this data: policies.google.com/technologies/partner-sites.

Waitlist

If you join the early-access waitlist on briskmail.app, we store your email address and, if you give them, your Mac type and number of Gmail accounts, in a private Vercel Blob store. We send one confirmation email through Resend and one email when Briskmail opens to everyone, nothing else. A hashed form of your IP address is kept briefly to limit abuse. The waitlist form uses Cloudflare Turnstile to block automated sign-ups. Turnstile processes limited browser and device signals under Cloudflare's privacy policy (https://www.cloudflare.com/privacypolicy/); we receive only a pass or fail. We delete every waitlist entry 30 days after the email saying Briskmail is open to everyone goes out. Email support@briskmail.app to have your entry deleted sooner.

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. Briskmail runs no server that receives your mail or your Google data, so apart from a diagnostics report you chose to send us or a waitlist entry (both described above), there is nothing to delete on our side. Purchase and licence records are kept as described under Purchases and licences. If you enabled external AI sorting, ask your chosen provider about deletion of requests it received before you turned transfer off or signed out.

Your rights, and the law that applies

Briskmail is made by Valley Edge Consulting, 3815 Keeha Drive, Port Alberni, BC V9Y 8C8, Canada. We are responsible for the personal data described on this page (the "controller" under the EU and UK GDPR). Contact us at support@briskmail.app.

Your Gmail content stays on your Mac. We do not receive it. The only mail content that leaves your Mac is what you send to a Triage provider you chose, as described above, and that goes straight to the provider, not to us.

For the data we do receive, these are our reasons under the law:

  • Purchases, orders and licence activation: we need them to sell you a licence and honor it (performance of a contract).
  • The waitlist: your consent. You can withdraw it at any time by asking us to delete your entry.
  • Diagnostics reports and support email: you sent them to us, and we have a legitimate interest in fixing the problem you reported.
  • Google Analytics cookies on this website: your consent, if you are in the European Economic Area, the UK or Switzerland. Google Analytics sets no cookie there until you choose Accept in the cookie banner. You can change your mind at any time: use "change your cookie choice" under Visiting briskmail.app and choose Reject. Your choice is saved in your browser, not in a cookie. Everywhere else Google Analytics runs when you open a page, and you can turn it off the same way.
  • The hashed IP address and Cloudflare Turnstile: our legitimate interest in keeping automated sign-ups and abuse off the waitlist.

You can ask us to give you a copy of your data, correct it, delete it, limit how we use it, send it to you in a portable format, or stop using it where we rely on legitimate interest. Where we rely on your consent, you can withdraw it at any time. Email support@briskmail.app. We answer within one month.

If you are not happy with our answer, you can complain to the data protection authority where you live: in the EU, your national authority; in the UK, the Information Commissioner's Office (ico.org.uk). Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) also applies to us, and you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca).

We are in Canada, and the services we use may process data in the United States and other countries. Polar handles payments and licences as our merchant of record; its privacy policy says it protects transfers from the EU and UK with the European Commission's Standard Contractual Clauses. Vercel hosts this site and stores the waitlist, Resend sends the waitlist confirmation email, and Cloudflare runs Turnstile; each says it takes part in the EU-U.S. Data Privacy Framework and uses Standard Contractual Clauses for transfers from the EU and UK. Google Workspace hosts our support@briskmail.app mailbox, which receives support email and any diagnostics report you send; Google's data processing terms rely on the EU-U.S. Data Privacy Framework and its UK Extension for transfers to the United States, and on Standard Contractual Clauses otherwise.

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.

Contact

support@briskmail.app

Questions about your data?

Write to support@briskmail.app.

Email support