Privacy Policy
SwiftMail for Gmail connects directly to Gmail using Google OAuth authentication. Mail is processed on your Mac and cached locally for reading and offline access; SwiftMail does not operate a server-side database for your Gmail data.
Gmail Data
Section titled “Gmail Data”SwiftMail uses Gmail data to read and organize mail, compose and send messages, manage drafts and attachments, and detect verification codes. Messages and related account data are cached locally for these features.
All communication with Gmail uses the official Gmail API over HTTPS.
Google User Data Sharing
Section titled “Google User Data Sharing”We do not sell Google user data. We do not share, transfer, or disclose Google user data to third parties except as necessary to provide the application’s functionality, comply with applicable law, protect the security of the service, or with the user’s explicit consent.
Contacts
Section titled “Contacts”Contacts from your Google account and Apple Contacts are accessed locally for autofill suggestions when composing emails. Suggestions are processed on your Mac. Recipients you choose are included in messages and drafts sent to Gmail.
Local Storage
Section titled “Local Storage”Email data is cached locally using SwiftData for offline access. The cache is stored on your Mac and protected by macOS and your device account’s security controls.
Third-Party Services
Section titled “Third-Party Services”SwiftMail does not use any third-party analytics, advertising, or data collection services.
Sign Out
Section titled “Sign Out”Removing an account in Settings deletes its saved sign-in and locally cached SwiftMail mail data. Deleting the app alone may leave application data or Keychain items on your Mac.
Verification codes and external content
Section titled “Verification codes and external content”Detected verification codes are stored locally while the feature is enabled. Choosing Copy Code places the code on the macOS clipboard and requests that Gmail move its source email to Trash. Code notifications are delivered through macOS when allowed.
HTML emails can load remote images over HTTPS, which contacts the image hosts and may reveal that an email was viewed. Opening email links contacts the destination website. Release builds also contact the update host to check for and download app updates.