Mailie Pro is built so that your mail simply cannot leak. There is no analytics SDK to disable and no “share usage data” toggle, because neither exists in the app. This is a property of how it is put together, not a promise about how we behave.
A privacy policy describes intent. Architecture describes capability. Mailie Pro is built so the private thing is the only thing that can happen.
We do not operate a mail service, an account system, a sync backend or an AI endpoint. There is no infrastructure of ours that your mail could reach, which is a stronger guarantee than any policy: we could not read your inbox if we wanted to.
The language model and the semantic index run in the app’s own process. The only time anything is fetched is when you download a model file — a one-time, user-initiated transfer over TLS that carries none of your data with it.
No analytics SDK, no crash reporter, no advertising identifier, no fingerprinting library is compiled into the app. That is why there is no “share usage data” switch — there would be nothing for it to turn off.
No contacts permission, even though the app has a full address book. No camera permission, even though it scans documents. No location, and no broad storage access. Attachments use a one-shot file-picker grant that expires.
No analytics, no crash-reporting SDK, no advertising identifier, no fingerprinting. Nothing about how you use the app is collected, because there is no code that could collect it.
Mail travels strictly between your device and the server you configured. There is no Mailie Pro cloud anywhere in the loop — we operate no service that could receive your mail.
Briefings, summaries, replies, answers and everything the app learns about your inbox are produced and stored by models on your device. Your mail and your prompts never reach an API, and nothing you do is used to train a shared model.
Remote content is blocked until you ask for it, defeating the open-tracking pixels marketers rely on — and Mailie Pro never auto-sends a read receipt.
Server lookups use DNS-over-HTTPS and fail closed, so the network cannot see — or tamper with — which mail servers you connect to.
The local cache, your contacts, your briefings and the search index all live in a SQLCipher AES-256 database, with credentials sealed by the hardware Keystore.
No contacts permission, no location, no broad storage access, and no camera permission even for document scanning. Attachments use a one-shot file-picker grant.
This website holds itself to the same standard: its analytics are first-party and cookieless, store no IP address and no fingerprint, honour Do Not Track and Global Privacy Control, and it loads no third-party scripts or fonts at all.
The exact detail of what the site records, for how long, and how to have it erased is in the privacy policy.
Nowhere. That is the whole design, and it is worth being precise about what it means.
The one network transfer involved is downloading a model file, which you start and can cancel. It carries nothing about you.
A one-time purchase — no subscriptions, no ads, no data sales, ever.
Point your Android camera here to install
GET IT ONGoogle Play