📜 Privacy Policy – Messages SMS - Phone Call
PRIVACY POLICY
Effective Date: November 6, 2026
Last Updated: November 6, 2026
This Privacy Policy describes how Messages SMS Text Messenger ("we", "us", or "Service Provider") collects, uses, processes, and protects your information when you use the Messages SMS - Phone Call mobile application (package name: `messages.chatsms.freechatmsg`, referred to as the "Application").
By installing or using the Application, you agree to the collection and use of information in accordance with this Privacy Policy.
---
1. Summary of Core Privacy Principles
On-Device Processing: Your personal SMS/MMS messages, Secret Vault conversations, Contact lists, and Call Logs remain stored locally on your device. We do not upload, store, or read your private messages or call history on our servers.
No Sale of Personal Data: We never sell, rent, or trade your personal data, SMS contents, contacts, or call logs to any third party.
Strict Purpose Limitation: Sensitive permissions (SMS, Call Log, Contacts, Phone State, Overlay) are used strictly to provide the Application's core user-facing messaging, calling, Caller ID, and After-Call features.
---
2. Information We Access and Process
A. SMS and MMS Data (On-Device Only)
When you set the Application as your Default SMS Handler, the Application accesses your SMS and MMS messages (`READ_SMS`, `RECEIVE_SMS`, `RECEIVE_MMS`, `SEND_SMS`, `WRITE_SMS`) to provide core functionality:
* Sending, receiving, displaying, and organizing text and multimedia messages.
* Automatically sorting messages locally on your device into categories (such as All, OTP, and Offers).
* Protecting user-selected conversations inside an on-device PIN-protected Secret Vault.
* Scheduling messages for future delivery and blocking unwanted spam messages.
* Creating and restoring local message backups initiated by you.
Data Handling: All SMS/MMS parsing, categorization, vault encryption, and backup creation happen 100% locally on your device. SMS and MMS content is never transmitted to our servers or shared with advertising networks.
B. Call Log, Phone State, and Caller ID Data
To provide the built-in Dialpad, Recent Call History, Caller ID, and After-Call summary screen, the Application requests `CALL_PHONE`, `READ_CALL_LOG`, and `READ_PHONE_STATE`:
Dialpad & Recent Calls: Allows you to initiate phone calls and view your incoming, outgoing, and missed call history within the Application.
Caller ID & Spam Identification: Detects incoming and outgoing call status to display caller information and help identify unknown or spam numbers (utilizing local phone number formatting via `libphonenumber` and Call Control DataShare services where applicable).
After-Call Feature: Displays an immediate post-call summary screen showing call details and allowing you to quickly message the caller, block the number, or set a reminder.
Data Handling: Your Call Log history is read locally on your device to populate your Recent Calls screen and After-Call card. We do not store or upload your call logs to external servers.
C. Contacts Information (On-Device Only)
The Application requests `READ_CONTACTS` solely to match phone numbers with contact names and profile photos saved on your device, and to support vCard (`.vcf`) contact sharing (`ez-vcard`). Your contact book remains on your device and is never uploaded or shared.
D. Installed Application Queries (Limited Package Visibility)
Through Android's `<queries>` manifest declaration, the Application checks solely for the installation status of specific communication apps on your device:
* WhatsApp (`com.whatsapp`)
* WhatsApp Business (`com.whatsapp.w4b`)
* Telegram (`org.telegram.messenger`)
* Gmail (`com.google.android.gm`)
* Standard Camera capture apps (`android.media.action.IMAGE_CAPTURE`)
Purpose: This check is performed strictly on-device to display direct one-tap communication shortcuts on the After-Call Screen (allowing you to open a chat with the caller in WhatsApp or Telegram) and to attach camera photos. We do not collect a broader list of your installed applications, and we never use package visibility data for advertising or user profiling.
E. Location Information
The Application may request approximate or precise location permissions (`ACCESS_COARSE_LOCATION`, `ACCESS_FINE_LOCATION`) via Google Play Services Location:
Purpose: Used only when you explicitly grant permission to support location-assisted features (such as displaying regional caller location context or sharing location details) and to serve regionally relevant advertisements and prevent ad fraud via Google AdMob and its mediation partners.
User Control: Location permission is optional. You can deny or revoke location access at any time in your Android System Settings (`Settings > Apps > Messages SMS - Phone Call > Permissions > Location`) without affecting core SMS or calling functionality.
F. Automatically Collected Data (Analytics, Diagnostics & Identifiers)
When the Application connects to the internet, integrated third-party SDKs automatically collect certain non-personal technical data:
Device & Advertising Identifiers: Google Advertising ID (`com.google.android.gms.permission.AD_ID`), device model, OS version, language, mobile network carrier, and screen resolution.
App Activity & Usage Data: Session duration, feature interaction events, app opens, and foreground/background states collected via Firebase Analytics.
Crash Logs & Diagnostics: Stack traces, ANR (Application Not Responding) reports, and performance metrics collected via Firebase Crashlytics.
In-App Purchase & Subscription Status: Transaction verification tokens processed securely through Google Play Billing (`com.android.billingclient:billing`) if you purchase ad-free upgrades or premium features.
---
3. Detailed Permissions Disclosure
| Permission | Purpose of Use |
| `READ_SMS`, `WRITE_SMS`, `SEND_SMS`, `RECEIVE_SMS`, `RECEIVE_MMS` | Core Default SMS/MMS handler features: reading, sending, receiving, organizing, archiving, blocking, and backing up messages.|
| `READ_CALL_LOG`, `CALL_PHONE`, `READ_PHONE_STATE` | Displaying Recent Call lists, placing calls from the in-app Dialpad, detecting incoming/ended calls for Caller ID, and triggering the After-Call screen. |
| `READ_CONTACTS` | Matching incoming/outgoing phone numbers with saved contact names and avatars on-device. |
| `SYSTEM_ALERT_WINDOW` | Displaying Caller ID popups, OTP quick-alerts, and the After-Call utility screen on top of other apps. |
| `SCHEDULE_EXACT_ALARM`, `RECEIVE_BOOT_COMPLETED`, `WAKE_LOCK` | Ensuring scheduled SMS messages and user reminders trigger accurately at the user-selected time, even after a device reboot. |
| `FOREGROUND_SERVICE`, `FOREGROUND_SERVICE_DATA_SYNC` | Running user-initiated SMS backup/restore tasks and reliable background message synchronization without system interruption. |
| `CAMERA`, `WRITE_EXTERNAL_STORAGE` | Capturing photos to attach to MMS messages and saving/restoring local SMS backup files on older Android versions. |
| `POST_NOTIFICATIONS` | Sending real-time alerts for incoming SMS/MMS messages, missed calls, and scheduled message reminders. |
| `ACCESS_FINE_LOCATION`, `ACCESS_COARSE_LOCATION` | Supporting optional location-context features and regional ad relevance (only if granted by the user). |
| `INTERNET`, `ACCESS_NETWORK_STATE`, `AD_ID` | Delivering advertisements, processing analytics/crash logs, checking remote configuration updates, and managing in-app purchases. |
---
4. Third-Party Services and SDKs
The Application integrates reputable third-party Software Development Kits (SDKs) for analytics, stability monitoring, consent management, monetization, and utility functions. These providers process data under their respective privacy policies:
Google Play Services & Google Play Billing: [https://policies.google.com/privacy](https://policies.google.com/privacy)
Google AdMob & User Messaging Platform (UMP): [https://support.google.com/admob/answer/6128543](https://support.google.com/admob/answer/6128543)
Google Analytics for Firebase & Firebase Crashlytics / Remote Config / Cloud Messaging: [https://firebase.google.com/support/privacy](https://firebase.google.com/support/privacy)
Meta Audience Network (Facebook Mediation): [https://www.facebook.com/about/privacy/](https://www.facebook.com/about/privacy/)
Unity LevelPlay / IronSource Mediation: [https://unity.com/legal/privacy-policy](https://unity.com/legal/privacy-policy)
Liftoff Monetize (Vungle Mediation): [https://liftoff.io/privacy-policy/](https://liftoff.io/privacy-policy/)
InMobi Mediation: [https://www.inmobi.com/privacy-policy](https://www.inmobi.com/privacy-policy)
Pangle (Bytedance Ad Network): [https://www.pangleglobal.com/privacy/enduser-en](https://www.pangleglobal.com/privacy/enduser-en)
Call Control DataShare (`com.callcontrol:datashare`): [https://www.callcontrol.com/privacy](https://www.callcontrol.com/privacy)
---
5. Legal Basis for Processing & Consent (GDPR / CCPA / DPDP Act)
Depending on your region (including the European Economic Area, United Kingdom, California, and India), we process data under the following legal bases:
Contractual Necessity: To provide the core SMS, MMS, Dialpad, Secret Vault, and Caller ID functionalities you request.
User Consent: We use Google's User Messaging Platform (UMP) SDK (`com.google.android.ump:user-messaging-platform`) to obtain verifiable prior consent from users in the EEA, UK, and applicable regions before serving personalized advertisements or accessing device identifiers.
Legitimate Interests: To maintain application stability, fix crashes, prevent fraud, and improve user experience.
Opt-Out of Personalized Ads: You may reset or delete your Google Advertising ID or opt out of personalized ads at any time via your Android device settings (`Settings > Google > All services > Ads`).
---
6. Data Retention and Deletion
On-Device Data (SMS, Vault, Backups, Call Logs, Contacts): Stored exclusively on your device using local Android databases and Realm storage (`io.realm`). You can delete individual messages, clear your Secret Vault, or remove backups at any time inside the Application. Uninstalling the Application permanently deletes all app-specific local databases from your device.
Analytics & Crash Data: Retained by Firebase and advertising partners in accordance with their standard data retention schedules (typically 60 days to 14 months).
Data Deletion Requests: Because we do not maintain user accounts or store your personal SMS/Call Log data on external servers, we hold no personal profile linked to your identity. If you wish to request deletion of any device-level analytics or ad identifier records associated with your Advertising ID, please email us at tiwarirahulkumar0101@gmail.com with your Advertising ID.
---
7. Data Security
We implement industry-standard technical and organizational safeguards to protect your information:
* All network transmissions between the Application and third-party SDKs (Firebase, AdMob, Google Play) are encrypted in transit using HTTPS/TLS.
* Sensitive messages placed in the Secret Vault are protected locally behind your custom PIN code.
---
8. Children's Privacy
The Application is intended for general audiences and is not directed to children under the age of 13 (or the minimum legal age in your jurisdiction). We do not knowingly collect personal information from children under 13. If you believe a child has provided information through the Application, please contact us immediately at tiwarirahulkumar0101@gmail.com so we can take appropriate action.
---
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect new features, SDK updates, or regulatory requirements. Any changes will be posted on this page with an updated "Last Updated" date. You are encouraged to review this Privacy Policy periodically.
---
10. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
Developer / Account Name: Messages SMS Text Messenger
Application Name: Messages SMS - Phone Call
Support Email: tiwarirahulkumar0101@gmail.com
Effective Date: November 6, 2026
Last Updated: November 6, 2026
This Privacy Policy describes how Messages SMS Text Messenger ("we", "us", or "Service Provider") collects, uses, processes, and protects your information when you use the Messages SMS - Phone Call mobile application (package name: `messages.chatsms.freechatmsg`, referred to as the "Application").
By installing or using the Application, you agree to the collection and use of information in accordance with this Privacy Policy.
---
1. Summary of Core Privacy Principles
On-Device Processing: Your personal SMS/MMS messages, Secret Vault conversations, Contact lists, and Call Logs remain stored locally on your device. We do not upload, store, or read your private messages or call history on our servers.
No Sale of Personal Data: We never sell, rent, or trade your personal data, SMS contents, contacts, or call logs to any third party.
Strict Purpose Limitation: Sensitive permissions (SMS, Call Log, Contacts, Phone State, Overlay) are used strictly to provide the Application's core user-facing messaging, calling, Caller ID, and After-Call features.
---
2. Information We Access and Process
A. SMS and MMS Data (On-Device Only)
When you set the Application as your Default SMS Handler, the Application accesses your SMS and MMS messages (`READ_SMS`, `RECEIVE_SMS`, `RECEIVE_MMS`, `SEND_SMS`, `WRITE_SMS`) to provide core functionality:
* Sending, receiving, displaying, and organizing text and multimedia messages.
* Automatically sorting messages locally on your device into categories (such as All, OTP, and Offers).
* Protecting user-selected conversations inside an on-device PIN-protected Secret Vault.
* Scheduling messages for future delivery and blocking unwanted spam messages.
* Creating and restoring local message backups initiated by you.
Data Handling: All SMS/MMS parsing, categorization, vault encryption, and backup creation happen 100% locally on your device. SMS and MMS content is never transmitted to our servers or shared with advertising networks.
B. Call Log, Phone State, and Caller ID Data
To provide the built-in Dialpad, Recent Call History, Caller ID, and After-Call summary screen, the Application requests `CALL_PHONE`, `READ_CALL_LOG`, and `READ_PHONE_STATE`:
Dialpad & Recent Calls: Allows you to initiate phone calls and view your incoming, outgoing, and missed call history within the Application.
Caller ID & Spam Identification: Detects incoming and outgoing call status to display caller information and help identify unknown or spam numbers (utilizing local phone number formatting via `libphonenumber` and Call Control DataShare services where applicable).
After-Call Feature: Displays an immediate post-call summary screen showing call details and allowing you to quickly message the caller, block the number, or set a reminder.
Data Handling: Your Call Log history is read locally on your device to populate your Recent Calls screen and After-Call card. We do not store or upload your call logs to external servers.
C. Contacts Information (On-Device Only)
The Application requests `READ_CONTACTS` solely to match phone numbers with contact names and profile photos saved on your device, and to support vCard (`.vcf`) contact sharing (`ez-vcard`). Your contact book remains on your device and is never uploaded or shared.
D. Installed Application Queries (Limited Package Visibility)
Through Android's `<queries>` manifest declaration, the Application checks solely for the installation status of specific communication apps on your device:
* WhatsApp (`com.whatsapp`)
* WhatsApp Business (`com.whatsapp.w4b`)
* Telegram (`org.telegram.messenger`)
* Gmail (`com.google.android.gm`)
* Standard Camera capture apps (`android.media.action.IMAGE_CAPTURE`)
Purpose: This check is performed strictly on-device to display direct one-tap communication shortcuts on the After-Call Screen (allowing you to open a chat with the caller in WhatsApp or Telegram) and to attach camera photos. We do not collect a broader list of your installed applications, and we never use package visibility data for advertising or user profiling.
E. Location Information
The Application may request approximate or precise location permissions (`ACCESS_COARSE_LOCATION`, `ACCESS_FINE_LOCATION`) via Google Play Services Location:
Purpose: Used only when you explicitly grant permission to support location-assisted features (such as displaying regional caller location context or sharing location details) and to serve regionally relevant advertisements and prevent ad fraud via Google AdMob and its mediation partners.
User Control: Location permission is optional. You can deny or revoke location access at any time in your Android System Settings (`Settings > Apps > Messages SMS - Phone Call > Permissions > Location`) without affecting core SMS or calling functionality.
F. Automatically Collected Data (Analytics, Diagnostics & Identifiers)
When the Application connects to the internet, integrated third-party SDKs automatically collect certain non-personal technical data:
Device & Advertising Identifiers: Google Advertising ID (`com.google.android.gms.permission.AD_ID`), device model, OS version, language, mobile network carrier, and screen resolution.
App Activity & Usage Data: Session duration, feature interaction events, app opens, and foreground/background states collected via Firebase Analytics.
Crash Logs & Diagnostics: Stack traces, ANR (Application Not Responding) reports, and performance metrics collected via Firebase Crashlytics.
In-App Purchase & Subscription Status: Transaction verification tokens processed securely through Google Play Billing (`com.android.billingclient:billing`) if you purchase ad-free upgrades or premium features.
---
3. Detailed Permissions Disclosure
| Permission | Purpose of Use |
| `READ_SMS`, `WRITE_SMS`, `SEND_SMS`, `RECEIVE_SMS`, `RECEIVE_MMS` | Core Default SMS/MMS handler features: reading, sending, receiving, organizing, archiving, blocking, and backing up messages.|
| `READ_CALL_LOG`, `CALL_PHONE`, `READ_PHONE_STATE` | Displaying Recent Call lists, placing calls from the in-app Dialpad, detecting incoming/ended calls for Caller ID, and triggering the After-Call screen. |
| `READ_CONTACTS` | Matching incoming/outgoing phone numbers with saved contact names and avatars on-device. |
| `SYSTEM_ALERT_WINDOW` | Displaying Caller ID popups, OTP quick-alerts, and the After-Call utility screen on top of other apps. |
| `SCHEDULE_EXACT_ALARM`, `RECEIVE_BOOT_COMPLETED`, `WAKE_LOCK` | Ensuring scheduled SMS messages and user reminders trigger accurately at the user-selected time, even after a device reboot. |
| `FOREGROUND_SERVICE`, `FOREGROUND_SERVICE_DATA_SYNC` | Running user-initiated SMS backup/restore tasks and reliable background message synchronization without system interruption. |
| `CAMERA`, `WRITE_EXTERNAL_STORAGE` | Capturing photos to attach to MMS messages and saving/restoring local SMS backup files on older Android versions. |
| `POST_NOTIFICATIONS` | Sending real-time alerts for incoming SMS/MMS messages, missed calls, and scheduled message reminders. |
| `ACCESS_FINE_LOCATION`, `ACCESS_COARSE_LOCATION` | Supporting optional location-context features and regional ad relevance (only if granted by the user). |
| `INTERNET`, `ACCESS_NETWORK_STATE`, `AD_ID` | Delivering advertisements, processing analytics/crash logs, checking remote configuration updates, and managing in-app purchases. |
---
4. Third-Party Services and SDKs
The Application integrates reputable third-party Software Development Kits (SDKs) for analytics, stability monitoring, consent management, monetization, and utility functions. These providers process data under their respective privacy policies:
Google Play Services & Google Play Billing: [https://policies.google.com/privacy](https://policies.google.com/privacy)
Google AdMob & User Messaging Platform (UMP): [https://support.google.com/admob/answer/6128543](https://support.google.com/admob/answer/6128543)
Google Analytics for Firebase & Firebase Crashlytics / Remote Config / Cloud Messaging: [https://firebase.google.com/support/privacy](https://firebase.google.com/support/privacy)
Meta Audience Network (Facebook Mediation): [https://www.facebook.com/about/privacy/](https://www.facebook.com/about/privacy/)
Unity LevelPlay / IronSource Mediation: [https://unity.com/legal/privacy-policy](https://unity.com/legal/privacy-policy)
Liftoff Monetize (Vungle Mediation): [https://liftoff.io/privacy-policy/](https://liftoff.io/privacy-policy/)
InMobi Mediation: [https://www.inmobi.com/privacy-policy](https://www.inmobi.com/privacy-policy)
Pangle (Bytedance Ad Network): [https://www.pangleglobal.com/privacy/enduser-en](https://www.pangleglobal.com/privacy/enduser-en)
Call Control DataShare (`com.callcontrol:datashare`): [https://www.callcontrol.com/privacy](https://www.callcontrol.com/privacy)
---
5. Legal Basis for Processing & Consent (GDPR / CCPA / DPDP Act)
Depending on your region (including the European Economic Area, United Kingdom, California, and India), we process data under the following legal bases:
Contractual Necessity: To provide the core SMS, MMS, Dialpad, Secret Vault, and Caller ID functionalities you request.
User Consent: We use Google's User Messaging Platform (UMP) SDK (`com.google.android.ump:user-messaging-platform`) to obtain verifiable prior consent from users in the EEA, UK, and applicable regions before serving personalized advertisements or accessing device identifiers.
Legitimate Interests: To maintain application stability, fix crashes, prevent fraud, and improve user experience.
Opt-Out of Personalized Ads: You may reset or delete your Google Advertising ID or opt out of personalized ads at any time via your Android device settings (`Settings > Google > All services > Ads`).
---
6. Data Retention and Deletion
On-Device Data (SMS, Vault, Backups, Call Logs, Contacts): Stored exclusively on your device using local Android databases and Realm storage (`io.realm`). You can delete individual messages, clear your Secret Vault, or remove backups at any time inside the Application. Uninstalling the Application permanently deletes all app-specific local databases from your device.
Analytics & Crash Data: Retained by Firebase and advertising partners in accordance with their standard data retention schedules (typically 60 days to 14 months).
Data Deletion Requests: Because we do not maintain user accounts or store your personal SMS/Call Log data on external servers, we hold no personal profile linked to your identity. If you wish to request deletion of any device-level analytics or ad identifier records associated with your Advertising ID, please email us at tiwarirahulkumar0101@gmail.com with your Advertising ID.
---
7. Data Security
We implement industry-standard technical and organizational safeguards to protect your information:
* All network transmissions between the Application and third-party SDKs (Firebase, AdMob, Google Play) are encrypted in transit using HTTPS/TLS.
* Sensitive messages placed in the Secret Vault are protected locally behind your custom PIN code.
---
8. Children's Privacy
The Application is intended for general audiences and is not directed to children under the age of 13 (or the minimum legal age in your jurisdiction). We do not knowingly collect personal information from children under 13. If you believe a child has provided information through the Application, please contact us immediately at tiwarirahulkumar0101@gmail.com so we can take appropriate action.
---
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect new features, SDK updates, or regulatory requirements. Any changes will be posted on this page with an updated "Last Updated" date. You are encouraged to review this Privacy Policy periodically.
---
10. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
Developer / Account Name: Messages SMS Text Messenger
Application Name: Messages SMS - Phone Call
Support Email: tiwarirahulkumar0101@gmail.com