SMS PRIVACY POLICY
Privacy Policy for SMS Messages
Last Updated: September 18, 2026
This Privacy Policy describes how SMS Messages ("the App," "we," "us," or "our"), package name chat.messenger.textsms.messaging, handles information when you use our application. We are committed to protecting your privacy and being transparent about how the App works.
By downloading, installing, or using SMS Messages, you agree to the terms described in this Privacy Policy.
1. Overview
SMS Messages is a messaging application designed to replace your device's default SMS/MMS handler, providing a fast and private texting experience with spam blocking, a Private Chat vault, backup and restore, and customizable themes.
All of your message data is stored and processed locally on your device. SMS Messages does not upload, transmit, sell, or share your message content or message metadata to our servers or to any third party.
2. Information We Access
To function as a default SMS/MMS handler and provide its core features, the App requests the following permissions:
2.1 SMS and MMS Permissions
| Permission | Purpose |
|---|---|
| READ_SMS | Reads the device's SMS/MMS message store to display your conversation list and message threads, enable in-app search, and create backups of your own messages at your request. |
| RECEIVE_SMS | Receives incoming SMS messages via the SMS_DELIVER broadcast, which is only accessible to the device's default SMS handler. Without this permission, the App cannot deliver incoming messages to you. |
| RECEIVE_MMS | Receives incoming MMS messages via WAP_PUSH_DELIVER, allowing the App to download and display multimedia messages. |
| SEND_SMS | Sends SMS and MMS messages that you compose, including scheduled/delayed messages you set up and quick replies sent from the notification shade. |
These permissions are used exclusively to provide core messaging functionality. The App implements all components required by the Android platform to operate as a default SMS handler, including:
- A broadcast receiver for incoming SMS (
SMS_DELIVER) - A broadcast receiver for incoming MMS (
WAP_PUSH_DELIVER) - An activity that handles
SENDTOintents forsms:,smsto:,mms:, andmmsto:links - A service that handles
RESPOND_VIA_MESSAGEfor quick replies
2.2 Contacts
The App accesses your device contacts to display sender/recipient names instead of raw phone numbers, support group messaging, and enable caller identification for the after-call messaging feature.
2.3 Phone State / Call Log
The App uses call state information to detect when a call begins and ends, which powers the caller identification and after-call messaging feature.
2.4 Storage
The App accesses device storage to save and read local backup files, attachments, and media shared within MMS messages.
2.5 Google Drive Access (Optional)
If you choose to back up your conversations to Google Drive, the App will request access to your Google Drive account solely to upload and retrieve your own backup files. This connection is only established when you explicitly initiate a backup or restore action.
3. How We Use Information
Information accessed by the App is used only to:
- Display, send, and receive your SMS and MMS messages
- Show your conversation history and enable message search
- Identify callers and support after-call texting
- Block spam messages and unwanted numbers based on your blocklist or connected blocking services
- Protect conversations you move into Private Chat with a PIN
- Back up and restore your own messages at your request
- Apply your chosen themes, chat bubble styles, and display preferences
We do not use your SMS/MMS content, contacts, or call data for advertising, profiling, or any purpose unrelated to delivering the App's messaging features.
4. Data Storage and Transmission
- Local storage: Your messages, contacts references, and settings are stored locally on your device, within the system SMS/MMS provider and the App's local database.
- No server transmission of message content: SMS Messages does not operate servers that receive, log, or store your message content or metadata. The App contains no code that uploads, sells, or shares message data with us or third parties.
- User-initiated cloud backup: If you enable backup, your message data is transmitted only to your own Google Drive account, under your Google account's own privacy and security controls. We do not have access to backups stored in your Google Drive.
5. Private Chat
Conversations moved into Private Chat are protected by a 4-digit PIN that you set. Message previews for these conversations are hidden from notifications and the main inbox view. The PIN and associated private conversations are stored locally on your device only.
6. Spam and Call Blocking
The App allows you to maintain a personal blocklist of numbers and, optionally, connect trusted third-party blocking services to help filter spam messages and robocalls. If you choose to enable a third-party blocking service, that service's own privacy policy will govern how it processes any data shared with it. We recommend reviewing the privacy policy of any blocking service you choose to connect.
7. Foreground Services
The App uses the following foreground services, each limited to a specific, user-initiated or event-driven purpose:
7.1 Data Sync Foreground Service (RestoreBackupForegroundService)
- Purpose: Restores your own SMS/MMS messages from a backup file you select.
- How it starts: Only when you manually open the Backup screen, tap "Restore," choose a backup file (local storage or your Google Drive), and confirm. It is never started automatically, on boot, on a schedule, or by any background trigger.
- Why it's needed: Restoring a large message archive can involve writing tens of thousands of records and may take several minutes. A foreground service ensures the operation completes without being terminated by the system, while keeping you informed of its progress.
7.2 Phone Call Foreground Service (PhoneCallService)
- Purpose: Supports caller identification and after-call messaging.
- How it starts: Automatically when the device signals an active call state, and stops when the call ends. It is not active at any other time.
8. Data Sharing and Third Parties
We do not sell your personal data. We do not share your message content, contacts, or call data with advertisers or data brokers.
Limited sharing may occur only in these cases:
- Google Drive: When you choose to back up or restore data, files are transmitted directly to/from your own Google Drive account.
- Optional spam-blocking services: If you choose to connect a third-party blocking service, relevant data (such as sender numbers) may be shared with that service to identify spam, subject to that service's own privacy policy.
- Legal requirements: We may disclose information if required by law, regulation, legal process, or governmental request.
9. Data Security
We take reasonable technical and organizational measures to protect information handled by the App, including keeping message data local to your device and PIN-protecting Private Chat conversations. However, no method of electronic storage is 100% secure, and we cannot guarantee absolute security.
10. Children's Privacy
SMS Messages is not directed to children under the age of 13 (or the applicable age of digital consent in your region), and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us so we can address it.
11. Your Choices and Controls
- You can revoke SMS, contacts, phone, or storage permissions at any time through your device's system settings, though doing so may disable core App functionality.
- You can disable or remove SMS Messages as your default SMS handler at any time through your device settings.
- You can delete local backups or disconnect Google Drive access at any time from within the App or your Google account settings.
- You can delete Private Chat conversations and disable the PIN lock feature at any time.
12. Data Retention
Message data is retained locally on your device according to the standard behavior of the Android SMS/MMS provider and your own actions (e.g., deleting conversations). Backup files persist in your own Google Drive or local storage until you delete them.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in the App's features or legal requirements. We will update the "Last Updated" date at the top of this policy when changes are made. Continued use of the App after changes take effect constitutes acceptance of the revised policy.
14. Contact Us
If you have questions or concerns about this Privacy Policy or the App's data practices, please contact us at email.