Privacy in the Mailami app
This page describes the current personal macOS app. Public Google access is still being prepared. This is a technical privacy notice for that app; the final policy for a public release is pending confirmation of the operator’s processing roles, retention and legal disclosures.
Developer and contact
Mailami is developed by Amadeusz Dylla. For support or privacy requests, email dev@amadeuszdylla.pl. Visiting this website does not connect an account.
Data used by the app
When you connect a mailbox, Mailami accesses mail content, headers and participants, folders, attachments and account settings to display, search, compose, send and organize your mail. It stores local working data on your Mac. Tasks you create, including links to messages, are local app data.
Calendar connections access calendar lists and events, including titles, dates, descriptions and participants as available, to display and synchronize your calendars and the changes you make. Imported calendar files are also stored locally.
Google permissions
The current Gmail integration uses IMAP/SMTP and requests full mail access (https://mail.google.com/), a broad permission that can include permanent deletion. Optional profile access (openid email profile) is used for account identity and a profile image. Calendar authorization is separate and requests openid email, calendar.calendarlist.readonly and calendar.events to list calendars and read and change events. Authorize only accounts you want to connect.
Connections and sharing
The app communicates with your selected mail and calendar providers to perform the features you use. Sending a message or a calendar invitation shares its contents with recipients through those providers. Loading external images in mail or opening a link can contact the external host. Provider policies apply to data they process.
The personal edition has no AI features or shared workspaces. It does not send mail to AI providers. No sale of Google user data or use for advertising or model training is part of this edition. The operator does not receive your mailbox through a Mailami synchronization service; support receives only what you choose to send.
Local protection and backups
Passwords and authorization credentials use macOS Keychain. New local backup archives created by the app use AES-256-GCM with a device-bound Keychain key. Losing that key or the Mac can make those archives unrecoverable. For transfer to another Mac, create a separate password-protected export; it requires a password of at least 12 characters. Keep that password separately.
Backup encryption is not a promise that every local working file or older copy is encrypted. Earlier plain-text backups and technical snapshots may remain. Local data protection is being extended and must be verified for each release. App Sandbox and encrypted connections do not provide end-to-end encryption of email. Protect your Mac and its backups.
Disconnecting and deleting data
You can remove a connected account from the app and revoke Google access in your Google account connections. Revocation stops future authorized access; it does not delete existing local copies. Removing a local account does not delete your account with the provider, all previously created tasks or separate backup archives. Provider-side messages and events follow the operations you perform and the provider’s retention rules.
Review saved exports and backups separately when deleting data. No fixed retention period or secure erasure guarantee is claimed here. For correspondence held by the developer, send a privacy request without attaching mailbox contents or archives.
Google Limited Use
Use of information received from Google Workspace scopes is limited to the disclosed user-facing mail and calendar features and is subject to the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. This statement is a commitment about use, not a claim of Google verification, certification or completed security assessment.
Support without exposing private content
Send the app and macOS versions, steps to reproduce and a redacted error message. Do not send passwords, authorization tokens or codes, complete logs, mailbox databases, backup archives, private messages or attachments. If an example is needed, use synthetic data.