Privacy Policy — Winmail Reader

Last updated: October 16, 2026

Winmail Reader ("we", "us", or "our") is built to open email files without putting your data at risk. This Privacy Policy explains what the app handles, what it never collects, and your choices. The short version: your files are decoded on your device and never uploaded.

1. Scope

This policy applies to the iOS app Winmail Reader - DAT, MSG, EML on iPhone and iPad, published by W4N9WE1 / Lababacy.

2. Data We Process

2.1 Your files — processed on your device only

Winmail Reader decodes winmail.dat (TNEF), MSG, OFT, EML, MHT/MHTML, XPS, OXPS, MBOX, PST, OST and OLM files entirely on your device. There is no Winmail Reader server, and no upload step.
Your original files are opened read-only — the app never modifies them. ("Your originals are never modified.")
Decoded copies (extracted text, attachments, exports) are written only into the app's own sandbox on your device, where you can view, share, or delete them.

2.2 Permissions

The app requests no standing permissions — no camera, microphone, location, photo library, contacts, or calendar access is held while you use it.
Calendar and contacts, one exception by design: if you tap Add to Calendar or Save to Contacts on a decoded invitation or attachment, the specific data you selected is handed to the system editor screen for you to review and confirm. The app itself does not read your calendar or your contacts, before or after.

2.3 Settings stored on your device

Your preferences, the recent-files list, and browsing history are stored locally on your device. You can delete the recent list and history from inside the app at any time (see section 8).

3. What We Do NOT Collect

No account, sign-up, or email address required
No file uploads — there is no server that could receive them
No file contents in analytics: no file names, no message subjects, no search terms
No access to your contacts or calendar databases
No behavioral profiles, and we do not sell personal data

4. Advertising

The free tier of Winmail Reader shows ads served by Google AdMob so that reading stays free.
If you are in the EU/UK, Google's consent management platform (UMP) shows a consent form before ads are served, as required by Google's consent policy.
Where required (for example, in the EU/UK), the app's settings include an entry to Google's ad privacy options, where you can review or change your ads-related choices.
Depending on your region and your consent choices, Google's consent flow may include Apple's App Tracking Transparency prompt asking whether you allow tracking. You can change this at any time in iOS Settings → Privacy & Security → Tracking.

Google's handling of ad data is described in Google's Privacy Policy. Your files are never used for advertising: ad requests do not include your documents, their names, or their contents.

5. Purchases

Winmail Reader Pro is a one-time purchase processed by Apple as an App Store In-App Purchase. When you purchase, restore, or check entitlement, RevenueCat acts as our service provider and may process purchase records, transaction information, entitlement status, and a pseudonymous app user ID. RevenueCat does not receive your files and has no way to see them. We never receive or store your payment card details.

See RevenueCat's Privacy Policy and Apple's privacy information for how these providers handle purchase-related data.

6. Crash Reports and Usage Analytics

Firebase Crashlytics collects crash and error reports, which may include device model, operating-system and app versions, and stack traces, to diagnose and fix crashes.
Firebase Analytics records a limited set of usage events (for example, that a tool was opened, with counters and an app-instance identifier). Event parameters are only closed enumerations and counts — they do not include file names, message subjects, search terms, file contents, or personal information.
These analytics are not used to build advertising profiles.

Google processes this information as described in Google's Privacy Policy.

We do not sell personal data. Data is shared only with the processors described above — Google (AdMob and Firebase), Apple (App Store and purchases), and RevenueCat (purchase entitlement) — or where the law requires it.

8. Local Data and Retention

Temporary decoded copies are stored only inside the app's private sandbox and are kept in a rolling window of the most recently used copies — they are never shared.
Deleting an entry from the recent list does not delete its decoded copy.
Uninstalling the app removes all of it — files, decoded copies, settings, and history.

9. Children

Winmail Reader is not directed at children, and we have no knowledge of collecting personal information from children.

10. Your Choices

Delete a recent-files entry by swiping it in the recent list on the home screen.
Review or reset ads consent choices through the ad privacy entry in the app or your Google account settings.
Restore a purchase with Restore Purchases in the app; manage or refund purchases through Apple.
Uninstall the app to remove all locally stored data.
Questions or requests: email us (below).

11. Changes

We may update this policy as the app evolves. Changes are posted on this page with a new "Last updated" date.

12. Contact

Questions about this policy: email the developer.

Related: Terms of Use · Support · All our apps