Mitt MailMitt Mail

Mitt Mail / Privacy

Your data.
Clear purposes.

This policy describes how Mitt Mail for Windows, Linux and Android handles information when you connect email, read, send and use the local workspace.

Last updated: 24 October 2026 · Website analytics and owner access updated.

1. Operator and contact

The publisher and operator of Mitt Mail is 2024 ehf. Created by someone with a passion for this work.

Mitt Mail is an email application on the user's device. Your chosen email provider also has its own terms and privacy policy governing data on its servers.

2. What information is processed?

Google sign-in requests basic identity information and email address along with mail access. The local calendar and contact cards do not automatically sync with Google Calendar or Google Contacts in this release.

3. Purposes and permissions

Information is used to display, search and organise mail, save drafts and attachments, send messages you compose, synchronise supported changes and show notifications. Workspace content is used to provide the features you choose.

You choose to connect an account and consent to OAuth permissions with Google or Microsoft. The Gmail connection uses https://mail.google.com/ for IMAP/SMTP. The Microsoft connection requests sign-in and mail permissions along with offline_access, so access can be renewed while the connection is saved.

Access tokens are used to communicate with the email provider, not as consent for other uses of mail data. Data is not sold, used for targeted advertising or used to train general-purpose AI models.

4. Storage and security

Mail, drafts, attachments, images and workspace content are stored on your device. Windows normally uses %LOCALAPPDATA%\Mitt Mail, Linux uses the application's private directory under your home directory, and Android uses private app storage. Saved credentials are protected by Windows CurrentUser DPAPI, Linux Secret Service or Android Keystore, depending on the operating system.

Mitt Mail does not automatically encrypt the mail database or attachments. Protecting access tokens does not encrypt all stored mail. Access to the computer, Windows settings and disk encryption therefore affect the protection of this data.

Mail connections use TLS and certificate validation. OAuth sign-in takes place with the provider. Windows/Linux use PKCE and a temporary local callback listener; Google sign-in on Android uses the built-in Google flow. Mitt Mail runs a local service on the computer to display its interface.

Windows notifications may show the sender and subject, including on the lock screen depending on Windows settings. You can turn off notifications and sounds in the app.

5. Sharing and external services

Without Device sync, mail travels directly between your device and your chosen email provider. Since release 0.19.17 / Android 0.1.18, Device sync connects automatically through the primary connected email account with supported services. You can stop sync in settings.

Without Device sync, the operator does not automatically have access to your mailbox through this local implementation.

Automatic device sync

When a supported primary email account is connected in Mitt Mail, sync may connect automatically. To verify access, the server receives saved mail connection credentials or a short-lived OAuth access token over HTTPS and validates them against a predetermined mail server over TLS. OAuth refresh tokens are not sent to the sync server. Copies of account settings, saved password-based accounts, mail, attachments, drafts, contacts, calendar, tasks, notes, profiles, rules and supported settings are transferred over HTTPS to the sync server shown in the app, adminmail.mintonlist.is. Workspace data becomes accessible to other devices using the same verified primary email address or already paired with the same workspace.

Sync storage is separate from the mail-server database and protected by Windows DPAPI under the service identity and file access controls. This is not end-to-end encryption; the server administrator is responsible for access and backups. Each device also retains a local mail-database copy. Device pairing identifiers and credentials are protected by DPAPI, Android Keystore or Linux Secret Service, depending on the operating system.

Google and Microsoft OAuth access and refresh tokens are not transferred between devices. A new device may require signing in again with the provider. Disconnecting or revoking a device stops further access but does not delete copies it already downloaded. Backups and older encrypted data chunks on the server are not automatically removed; the operator handles permanent deletion and backups under their retention arrangements.

6. Google data and Limited Use

Mitt Mail's use and transfer of information received from Google adheres to the Google API Services User Data Policy, including the requirements for restricted use (Limited Use).

Google mail data is used for visible email features chosen by the user. It is not sold or provided to advertising intermediaries and is not used for general AI training. Apart from information you specifically provide for support, this release does not automatically collect mail data for the operator.

7. Retention and deletion

Local mail and content remain until you remove them. Saved sign-in credentials remain until the account is removed, access is revoked with the provider or access expires. Expired access does not delete local mail.

  1. Disconnect and remove credentials: use Settings → Email accounts → Remove account. This removes that account's saved sign-in credentials from Mitt Mail. Downloaded mail remains.
  2. Revoke OAuth: remove Mitt Mail from connected apps in your Google account or from authorised apps in your Microsoft account/organisation. Removing an account locally does not automatically revoke access with the provider.
  3. Delete all local content: close Mitt Mail completely and remove its data directory if you wish to delete all local accounts, mail, attachments and workspace content. Make a backup only if you wish to retain the data. Exported files and other copies must be removed separately.

Normal Windows uninstallation leaves the data directory in place. Deleting a local directory does not delete server mail. However, deletions or moves within a synchronised mailbox may affect mail held by the provider.

8. Your choices and enquiries

You can choose which accounts are connected, turn off automatic mail retrieval, change image loading and notifications, export saved data and revoke the email connection.

For server-held data, you may need to contact your email provider. The user controls local data on their own computer.

9. This website

This website uses Mitt Mail’s own website analytics for the site owner. It measures browser sessions, pages and sections viewed, gallery use and download clicks. It does not read emails, mailboxes or their contents.

Recorded information may include IP address, User-Agent and browser/operating-system hints, language, time zone, screen and viewport size, referrer origin without path or query, timestamps and estimated active time. Passwords, form contents, licence keys and access tokens are not recorded. A click does not confirm a completed download or purchase.

A name is shown only when this website’s separate sign-in has been verified on the server. Other sessions are unnamed; an IP address does not identify a person. Website access is separate from Mitt Mail email accounts.

A session identifier is kept in browser sessionStorage and is not shared across websites. Opt-out preference is stored in this browser’s localStorage. DNT (Do Not Track) and GPC (Global Privacy Control) automatically stop tracking. The owner authentication cookie is used only for secure website sign-in.

Data is stored privately outside the public web root, separately from accounts and mail data. The dashboard covers at most 30 days, with up to 2,000 sessions, the latest 40 pages and 60 actions per session, within an 8 MB limit. Older data is removed on the next processing operation; setup instructions include daily cleanup. Both the dashboard and its JSON data are restricted to the owner.

The web server may send an IP address to ipwho.is to estimate country and city. Location may be inaccurate, including when a VPN is used. This lookup can be disabled in private website settings. Flag images in the owner dashboard are fetched from cdn.ipwhois.io; no third-party geolocation script runs in visitors’ browsers.

The web host may also maintain its own technical logs, including IP address and requested URL. Opting out of Mitt Mail website analytics does not control those logs. Additional services and linked external websites have their own privacy information.

10. Changes

The policy will be updated when data handling or features change. The date above shows the latest update. New use of Google data beyond approved permissions requires appropriate disclosure and fresh consent before it begins.

← Back to the Mitt Mail homepage