Privacy Policy

Last updated: November 9, 2026

MailMySMS ("the app") is built, maintained, and this policy is written, by one independent developer — not a company. This page explains, plainly, what data the app accesses on your device, what it does with it, and what it never does.

The short version

MailMySMS reads the SMS, MMS, RCS, and call-log data already on your phone and writes it directly into the email account you configure, over a direct, encrypted IMAP connection. There is no server operated by the developer in between. Nothing is sent anywhere except the mailbox you choose. The app's source code is public, so you can verify all of this yourself.

What MailMySMS accesses, and why

• SMS and MMS messages (read and receive) — to forward them to your mailbox and to back up existing history.
• Call log — to forward call records to your mailbox.
• RCS messages — where your device's own messaging app stores them in a way Android exposes (gated behind the same SMS-read permission). Not every device or messaging app makes RCS history available this way; when it isn't, RCS messages are simply skipped.
• Phone state — to detect incoming/outgoing calls and which SIM they used, for call-log forwarding and dual-SIM labeling.
• Contacts — looked up locally, on-device, only to resolve a phone number to a saved contact name so the forwarded message is more readable. This lookup never leaves your device except as part of the message text written to your own mailbox.
• Notifications — to show you backup progress and status, required by Android for the app's background service to run.
• Network state and internet access — to connect to your email provider's IMAP server.
• Storage (on Android 9 and below only) — to write local export files to your device's Downloads folder. On newer Android versions this uses the system's scoped Downloads API instead, which needs no special permission.

MailMySMS requests each permission only when the corresponding feature (live forwarding, call-log forwarding, or local export) is actually enabled — not all at once, and not for anything unrelated to what you turned on. You can revoke any permission at any time from Android's app settings; the corresponding feature simply stops working until it's granted again.

Where your data goes

Your email account credentials (address and app password) are encrypted on-device using Android's EncryptedSharedPreferences (AES-256), and used only to open a direct, encrypted (IMAPS) connection to the mail server you specify. Each message or call record is written straight into your mailbox as an email, using IMAP's APPEND command — the same operation an email client uses to save a draft. There is no email actually sent through SMTP, and no server run by the developer that your data passes through, is logged by, or is stored on.

Local exports (an optional, separate feature) save a snapshot of your SMS/MMS/RCS and call history as XML/CSV files directly to your device's own storage. These files never leave your device unless you manually move or share them yourself.

What MailMySMS does not do

• It does not operate a backend server that your messages, calls, or credentials pass through.
• It does not include analytics, crash-reporting, advertising, or any third-party tracking SDK.
• It does not sell, rent, or share your data with any third party.
• It does not require creating an account with the developer — only with your own existing email provider.

Your email provider

Once a message is written to your mailbox, it is stored and processed by your email provider (e.g. Gmail) according to that provider's own privacy policy and terms — the same as any other email in your inbox. MailMySMS has no control over, and no visibility into, how your provider subsequently stores or processes that mail.

Data retention and deletion

MailMySMS itself only retains, on your device, a small local log of recent forwarding activity (for the app's own status display) and your settings — nothing is retained anywhere else. Messages already delivered to your mailbox, or files already saved by a local export, are not affected by uninstalling the app; you manage and delete those the same way you manage any other email or file.

Children's privacy

MailMySMS is not directed at children and does not knowingly collect data from children. It simply forwards SMS/call data already present on the device it's installed on, to a mailbox the device's owner configures.

Open source

MailMySMS's source code is public. If you want to verify any statement on this page against what the app actually does, read it yourself at github.com/antojose/mailmysms.

Changes to this policy

If this policy changes, the updated version will be posted on this same page with a revised "Last updated" date above.

Contact

Questions about this policy or how MailMySMS handles data: privacy@mailmysms.app or open a GitHub issue.