Your mail stays yours.

The short version

• Gmail requests travel directly between LiquidMail on your Mac and Google.
• There is no developer-operated mail-processing backend.
• Credentials are stored in the macOS Keychain.
• LiquidMail does not sell personal information or use Gmail data for advertising.
• Optional agent access is off by default and requires your approval for every request.

Information LiquidMail accesses

Google account and Gmail data

When you connect Gmail, LiquidMail receives your Google account email address and display name and requests the gmail.modifypermission. This lets the app read and search messages, threads, labels, attachments, and drafts; compose and send mail; and manage mailbox state such as read status, stars, archive, spam, and Trash.

LiquidMail does not request unrestricted access to permanently delete Gmail messages. Google API data is used only to provide the visible email and user-authorized agent features described here.

Information stored on your Mac

LiquidMail stores the following inside its macOS App Sandbox container:

• connected account identifiers, display names, ordering, colors, and signatures;
• local compose drafts and attachment metadata;
• app preferences, synchronization markers, and Premium state;
• limited local agent activity records without message bodies or returned payloads.

Refresh tokens and local agent bearer tokens are stored in the macOS Keychain. Attachments are exported only to a location you select.

Google Sign-In and Apple

LiquidMail uses Google Sign-In for authentication. Google may process account and device information according to the Google Privacy Policy. Premium subscriptions are processed by Apple through StoreKit. The publisher receives subscription entitlement information but never your payment card or bank details.

Agents and AI providers

The optional Premium MCP server runs only on 127.0.0.1 on your Mac. It remains disabled until you review a disclosure and consent. Each request requires a separate Allow Once decision in LiquidMail.

If you approve a read, LiquidMail returns the requested Gmail data to the local client. That client may transmit it to the AI provider you selected. The client and provider have their own terms and privacy policies. LiquidMail does not select that provider or train a model on your Gmail data.

Sharing and retention

Information is transmitted only as needed to:

• Google, for authentication and Gmail requests;
• Apple, for App Store distribution and subscriptions;
• a client you authorize, for an approved local agent request.

LiquidMail does not sell or rent Gmail data or personal information.

Disconnecting and deletion

Disconnecting an account asks Google to revoke authorization before removing the saved credential, account record, local drafts, synchronization markers, and in-memory mail state. You can also revoke access from your Google Account security settings.

Security

LiquidMail uses the macOS App Sandbox, Keychain storage, encrypted TLS connections, loopback-only agent networking, bearer-token authentication, granular permissions, and per-request approval.

Contact

For privacy questions or requests, contact Baptiste Bouillot at baptiste@ultraviolettes.fr. Most mail content remains stored locally or by Google, so requests about Gmail-hosted data should also be directed to Google.