iHeartMail is an application published by Practical Dev Studio ("we", "us"). This policy explains what the app does with your email and your Google account data.
iHeartMail reads your Gmail and analyses it in the app, on your own device. It can also show the coming week from your Google Calendar in your daily brief — read-only, never modified, and never stored. Your email content is never sent to us, and we operate no server that receives it. We cannot read your mail.
Today the app sends us nothing at all. It has no update check: new versions will come through your platform's app store. Two things that would contact us are planned, not built: optional crash reports, and syncing your settings between your own devices. Neither will carry your email. Each is described below, along with what we commit to before it ships.
When you connect your Google account, iHeartMail requests these permissions:
| Permission | What it allows | Why iHeartMail needs it |
|---|---|---|
gmail.modify |
Read your mail; add and remove labels; move messages to Trash; send mail | Reading and categorising your mail; marking messages read or unread; moving messages to Trash; sending, replying, and following up |
openid, userinfo.email,
userinfo.profile |
Your basic Google profile and email address | Showing which account is connected |
calendar.events.readonly |
Read-only access to events on your Google Calendar | Showing the coming week's events, and the nearest one, in your daily brief |
iHeartMail requests the narrowest Gmail permission that supports its
features. It does not request full-access permission
(https://mail.google.com/), because it never permanently
deletes mail — "delete" moves a message to Gmail's Trash, exactly as
the Gmail web interface does, and Gmail's own retention rules apply
from there.
You can revoke access at any time from your Google Account permissions page, or by signing out inside the app.
Your email travels between Google's servers and the iHeartMail application on your device. It goes nowhere else. We operate no server that receives your email, and your content, subject lines, sender addresses, and attachments are never transmitted to us or to any third party.
That's possible because the language model that categorises and summarises your mail runs inside the iHeartMail process itself, rather than in the cloud — see how it works for how that fits together.
iHeartMail keeps a local cache in a database file on your device, so the app can show your mail instantly and work offline. This cache holds:
iHeartMail does not store full email bodies. When you open a message, its full content is fetched from Gmail at that moment, displayed, and not written to the local database.
For mail you send, iHeartMail stores only metadata — the same details it keeps for received mail, listed above, so it can show your Sent folder. The message itself is held by Gmail only.
Your Google access and refresh tokens are stored in your operating system's secure credential store (Windows Credential Manager, macOS Keychain), not in the app's database or in plain text.
Many emails reference images hosted on the sender's own servers — logos, banners, and sometimes invisible "tracking pixels." Loading them tells the sender that you opened the message and when, and reveals your IP address to the server hosting the image.
iHeartMail does not load these images by default. Unless you choose to load them, no request is made to the sender's servers and neither disclosure occurs.
You can turn images on in Settings → Privacy, or load them for an individual message. When you do, images are fetched directly from the sender's host, and that host can see your IP address. iHeartMail has no server to route those requests through — the same design choice that keeps your mail off our infrastructure — so this connection is between your device and the sender's host. It does not involve us, and we learn nothing from it.
iHeartMail has no update check and no updater, and it never contacts us to find out about or fetch a new version. It will be distributed through each platform's app store: Flathub on Linux, the Microsoft Store on Windows and the Mac App Store on macOS. The store delivers new versions, under the store's own privacy policy, and the app takes no part in it.
iHeartMail does not currently send crash reports or any diagnostic data. The app contains no telemetry and no analytics.
We may add optional crash reporting in a future version, so that we can find and fix faults. If we do, we commit that it will:
We will update this policy, and the list of network connections below, before any such feature ships.
iHeartMail does not currently sync anything. Nothing about your categories, settings, or mail leaves the device you use it on.
We plan to let you pair a second device of your own, so that your categories and settings follow you. If we build it, we commit that sync will:
We will update this policy, including the Limited Use disclosure and the list of network connections below, before sync ships.
For transparency, this is the complete list of what the app connects to today:
Planned, and not in the app today: optional crash reports, and sync between your own devices, each as described above. This list will gain each one in the same change that ships it.
iHeartMail's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
Your email data lives on your device and is under your control.
Because we hold no copy of your email, there is no deletion request to make of us for it. If we introduce optional crash reporting or sync in the future, this policy will state how long each is kept and when it is deleted.
Local database files are protected by your operating system's user account permissions. If other people can sign in to your device as you, they can read your mail — as they could with any local email client. Use full-disk encryption and a strong account password.
This is about our website, not the app: the app itself still sends us nothing. If you subscribe to iHeartMail updates on the website, we collect your email address and nothing else.
iHeartMail is not directed at children under 13 (or the equivalent minimum age in your country) and we do not knowingly collect their data.
If we change this policy we will update the date at the top, and material changes will be noted in the app or on this page.
Questions about this policy or about privacy in iHeartMail? Contact us.
iHeartMail is published by Practical Dev Studio Pty Ltd (ACN 701 677 518), Australia.