📄 Privacy Policy
Privacy Policy for Messages: Text & SMS Messaging
Effective Date: June 4, 2026
1. Introduction
Welcome to Messages: Text & SMS Messaging (the "App"), developed by [Your Developer Account Name] ("we," "us," or "our"). We are committed to protecting your privacy and ensuring transparency about how your data is handled.
Because this App functions as a Default SMS Handler, it requires access to highly sensitive device permissions. This policy explains what data we collect, why we collect it, how it is secured, and how it interacts with the third-party services integrated into the App.
2. Core Functionality & Sensitive Data (SMS, MMS, Contacts, Call Logs)
To operate as your primary messaging application, the App requires direct access to your local communication data.
- SMS & MMS Data: The App requires the READ_SMS, SEND_SMS, and RECEIVE_SMS permissions to display your conversations and allow you to send/receive messages.
- Call Log Data (Integrated Inbox): The App requires the READ_CALL_LOG permission to display recent missed calls within your message threads, allowing you to quickly reply to missed callers via text.
- Contact Information: The App requires READ_CONTACTS to display the names and avatars of your contacts alongside your messages.
How this data is handled:
- 100% Local Processing: Your SMS messages, MMS media, call history, and contact lists are processed entirely locally on your device.
- No External Uploads: We do not upload, transmit, or store your private communications or contact lists on our servers.
- No Third-Party Sharing: Your private message and call log data is never shared with third-party advertisers, analytics providers, or any other external entities.
3. Location Data
The App includes the ability to share your location with a contact via an MMS message.
- If you choose to use this feature, the App accesses your device location (Precise/Approximate) only at the moment you choose to share it.
- This location data is embedded into the message sent to your contact. It is not tracked continuously, nor is it uploaded to our servers or shared with advertisers.
4. Third-Party Integrations & Data Collection
While your private messages remain strictly on your device, our App utilizes industry-standard third-party SDKs to ensure stability, track app performance, and serve advertisements. These services may automatically collect specific technical data:
A. Google Play Services & Firebase (Analytics, Crashlytics, Performance Monitoring)
We use Google Firebase to monitor the App for crashes and technical errors.
Data Collected: Device information (model, OS version), App launch times, hang rates, crash logs, and general diagnostic data.
Purpose: This data is collected solely to help us identify bugs, improve App stability, and ensure a smooth user experience.
Privacy: This technical data does not include any of your personal SMS/MMS content. You can learn more by reading the Google Privacy Policy.
B. Google Mobile Ads SDK (AdMob)
To support the ongoing development of this free App, we use the Google Mobile Ads SDK to display advertisements.
Data Collected: The SDK automatically collects your IP address, user product interactions, diagnostic information, and your device's Advertising ID.
Purpose: This data is used for ad delivery, analytics, and fraud prevention.
Opting Out: You can reset or delete your Advertising ID at any time by navigating to your Android device settings (Settings > Privacy > Ads).
5. Permissions Declared
Below is a summary of the key Android permissions requested by the App and their purpose:
Communication: SEND_SMS, READ_SMS, RECEIVE_SMS, RECEIVE_MMS, WRITE_SMS (Required to act as the default SMS app).
Identity & Logging: READ_CONTACTS, READ_PHONE_STATE, READ_CALL_LOG, WRITE_CALL_LOG (Required to map numbers to names and show integrated call history).
Media & Sharing: CAMERA, RECORD_AUDIO, ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION (Required only when attaching photos, voice notes, or location to a message).
System: POST_NOTIFICATIONS, FOREGROUND_SERVICE (Required for receiving messages in the background and notifying you).
Advertising: AD_ID (Required by Google policies for serving ads).
6. Data Security and Encryption
All data transmitted by our integrated third-party SDKs (such as diagnostic logs and ad requests) is encrypted in transit using Transport Layer Security (TLS). Your private SMS/MMS data remains secured within the Android system's native telephony database on your device.
7. User Rights and Data Deletion
Because your messages and contacts are processed locally, you maintain complete control over your data:
You can delete individual messages, entire threads, or call log entries directly within the App.
Uninstalling the App will completely remove its access to your data.
You can manage ad personalization and reset your Advertising ID via your Android system settings.
8. Changes to This Privacy Policy
We may update our Privacy Policy from time to time to reflect changes in Google Play policies or App features. We will notify you of any significant changes by updating the "Effective Date" at the top of this document.
9. Contact Us
If you have any questions or concerns about this Privacy Policy or how your data is handled, please contact us at: playconsole.s2soft@gmail.com
Effective Date: June 4, 2026
1. Introduction
Welcome to Messages: Text & SMS Messaging (the "App"), developed by [Your Developer Account Name] ("we," "us," or "our"). We are committed to protecting your privacy and ensuring transparency about how your data is handled.
Because this App functions as a Default SMS Handler, it requires access to highly sensitive device permissions. This policy explains what data we collect, why we collect it, how it is secured, and how it interacts with the third-party services integrated into the App.
2. Core Functionality & Sensitive Data (SMS, MMS, Contacts, Call Logs)
To operate as your primary messaging application, the App requires direct access to your local communication data.
- SMS & MMS Data: The App requires the READ_SMS, SEND_SMS, and RECEIVE_SMS permissions to display your conversations and allow you to send/receive messages.
- Call Log Data (Integrated Inbox): The App requires the READ_CALL_LOG permission to display recent missed calls within your message threads, allowing you to quickly reply to missed callers via text.
- Contact Information: The App requires READ_CONTACTS to display the names and avatars of your contacts alongside your messages.
How this data is handled:
- 100% Local Processing: Your SMS messages, MMS media, call history, and contact lists are processed entirely locally on your device.
- No External Uploads: We do not upload, transmit, or store your private communications or contact lists on our servers.
- No Third-Party Sharing: Your private message and call log data is never shared with third-party advertisers, analytics providers, or any other external entities.
3. Location Data
The App includes the ability to share your location with a contact via an MMS message.
- If you choose to use this feature, the App accesses your device location (Precise/Approximate) only at the moment you choose to share it.
- This location data is embedded into the message sent to your contact. It is not tracked continuously, nor is it uploaded to our servers or shared with advertisers.
4. Third-Party Integrations & Data Collection
While your private messages remain strictly on your device, our App utilizes industry-standard third-party SDKs to ensure stability, track app performance, and serve advertisements. These services may automatically collect specific technical data:
A. Google Play Services & Firebase (Analytics, Crashlytics, Performance Monitoring)
We use Google Firebase to monitor the App for crashes and technical errors.
Data Collected: Device information (model, OS version), App launch times, hang rates, crash logs, and general diagnostic data.
Purpose: This data is collected solely to help us identify bugs, improve App stability, and ensure a smooth user experience.
Privacy: This technical data does not include any of your personal SMS/MMS content. You can learn more by reading the Google Privacy Policy.
B. Google Mobile Ads SDK (AdMob)
To support the ongoing development of this free App, we use the Google Mobile Ads SDK to display advertisements.
Data Collected: The SDK automatically collects your IP address, user product interactions, diagnostic information, and your device's Advertising ID.
Purpose: This data is used for ad delivery, analytics, and fraud prevention.
Opting Out: You can reset or delete your Advertising ID at any time by navigating to your Android device settings (Settings > Privacy > Ads).
5. Permissions Declared
Below is a summary of the key Android permissions requested by the App and their purpose:
Communication: SEND_SMS, READ_SMS, RECEIVE_SMS, RECEIVE_MMS, WRITE_SMS (Required to act as the default SMS app).
Identity & Logging: READ_CONTACTS, READ_PHONE_STATE, READ_CALL_LOG, WRITE_CALL_LOG (Required to map numbers to names and show integrated call history).
Media & Sharing: CAMERA, RECORD_AUDIO, ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION (Required only when attaching photos, voice notes, or location to a message).
System: POST_NOTIFICATIONS, FOREGROUND_SERVICE (Required for receiving messages in the background and notifying you).
Advertising: AD_ID (Required by Google policies for serving ads).
6. Data Security and Encryption
All data transmitted by our integrated third-party SDKs (such as diagnostic logs and ad requests) is encrypted in transit using Transport Layer Security (TLS). Your private SMS/MMS data remains secured within the Android system's native telephony database on your device.
7. User Rights and Data Deletion
Because your messages and contacts are processed locally, you maintain complete control over your data:
You can delete individual messages, entire threads, or call log entries directly within the App.
Uninstalling the App will completely remove its access to your data.
You can manage ad personalization and reset your Advertising ID via your Android system settings.
8. Changes to This Privacy Policy
We may update our Privacy Policy from time to time to reflect changes in Google Play policies or App features. We will notify you of any significant changes by updating the "Effective Date" at the top of this document.
9. Contact Us
If you have any questions or concerns about this Privacy Policy or how your data is handled, please contact us at: playconsole.s2soft@gmail.com