1. Publisher and scope
SodCode publishes EML Reader for Android, package com.eml.attachmentreader, version 1.0.0. For privacy or support questions, contact sodcode.app@gmail.com.
EML Reader opens individual .eml email files, displays headers and message bodies, and saves selected attachments. Email processing works on your device without a mail account. We do not operate an email upload, mail account login or synchronization service. Email bodies, headers, sender and recipient addresses, attachment bytes, filenames and local paths are not sent with advertising or configuration requests.
2. Files, permissions and the message viewer
The app reads files you select through Android's document picker, Open With or Share. It creates a private source copy so you can reopen recent files and decodes message parts into a local cache. Exports are written to Downloads, a folder you choose or a location selected with Save as. It does not scan your storage or request broad storage, contacts, camera, microphone or precise-location access. Android may retain access to a folder you explicitly grant; you can forget that folder in Settings.
HTML emails are sanitized locally. The message WebView disables JavaScript, blocks network loads, rejects remote resources and prevents automatic navigation. Remote images and trackers in a message are not downloaded by the viewer. Following an external link requires a confirmation and opens another app, whose policies then apply. A cloud document provider may download the EML file or synchronize an export under its own policy.
The Android app has internet and network-state permissions for advertising, consent and public ad settings. Google's advertising SDK also declares advertising-ID and related permissions. These permissions do not give the email renderer permission to fetch remote content.
3. Local storage, retention and deletion
Private storage holds imported EML files, decoded attachments, rendered bodies and a database containing recent-file metadata, pins, reader position and export jobs and receipts. Metadata can include filenames, email subjects, sender addresses, sent dates, attachment counts and SHA-256 checksums. Preferences hold reading options, export destinations, naming templates, cached public ad settings and ad launch/frequency state. Google services maintain their own consent and SDK state.
Private copies default to 30 days. You can choose removal when the message closes, or retention for 7, 30, 90 or 365 days. Local history normally keeps up to 500 entries, with the existing size-limit exemption for pinned entries; the chosen time limit still applies. Clear Cache removes decoded and rendered data. Remove from Recents deletes that private source copy and its related records. Delete Local Data removes private copies, cache, recent-file records and export history. Original EML files and exported attachments are separate files and are not deleted by those actions. Uninstalling removes app-private data, subject to Android and your device's behavior.
App-private content has no additional app-level encryption layer. Android cloud backup and device-to-device transfer of private app data are disabled. Protect your device and keep independent backups of important original files and exports. We cannot retrieve local emails from a server copy because we do not hold one.
4. Advertising, optional rewards and consent
When enabled, Google Mobile Ads can display banner, native, interstitial, rewarded, rewarded-interstitial and app-open ads. Banners appear on Home; native ads appear below Recent Files. Interstitials may appear after leaving a fully verified export result, with a frequency limit. App-open ads are limited to eligible launches and long returns to idle Home, with guards around messages, dialogs, file opening and saving.
Settings can offer an optional rewarded ad for an ad-free current app process session. Successful multi-attachment exports can offer a rewarded-interstitial ad with an explanation and skip option. A reward is applied only when the SDK reports completion and ends when the process ends. Skipping, closing an ad, being offline or an unavailable ad never restricts reading, attachments, bulk saves, search, pins, naming templates or retention options. Development builds and test configurations use Google's demonstration ads.
The app requests non-personalized ads. Google and its services can still collect and share IP addresses, approximate location inferred from the network, device or advertising identifiers, app/ad interactions and diagnostic information for advertising, measurement, security and fraud prevention. We do not supply email contents to the ad SDK. SodCode adds no separate analytics or crash-reporting SDK.
Google's User Messaging Platform updates consent information on launch and displays a consent form where required. Ad delivery checks whether ads may be requested before initialization. An Ad privacy choices entry is provided in Settings when required by the SDK. Device advertising privacy settings also apply. Non-personalized ad requests do not replace consent where required.
See Google's Privacy Policy, Google services in partner apps and Google Mobile Ads data disclosures. Advertiser destinations are independent third-party services.
5. Public configuration and hosted pages
The app fetches a small public Firebase Realtime Database record at appConfig/emlReader/ads. It contains advertising on/off, test/live mode, per-format switches, ad unit IDs and an update timestamp. A valid copy is cached and refreshed at startup, on resume and approximately every minute. If a request fails, a valid cached copy or test-mode defaults are used. A changed master switch takes effect after the app receives the update; it cannot instantly reach an offline device.
Configuration requests contain no email content. Google/Firebase processes connection information needed to serve the request under its policies. Opening the published privacy or terms page uses your browser and the website's hosting services, which may process ordinary connection and request information. The bundled app copies can be read offline.
6. Your choices and contact
You can use local reading and saving features without an account, decline optional rewarded offers, manage consent where available, change retention and delete private email data. Android lets you manage app storage and relevant privacy permissions. If you contact us by email, we receive the information you choose to send and use it to respond; do not attach confidential emails unless needed and appropriate. We retain support correspondence only as needed for the request and legitimate recordkeeping.
The app is a general-purpose file utility and is not directed at children. Do not use it to process material you are not entitled to access. If you believe a child provided personal information directly to SodCode, contact us so we can address it. We may update this policy as the app changes; the date above identifies this version.