Last updated:
SMS to Email+ (SME+) is developed by DRC Labs. This Privacy Policy explains how we handle information when you use the app. Optional reporting described below applies to versions that offer the Usage & crash reporting setting; updating this policy does not enable reporting or add features to an older installed version.
With Android SMS permission, the app accesses incoming SMS messages and sender numbers on your device to apply your filters and forward qualifying messages when forwarding is enabled, including while the app is in the background. The current app does not read your address book or other apps' notifications. Its notification permission is used to display its own notifications.
Recipient email addresses, SMTP server details and credentials, filters, appearance preferences, and local activity records are stored on your device for the app's features. We do not operate a central SMS forwarding server.
When a qualifying message is waiting to be emailed, the app may temporarily keep its sender, message content, original received time, and delivery status in encrypted storage on your device. Android can then retry temporary connection failures after connectivity returns. The pending copy is removed after successful delivery or a final failure; a final failed item can be queued again only when you choose Retry now. Only a random work identifier, not message content, is provided to Android's background-work scheduler.
When you enable forwarding or send a test email, the app sends the information needed to deliver that email through your chosen SMTP provider to your configured recipients. This can include message content, sender information, recipient addresses, and authentication details needed by the provider. Your email provider and recipient mail systems handle that information under their own policies. Turning off optional reporting does not stop email forwarding.
Usage & crash reporting is optional and off by default, including when there is no previously saved explicit choice. You can enable it on the Welcome screen or in Settings, and change your choice in Settings at any time. Forwarding works without it. The in-app Learn more page explains the choice before you enable it.
When enabled, Google Analytics for Firebase receives app activity and technical information to help us understand usage and improve the app. This includes app opens, sessions, engagement, screen activity, app version, operating-system/device details, language, approximate location derived from IP, and app-instance or installation identifiers. It is not completely anonymous: identifiers can distinguish installations across reporting events.
Our limited product events cover:
These custom events use fixed categories, yes/no indicators, or broad count ranges. Change events describe activity, not a complete record of every user's current settings. Reporting represents installations that opted in, not every person who installed the app. Actions that were not recorded while reporting was off are not replayed after opt-in.
When reporting is enabled, Firebase Crashlytics, a Google service, receives technical crash information to help identify and fix failures. Reports may include stack traces, exception information, relevant application state, app/device and operating-system details, installation identifiers, and recent Analytics activity. We do not set a custom Crashlytics user ID or attach custom free-text diagnostic logs.
After you opt in, eligible crash reporting begins with your next fresh app run. Reports are uploaded on a later app start only when the previous run stayed opted in and reporting remains enabled. Crashlytics automatic uploads are disabled; the app controls approval of pending uploads.
We do not intentionally attach SMS or email message content, verification codes, phone numbers, contact names, recipient email addresses, SMTP hostnames or credentials, filter keywords or regular expressions, or local activity logs to Analytics or Crashlytics reporting. Crash reports can still contain incidental technical context or exception messages generated by an error, so we do not promise that diagnostics can never contain user-related information.
SME+ does not display ads or sell user data. Advertising ID collection and personalized advertising are disabled. We do not enable Google Signals or optional Google Analytics account data sharing.
Turning the switch off stops new Analytics collection and future crash-upload approvals and resets local Analytics data. Crash diagnostics may still be stored locally by the SDK; reports from off or mixed-consent runs are queued for deletion rather than upload. Local deletion is asynchronous. Uploads already started may finish, and turning the switch off does not delete reports already sent to Google.
Google processes optional usage and diagnostic information for us to provide Analytics and Crashlytics. DRC Labs uses those reports for app improvement and reliability. Service providers may process information in countries outside your own, including the United States, under the applicable service terms and data-transfer safeguards. Google Analytics has its own service terms. See Firebase Privacy and Security and Google's Privacy Policy for provider information.
Your chosen email provider separately processes the messages you direct the app to send. If you contact support, we receive your email address and whatever information you choose to include, for responding to your request. Please do not send passwords, verification codes, or private messages when reporting an issue.
The app uses Android security features and encrypted storage for SMTP credentials. Firebase reporting is encrypted in transit. SMTP connection security depends on the supported mode and your chosen provider's configuration; use a provider that supports encrypted connections. No storage or transmission method can be guaranteed completely secure.
You can disable forwarding, change or remove saved settings, revoke Android permissions, turn optional reporting off, or uninstall the app. Revoking SMS permission prevents the app from receiving messages for forwarding. You do not need to agree to optional reporting to use forwarding.
Depending on where you live, you may have rights to access, correct, delete, or receive a copy of personal information, restrict or object to processing, withdraw consent, or complain to your local data-protection authority. To make a request, contact DRC Labs below. We may need information sufficient to verify and locate the relevant data. We do not send your email address as an Analytics user ID, so an email address alone may not identify an installation's reports. Please contact us before clearing app storage if you want help with a request; do not send credentials or message content. Withdrawing consent does not affect processing already carried out.
We will update this page and its Last updated date when our practices change. Where required, we will provide additional notice or ask for a new choice before using information for a materially different purpose.
For questions regarding this Privacy Policy, please contact: