Last Updated: [21 Feb 2026]
This Privacy Policy details how [Secure Chat Messenger] ("we," "us," or "our") manages your information. We are committed to upholding your privacy and providing complete transparency, in compliance with international data regulations like the GDPR and the Google Play Developer Policy.
We do not gather, save, or utilize any personally identifiable information (PII) when you download or engage with our application.
If you voluntarily choose to contact us or provide personal information (e.g., for support), we may use that data only to:
Enhance our service quality and improve the user experience.
Respond efficiently to your support inquiries or requests.
Fulfill necessary legal and regulatory obligations.
We will only disclose your personal information in these specific circumstances:
Upon receiving your explicit, clear authorization.
When required by a judicial order or other legal procedure.
In response to requests from authorized governmental or public entities.
To safeguard and enforce our legal rights.
We may collect certain data that does not identify you personally. This non-personal information includes:
Your device's model and operating system version.
Your chosen language and geographical location.
The package identifier of our app installed on your device.
Application usage statistics (frequency and session length).
Details on your interaction with the app's various features.
This anonymous data serves to:
Analyze user behavior patterns and trends.
Optimize app performance and usability.
Facilitate the delivery of relevant advertisements via platforms like AdMob.
Note: Should any non-personal data ever be merged with personal details, we will treat the entire dataset as personal information.
Our application requires the following permissions to operate correctly:
android.permission.READ_SMS :- Used to read SMS messages in order to display conversations, enable search by name or number, archive messages, and perform backup and restore operations.
WRITE_SMS: Required to save sent messages, delete or archive conversations, and update message states (read/unread).
SEND_SMS: Allows the application to send SMS messages initiated by the user, including scheduled SMS messages.
RECEIVE_SMS: Required to receive incoming SMS messages and display them in the conversation list.
RECEIVE_MMS: Used to receive MMS messages including images and media attachments.
READ_PHONE_STATE : Used to detect call state changes (such as when a call ends) in order to trigger After Call features like opening the message screen, reminder screen, or related options.The app may access the device phone number only to display it inside the application. The phone number is not collected, stored, or transmitted to any external server.
POST_NOTIFICATIONS : Required to display notifications for new incoming messages, scheduled message alerts, and reminders.
CHANGE_NETWORK_STATE: Used to manage network connectivity behavior during MMS sending operations.
ACCESS_NETWORK_STATE: Used to detect current network availability before sending MMS or performing message synchronization tasks.
INTERNET: Required for MMS transmission and any backup/restore functionality that requires network communication.
CHANGE_WIFI_STATE: Used to manage WiFi connectivity when sending or receiving MMS messages.
READ_CONTACTS :- Used to display contact names in conversations, enable contact search, and share contacts via text message.
WAKE_LOCK :- Prevents the device from sleeping while sending scheduled SMS messages or processing MMS to ensure reliable message delivery.
SCHEDULE_EXACT_ALARM :- Required to send scheduled SMS messages at the exact time selected by the user.
ACCESS_WIFI_STATE :- Used to detect WiFi connectivity status for MMS sending optimization and certain after-call logic handling.
RECEIVE_BOOT_COMPLETED :- Used to restore scheduled messages and reminders after device reboot.
FOREGROUND_SERVICE :- Required to run foreground services for scheduled message processing, MMS handling, and after-call activity handling in compliance with Android background execution limitations.
FOREGROUND_SERVICE_SPECIAL_USE :- When a phone call ends, the app performs immediate post-call actions such as opening the messaging screen, composing a message, or setting a reminder. Since this may occur while the app is in the background, Android requires a properly declared foreground service type to ensure reliable and compliant execution
SYSTEM_ALERT_WINDOW :- Used to display the After Call overlay screen with messaging and reminder options when a phone call ends.
Default SMS Application Requirement :- This application operates as a full-featured SMS and MMS messaging app. To send, receive, read, and manage SMS/MMS messages, the user is required to set the app as the default SMS application. SMS-related permissions are used strictly for core messaging functionality and are active only when the app is selected as the default SMS handler by the user.
We integrate services from other companies (third-party SDKs) to support development and features, including:
These external providers manage and process data according to their individual privacy policies.
In adherence to the General Data Protection Regulation (GDPR):
You maintain the right to view, modify, or request the deletion of your personal data.
We ensure complete clarity regarding the data we collect and our reasons for its use.
You may withdraw your consent at any time by simply uninstalling the application or by contacting us directly.
We do not intentionally gather any data from children under the age of 13 (or the required minimum age in your jurisdiction). If you suspect a child has submitted data to us, please notify us immediately so we can promptly delete the information from our records.
We implement standard security practices within the industry, such as access controls, encryption, and firewalls, to protect the non-personal data we collect. However, it must be acknowledged that no electronic storage or transmission method over the internet can guarantee 100% security.
This Privacy Policy may be updated periodically. All modifications will be posted on this page, and users are encouraged to review this document regularly.
Our app uses the Google AdMob SDK to display advertisements. While we aim for a non-disruptive ad experience, we cannot fully control external ad services, which may occasionally result in unexpected behavior.
For any questions or concerns regarding this Privacy Policy, please contact us at:
📧 thewebmakers.club@gmail.com