Information the app accesses
When you connect an account, Susa Mail accesses information needed to provide its email features:
- Your email account address, account settings, and the display name you provide.
- Message senders and recipients, subjects, dates, headers, message text and formatted content, conversation information, folders or labels, read status, and synchronization identifiers.
- Attachment names, types, sizes, and the attachment content you download, preview, or include in a message.
- Drafts, replies, forwarded messages, selected files, outgoing recipients, and other content you create in the app.
Susa Mail also stores the credentials needed to keep your chosen account connected. Google accounts use authorization tokens. The current iCloud and other IMAP/SMTP development connections use the server credentials or app-specific passwords you provide.
Google account permissions
For Gmail and Google Workspace, you sign in through Google's website and decide whether to authorize Susa Mail. Susa Mail does not receive your Google account password.
Susa Mail requests the gmail.modify permission, which Google classifies as a restricted scope. The app uses it to load messages and attachments, send messages you compose, and synchronize changes such as marking mail read or archiving it. This permission does not grant immediate permanent deletion that bypasses Gmail's Trash. The app does not request Google Drive, Calendar, or Contacts permissions.
How information is used
Susa Mail uses account and message information to display and synchronize your mailbox, show conversations and attachments, search downloaded mail, save local drafts, process your mailbox actions, and send messages through the account you choose. Search and draft storage run locally in the current Mac app.
The current app does not send mailbox content to a Susa Mail-operated server. It connects from your Mac directly to Google or the incoming and outgoing mail servers configured for your account.
Local storage and security
In live-account mode, Susa Mail stores its local mailbox, drafts, outbox, and saved attachment copies in an encrypted vault on your Mac using AES-GCM encryption. The encryption key, Google authorization tokens, and mail-server credentials are stored in the macOS Data Protection Keychain as device-only, non-synchronizing items. Mail is decrypted in memory while the app uses it.
Connections to mail providers use encrypted transport. The app requires certificate verification and does not offer a plaintext or invalid-certificate bypass.
Attachment previews are an exception to encrypted file storage. When you choose Quick Look, Susa Mail creates a temporary plaintext copy with restricted file permissions so macOS can display it. The app normally removes that copy when the preview closes or the app exits. An unexpected termination, operating-system caches, or backups may retain copies; Susa Mail does not guarantee complete or immediate erasure.
An optional sample mode uses fictional messages and an unencrypted sample database. Do not use that mode to store real or sensitive mail.
When information is shared
Your email provider receives the authentication and mailbox requests needed to connect and synchronize. When you send, reply, or forward, the message, selected attachments, and recipient addresses are transmitted through your chosen sending provider for delivery to those recipients. Forwarding content through another connected account can transfer that content to that account's provider. Those providers and recipients handle the information under their own practices.
If you activate an external link in a message, your browser or the relevant application opens that destination. The destination may receive information associated with the visit. The app's formatted message reader blocks remote content and scripts before you choose to follow a link.
Susa Mail does not sell mailbox data or use it for advertising. The current Mac app has no remote AI integration, advertising SDK, or usage-analytics service. It does not provide the developer with remote access to your mailbox. If you voluntarily send information to support, that information is handled as support correspondence, as described below.
Google data and Limited Use
For information received from Google APIs, Susa Mail follows the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data and developer policy.
Google user data is used for the email features described in this policy. It is not sold, used for advertising, or used to develop, train, or improve general-purpose AI or machine-learning models. These restrictions also apply to information derived from Google user data.
The developer does not obtain routine human access to your Google mailbox through Susa Mail. If support needs a particular message or attachment, we will ask you to choose and explicitly share that material. Google-data transfers and human access remain subject to Google's Limited Use restrictions, including their limited security and legal exceptions.
AI features are planned, but are not part of the current app. Any future feature that changes the handling of your data will require updated disclosures and any necessary consent before that new use begins.
Retention, disconnection, and removal
Downloaded mail and other local account information remain in the app's vault while you use that account, subject to synchronization changes and actions you take. The current app does not apply a fixed automatic expiry period to the local mailbox.
To remove an account, open Susa Mail → Accounts & Privacy…, choose Remove… beside the account, and confirm. For Google accounts, the app first attempts to revoke authorization, then removes the account's local messages, drafts, outbox records, saved attachments, and credentials. If authorization cannot be revoked, including because the Mac is offline, removal may stop and need to be retried. If some encrypted attachment files cannot be deleted, the app reports the problem and retries that cleanup when it reopens.
You can also remove Susa Mail's access through your Google Account connections. Revoking access at Google does not by itself erase information already cached on your Mac. Remove the account in Susa Mail to clear its local account data. For iCloud or other mail hosts, you can separately revoke the app-specific password or other credential through your provider.
Removing an account from Susa Mail does not delete your mailbox or messages from your email provider. Uninstalling the app is not a guarantee that Keychain items, backups, operating-system caches, or previously created copies have been erased. Contact support if account removal cannot be completed or you need help locating remaining app data.
Website visits and support correspondence
Visiting this website does not authorize access to your mailbox. Website hosting services process ordinary web requests and associated visitor information, such as IP addresses and browser or request details, to deliver and operate the site under their own policies. This website activity is separate from the Mac app's mailbox storage and provider connections.
If you email support, we receive your address, your message, and any files or screenshots you choose to send. We use that correspondence to respond and investigate the issue. Support messages are handled through the support email service and are separate from your app's encrypted vault. They are retained for handling the request and related follow-up; you can request their deletion by contacting support. Removing an account in the app does not remove support correspondence.
Please do not send passwords, app-specific passwords, authorization codes, access tokens, or complete mailbox exports. Redact personal information from screenshots and send message content only when you deliberately choose to share it for a specific support issue.
Contact and policy changes
For privacy questions, deletion requests, or support, contact Susa Mail at ahmadpour@gmail.com.
We will update this page when the app's data practices change and show the new revision date. Material changes to the use of connected-account data will be disclosed before the new use begins, with consent requested where required. This policy does not represent Google verification, Apple approval, or a security certification.