Privacy Policy
In short
Mugyn runs on your device. We have no server that stores your mail, notes or login credentials. The app talks directly to your mail provider (Google, Microsoft or iCloud) to fetch and send your messages. The only Mugyn server handles new-mail notifications: it receives a "mailbox changed" signal from the provider, has no access to your mailbox and does not store your e-mail address. What exactly that signal contains is described below.
What data the app processes and where
| Data | Source | Stored |
|---|---|---|
| E-mail messages: body, headers, attachment metadata (name, type, size); an attachment's content is downloaded only when you open it | your account at the provider | local database on the device |
| Notes and side threads | created by you in the app | local database; notes are never sent to anyone, including the mail provider; optionally replicated through your own iCloud Drive (see below) |
| OAuth access tokens (Google, Microsoft) | result of signing in at the provider | iOS Keychain; they never leave the device and never reach any Mugyn server |
| App-specific password for iCloud Mail and IMAP/SMTP server addresses | entered by you when connecting the mailbox | password in the iOS Keychain, server addresses in the local database; they never leave the device and never reach any Mugyn server |
| E-mail address of the connected mailbox | read during sign-in | local database |
| App settings | your choices | locally |
| Names you give people, and names from Contacts for addresses that appear in your mail | you (the person card in the app); iOS Contacts, with your permission | local database; a copy for notification content in the iOS Keychain of this device; they never leave the device (details in the "Contacts" section) |
| On Apple Watch: the list of recent cases from the Inbox (sender, subject, beginning of the text), the content of messages you open on the watch, and copies of the OAuth tokens of Google and Microsoft mailboxes | your iPhone, over the system iPhone–Apple Watch link | app storage and Keychain of the watch paired with your iPhone; the watch talks to Google or Microsoft directly only when the iPhone is out of reach; none of it reaches any Mugyn server (details in the "Security" section) |
Access to your mail provider account
You sign in through the provider's standard sign-in window (OAuth 2.0 with PKCE). Mugyn never sees your password. We request the following permissions:
Google (Gmail API)
gmail.modify: reading messages into the local database and writing back the changes you make in the app: marking as read or unread, archiving, moving to trash. The same scope is used to subscribe to mailbox change notifications.gmail.send: sending messages you write in the app (replies, side threads).userinfo.emailandopenid: identifying the connected mailbox and issuing an identity token that proves to the notification server that the mailbox is yours. The identity token grants no access to your mail or to any Google API; the server verifies its signature and discards it immediately.
Mugyn's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Gmail data goes only to your device, is used solely to provide you with your own mail inside the app, is never transferred to any Mugyn server or third party, is not sold and is not used for advertising.
Microsoft (Microsoft Graph)
Mail.ReadWrite: reading messages and writing back read state and folder moves.Mail.Send: sending messages.offline_access: refreshing the session without signing in again.openid profile email: identifying the account and issuing an identity token for the notification server, as above.
iCloud Mail (IMAP and SMTP)
Apple offers third-party apps neither a mail API nor OAuth sign-in. You connect an iCloud mailbox with an app-specific password that you generate in your Apple Account (two-factor authentication must be on) and can revoke at any time at account.apple.com. Mugyn uses it solely to sign in to Apple's servers: fetching mail over IMAP (imap.mail.me.com) and sending over SMTP (smtp.mail.me.com). The password is stored only in the iOS Keychain on your device and never reaches any Mugyn server. For the same reason an iCloud mailbox has no real-time notifications: new mail appears when you open the app and during background refresh, and the Mugyn notification server takes no part in handling this mailbox and processes none of its data.
These permissions are used only to handle your own mail on your instruction. Traffic flows directly between your device and Google, Microsoft or Apple servers. Mugyn is not a party to that communication and keeps no copy of it on any server.
Real-time notifications
New-mail notifications are on by default; you can turn them off in the app settings at any time. They work like this:
- Your device itself subscribes to mailbox changes at the provider, using its own token. The Mugyn server does not hold and never receives access tokens to your mail.
- Google delivers the change signal through Google Cloud Pub/Sub in the Mugyn project. That signal contains your mailbox address and a mailbox state number (historyId), with no content, senders or subjects. The server immediately replaces the address with an irreversible pseudonym (a keyed cryptographic hash) and stores the address neither in its database nor in its logs; the address exists in server memory only while one signal is being handled.
- Microsoft sends the signal directly to the Mugyn server. It contains a subscription identifier and a Microsoft-assigned resource (message) identifier, with no e-mail address and no content.
- The server relays the signal to your iPhone through Apple Push Notification service (APNs). Your phone fetches the sender and subject directly from the provider and composes the notification text itself; only the mailbox pseudonym and the state number pass through APNs.
- At registration your phone sends the server an identity token for each mailbox (see scopes above). The server verifies the signature, reads the address from it solely to compute the pseudonym, and stores neither the token nor the address.
- The server stores: the device identifier issued by Apple for delivering notifications, the mailbox pseudonym, the provider, the device language and app version, and technical subscription data (identifier, expiry time, the secret that authenticates signals).
- Server logs contain no addresses, content or tokens; pseudonyms are truncated in them. Logs are kept for 7 days.
- Retention: turning notifications off or disconnecting the mailbox deletes this data immediately. A device Apple no longer delivers to is removed at once. An abandoned registration (for example after deleting the app without turning notifications off) is removed no later than 30 days after the provider subscription expires.
- The notification server runs on hardware owned by the controller in Poland; no third-party hosting provider is used. Should that change, this policy will be updated.
Since version 0.1.84 the notification extension also adds the beginning of the message text to the notification, so that the Apple Watch app can show it in the expanded notification. This happens on the iPhone, with your own token; the notification server never sees that text.
Notes in your iCloud Drive
If you enable note replication between your devices, Mugyn stores notes in the app's folder in your own iCloud Drive, through Apple's system mechanism on your iCloud account. Mugyn has no access to those files outside your devices. You can disable replication in the app settings or in the system iCloud settings.
Reminders
When you ask for a reminder about a case, Mugyn creates it in Apple Reminders with the case subject and a link back to the app in the reminder's note. To show whether the reminder is done, the app reads your reminders locally and considers only the ones it created. Apart from ordinary Reminders sync in your iCloud, nothing leaves the device. You can revoke access in system settings.
Contacts
During first setup the app asks for the system Contacts permission. You can decline in the system prompt and revoke access at any time in system settings. Once granted, Contacts are used for two things, each of which you can turn off separately in the app settings:
- Recipient suggestions ("Suggest recipients from Contacts"). When you type a recipient, the app suggests people from your mail, that is senders and recipients of messages already in the local database, and additionally people from your address book. Names and addresses from Contacts are searched in memory as you type and are not stored for this purpose; after you pick a recipient, only the address you put into the message remains.
- People's names ("Show names from Contacts"). If an e-mail address that appears in your mail is also in your Contacts, the app shows the name from Contacts for it instead of the name from message headers. To do so it stores that name in the local database next to the address, and the names shown in notifications also in the iOS Keychain of this device, where the notification extension reads them. Only names for addresses already in your mail are stored; other Contacts entries are not stored anywhere. Turning the option off or revoking the permission removes these names from the database and the Keychain.
You can also rename any person yourself on their card in the app; such a name is stored in the local database and takes precedence over names from Contacts and from headers. Neither names from Contacts nor names you set are sent to any Mugyn server or to your mail provider. The app does not add them to the messages you send either: for an address already in your mail, the recipient sees the name from your mail in the address field, not yours. The exception is an address picked from suggestions that is not yet in your mail: then the name shown next to it in the address field is sent.
Remote images in messages
Images hosted on senders' servers (including so-called tracking pixels) are blocked by default. They load only on your choice: for one message, always from this sender, always from this domain, or for all messages if you enable that in settings or from a message, after confirmation. Loading an image is a request from your device to the sender's server; Mugyn neither proxies nor records it.
In-app purchases
Paid features are purchased through the App Store; the seller is Apple Distribution International Ltd., which handles payment, card data, refunds and withdrawal. To check which features are unlocked, the app uses RevenueCat, Inc. (USA). RevenueCat receives an anonymous app installation identifier and purchase information from the App Store (product identifier, dates, status); it does not receive your e-mail address or anything from your mail. Details: RevenueCat privacy policy.
Analytics, telemetry, advertising
Mugyn collects no usage statistics, contains no analytics or advertising SDKs and does not track you across apps or websites. Any crash reports go only to Apple according to your system settings and contain no mail or note content. The mugyn.app website uses no cookies and no third-party scripts; the web server keeps a standard access log (IP address, time, requested URL) for 7 days for service maintenance and security.
Security
You can turn on an app lock and, separately, protect selected mailboxes. Unlocking uses Face ID, Touch ID or the device passcode through Apple's system mechanism; Mugyn has no access to biometric data and stores no codes. Mail in a protected mailbox stays on the device in the same encrypted database; it is only hidden in the interface and in notification content until unlocked.
Data on the device is protected by iOS encryption tied to the device passcode. OAuth tokens and the iCloud app-specific password live in the iOS Keychain, in an access group available only to the Mugyn app and its notification extension on the same device; they are excluded from backups and not transferred to other devices. Connections to providers and to the notification server are encrypted (TLS); the connection to iCloud mail servers is always TLS-encrypted, including sending (STARTTLS). Signals to the notification server are authenticated: from Google with a signed Google Cloud token, from Microsoft with a secret issued at registration.
Apple Watch. The watch app (since version 0.1.84) receives from the iPhone the list of recent cases, the content of the messages you open on it, and copies of the OAuth tokens of Google and Microsoft mailboxes, so that it can fetch a message directly from the provider when the iPhone is out of reach. IMAP mailboxes, including iCloud Mail, are read on the watch only through the iPhone; their password never reaches the watch. Transfer between the devices uses Apple's encrypted system channel, and data on the watch is protected by watchOS encryption and the watch Keychain. Protected mailboxes and mailboxes hidden by a schedule are invisible on the watch exactly as on the iPhone. A reply written on the watch is sent by the iPhone from your mailbox. Disconnecting the mailbox on the iPhone or removing the app from the watch deletes these copies.
Processors and international transfers
The following process data on our behalf: Apple (notification delivery via APNs, iCloud, App Store), Google Cloud (Pub/Sub: relaying the mailbox-change signal; its contents are described above) and RevenueCat (purchase status). Apple, Google and RevenueCat may process data in the United States. For Apple and Google, transfers rely on the European Commission's adequacy decision for organisations certified under the EU-U.S. Data Privacy Framework; for RevenueCat, on the Commission's standard contractual clauses (Module 2) incorporated in RevenueCat's data processing agreement. We share data with no one else unless required by law.
Your rights and control
- Disconnecting a mailbox in settings deletes its local data and, where the provider allows, revokes the access token. For Microsoft accounts you can additionally revoke consent at account.live.com/consent/Manage; for Google in your Google account permissions. For iCloud, disconnecting deletes the app-specific password from the device; the password itself is revoked at account.apple.com.
- Deleting the app deletes the local database with mail and notes. Notes in iCloud Drive can be deleted in the Files app or in iCloud settings.
- Turning notifications off deletes the registration data from the Mugyn server.
- Under the GDPR you have the right to access, rectify, erase, restrict, port and object, and to lodge a complaint with a supervisory authority; in Poland this is the President of the Personal Data Protection Office (UODO, ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl). For data requests write to bartosz@mugyn.app. Since, apart from notification registration, we store no data of yours on a server, most requests are fulfilled by you in the app, immediately.
Legal bases (GDPR)
Processing on the device is under your sole control. Notification registration and delivery, and purchase status checks, are processed to perform the service contract (Art. 6(1)(b) GDPR); server logs under our legitimate interest in maintaining and securing the service (Art. 6(1)(f) GDPR).
Children
The app is not directed at persons under 16 and does not knowingly collect their data.
Changes
We will announce material changes in the app and on this page in advance. Any new permission at your mail provider requires, in any case, your renewed confirmation in the provider's sign-in window.