Privacy Policy for SMS Death Guard
Last updated: November 21, 2026
SMS Death Guard is developed and published by Amin Bahrami. This Privacy Policy explains how the Android application handles information when you use its messaging, scanning, and message-management features.
Application ID: com.aminbahrami.smsdeathguard
Privacy contact: ABP.Bahrami@gmail.com
1. Messages and on-device scanning
SMS Death Guard accesses SMS and MMS information to provide messaging features and perform scans you request. Depending on the feature and the access permitted by Android, this information may include sender and recipient addresses, message content, attachments, timestamps, delivery information, and technical message records.
Security analysis runs on your device. The scanning feature does not upload message content or scan records to a developer-operated server.
Scan results and cleanup history are stored locally. These records may include sender information, detection details, timestamps, and the outcome of a deletion attempt.
Access to pending or incomplete messages depends on your Android version and device restrictions. Becoming the default SMS application does not guarantee access to every message record.
2. Permissions and the default SMS role
The application requests the default SMS role and relevant permissions to receive, display, send, and manage messages.
Where applicable, it also uses:
-
Notification permission to display messaging and application notifications.
-
Phone-state permission to identify available SIM subscriptions and support SIM selection.
-
Device and software information, such as Android version, security patch level, manufacturer, and model, to display device information and support diagnostics.
The application stores the identity of the previous default messaging application, when available, to help you return to it later.
You can change your default messaging application and manage permissions in Android Settings. Disabling access may prevent related features from working.
3. Sending and receiving SMS and MMS
When you send a message, its content, recipient information, and any selected attachments are transmitted through Android messaging services and your mobile carrier to the intended recipient.
MMS transfers may also involve your carrier’s multimedia messaging infrastructure. These communications are necessary to provide the messaging features you choose to use.
SMS and MMS are not end-to-end encrypted by SMS Death Guard. Their delivery and retention are also subject to your carrier’s and the recipient’s practices.
4. Google Play purchases and updates
The application uses Google Play services to verify purchase eligibility and check for application updates.
For license verification, the application requests a licensing response from Google Play and processes the signed response to determine access. License-verification information may be cached locally.
The Google Play in-app update library processes device metadata, application version information, and information about installed application modules or asset packs to determine update availability and size.
Google handles purchases, payment information, and its own service operations under its privacy policy and terms. SMS Death Guard does not ask you to enter payment-card details into the application.
Google Privacy Policy: https://policies.google.com/privacy
5. Diagnostic reports you choose to share
You can generate a diagnostic report and choose whether and where to share it using Android’s sharing interface.
The report includes information such as the application and analysis-engine versions, Android version, security patch level, device manufacturer and model, default SMS role status, scan timing, and the number of history records.
The generated report does not include phone numbers, SMS message bodies, raw message data, device fingerprints, or message hashes.
A report is not automatically sent to the developer. If you share it, the destination application or recipient handles that copy under its own practices.
6. Support communications
If you contact us by email, we receive your email address and the information you choose to include in your message or attachments.
We use this information to respond to your request and investigate the issue you report. Email hosting providers may process these communications to deliver and store them.
Please avoid sending private messages, passwords, payment details, or other sensitive information that is unnecessary for your support request.
7. Advertising and analytics
The current application does not include advertising SDKs or third-party analytics SDKs.
We do not sell your personal information or use your message content for targeted advertising.
8. Data retention and deletion
Application settings, cached license information, and scan history are stored on your device for use by the application.
You can clear scan history using the application’s settings. Clearing application storage or uninstalling the application removes its private local data.
Messages stored in Android’s shared messaging database are separate from the application’s private data. Uninstalling SMS Death Guard does not necessarily delete those messages.
Message cleanup requires your confirmation. Depending on the available options and system access, you may choose to delete an identified message record or a specified group of pending records from the same sender. Deletion may be irreversible.
Exported reports remain wherever you save or share them until you or the recipient deletes them. Clearing application history does not delete exported copies.
Support correspondence is retained only as long as needed to address the request and meet applicable legal obligations. You may request deletion of support correspondence by contacting [SUPPORT EMAIL].
Google, your mobile carrier, and recipients control the retention of information processed through their respective services.
9. Your choices
You can:
-
Decide whether to start a scan.
-
Review available findings before confirming cleanup.
-
Change your default messaging application.
-
Grant or revoke permissions in Android Settings.
-
Clear locally stored scan history.
-
Choose whether to export or share a diagnostic report.
-
Contact us about information you have provided directly to us.
The application does not create a separate SMS Death Guard user account.
10. Security
The application uses Android’s application storage and permission mechanisms to restrict access to its private data.
No storage or transmission method can guarantee absolute security. Information you send through SMS, MMS, email, or another application is also subject to the security protections of those services.
11. Changes to this policy
We may update this policy when application features or data-handling practices change. The latest version will be published on this page with an updated date.
12. Contact
For privacy questions or requests relating to information you have sent directly to us, contact:
Amin Bahrami
Email: ABP.Bahrami@gmail.com