Privacy Policy
Privacy Policy
Effective Date: 21 Sep 26
This Privacy Policy explains how the App accesses, collects, uses, and shares your information. We are committed to protecting your privacy while providing a reliable messaging experience.
1. Information We Access and Collect
To function as your default messaging application and provide supported features, we request specific Android permissions and collect the following data types:
SMS & MMS Data (READ_SMS, RECEIVE_SMS, SEND_SMS, RECEIVE_MMS, RECEIVE_WAP_PUSH, WRITE_SMS):
Purpose: As your default SMS handler, we require these permissions to send, receive, read, and manage your text and multimedia messages.
Data Handling: Message content is processed locally on your device. We do not upload, store, or share your message content on remote servers.
Location Data (ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION):
Purpose: We request precise and approximate location access to enable in-chat location sharing features.
Data Handling: Location data is accessed only when you actively choose to share it within a conversation. It is not tracked in the background or shared with third-party advertisers.
Contacts Data (READ_CONTACTS):
Purpose: We access your address book to display contact names and photos alongside your messages and to allow you to initiate new conversations. This data remains on your device.
Device and Advertising IDs (AD_ID):
Purpose: We collect your device's Advertising ID and standard device identifiers to serve advertisements and analyze app performance.
2. Device Permissions and Operations
Draw Over Other Apps (SYSTEM_ALERT_WINDOW): We require this permission to provide floating message notifications or chat head features, allowing you to quickly view or reply to messages without leaving your current active application.
Phone State (READ_PHONE_STATE): Used to manage cellular network connectivity for SMS/MMS transmission and to recognize active calls to handle app behavior accordingly.
Device Operations: Permissions such as POST_NOTIFICATIONS, INTERNET, and RECEIVE_BOOT_COMPLETED are utilized locally to alert you of incoming messages, download MMS media over the internet, and ensure message receiving services start automatically when your device restarts.
3. Third-Party Services and Data Sharing
This application integrates third-party SDKs for monetization, stability, and analytics. We share specific device identifiers with these approved services:
Google AdMob: We use Google AdMob to display advertisements. AdMob uses your Advertising ID and basic device information to serve ads. Depending on your region, we utilize the Google User Messaging Platform (UMP) to gather and manage your consent for personalized or non-personalized advertising.
Firebase Analytics, Crashlytics & Messaging: We utilize Firebase services to monitor app usage metrics, track feature engagement, deliver push notifications, and log crash reports. Firebase collects anonymous device identifiers, OS versions, and crash traces to help us identify bugs and improve app stability.
We explicitly do not sell, trade, or share your personal message content, location data, or contact lists with these third-party analytics or advertising networks.
4. Data Security
We rely on the standard security architecture of the Android operating system to protect the data processed by the App. The transmission of your SMS and MMS messages operates via your mobile carrier's cellular network, and the security of those transmissions is governed by your network provider.
5. Data Retention and User Control
Local Data: Your messages and contacts are managed locally. You can delete individual messages, entire conversation threads, or clear the App's storage directly from your device settings at any time.
Advertising Preferences: You can manage or revoke your consent for personalized advertising through the App's settings (if applicable via UMP) or by navigating to your Android device's system settings (Settings > Privacy > Ads).
Data Deletion: Uninstalling the App removes all locally stored data associated with it and immediately ceases any further data collection by integrated third-party SDKs.
6. Changes to This Privacy Policy
We may update this policy periodically to reflect updates to our code, new features, or changing platform requirements. Updates will be indicated by the "Effective Date" at the top of this document.
7. Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or how your data is handled, please contact us via the developer contact section provided on the App's Google Play Store listing.
Effective Date: 21 Sep 26
This Privacy Policy explains how the App accesses, collects, uses, and shares your information. We are committed to protecting your privacy while providing a reliable messaging experience.
1. Information We Access and Collect
To function as your default messaging application and provide supported features, we request specific Android permissions and collect the following data types:
SMS & MMS Data (READ_SMS, RECEIVE_SMS, SEND_SMS, RECEIVE_MMS, RECEIVE_WAP_PUSH, WRITE_SMS):
Purpose: As your default SMS handler, we require these permissions to send, receive, read, and manage your text and multimedia messages.
Data Handling: Message content is processed locally on your device. We do not upload, store, or share your message content on remote servers.
Location Data (ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION):
Purpose: We request precise and approximate location access to enable in-chat location sharing features.
Data Handling: Location data is accessed only when you actively choose to share it within a conversation. It is not tracked in the background or shared with third-party advertisers.
Contacts Data (READ_CONTACTS):
Purpose: We access your address book to display contact names and photos alongside your messages and to allow you to initiate new conversations. This data remains on your device.
Device and Advertising IDs (AD_ID):
Purpose: We collect your device's Advertising ID and standard device identifiers to serve advertisements and analyze app performance.
2. Device Permissions and Operations
Draw Over Other Apps (SYSTEM_ALERT_WINDOW): We require this permission to provide floating message notifications or chat head features, allowing you to quickly view or reply to messages without leaving your current active application.
Phone State (READ_PHONE_STATE): Used to manage cellular network connectivity for SMS/MMS transmission and to recognize active calls to handle app behavior accordingly.
Device Operations: Permissions such as POST_NOTIFICATIONS, INTERNET, and RECEIVE_BOOT_COMPLETED are utilized locally to alert you of incoming messages, download MMS media over the internet, and ensure message receiving services start automatically when your device restarts.
3. Third-Party Services and Data Sharing
This application integrates third-party SDKs for monetization, stability, and analytics. We share specific device identifiers with these approved services:
Google AdMob: We use Google AdMob to display advertisements. AdMob uses your Advertising ID and basic device information to serve ads. Depending on your region, we utilize the Google User Messaging Platform (UMP) to gather and manage your consent for personalized or non-personalized advertising.
Firebase Analytics, Crashlytics & Messaging: We utilize Firebase services to monitor app usage metrics, track feature engagement, deliver push notifications, and log crash reports. Firebase collects anonymous device identifiers, OS versions, and crash traces to help us identify bugs and improve app stability.
We explicitly do not sell, trade, or share your personal message content, location data, or contact lists with these third-party analytics or advertising networks.
4. Data Security
We rely on the standard security architecture of the Android operating system to protect the data processed by the App. The transmission of your SMS and MMS messages operates via your mobile carrier's cellular network, and the security of those transmissions is governed by your network provider.
5. Data Retention and User Control
Local Data: Your messages and contacts are managed locally. You can delete individual messages, entire conversation threads, or clear the App's storage directly from your device settings at any time.
Advertising Preferences: You can manage or revoke your consent for personalized advertising through the App's settings (if applicable via UMP) or by navigating to your Android device's system settings (Settings > Privacy > Ads).
Data Deletion: Uninstalling the App removes all locally stored data associated with it and immediately ceases any further data collection by integrated third-party SDKs.
6. Changes to This Privacy Policy
We may update this policy periodically to reflect updates to our code, new features, or changing platform requirements. Updates will be indicated by the "Effective Date" at the top of this document.
7. Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or how your data is handled, please contact us via the developer contact section provided on the App's Google Play Store listing.