Privacy policy

 Part 1: General Compliance Questions

Does your app collect or share any required user data types?


Yes


Is all user data encrypted in transit?


Yes (Data transmitted via Firebase and APIs is secured via HTTPS/TLS).


Do you provide a mechanism for users to request data deletion?


Yes (If your app handles user data externally or via account features; otherwise, select No if local messages stay strictly on-device).


Does your app follow the Google Play Families policy?


No (Assuming your messaging app is intended for a general audience).


Part 2: Detailed Data Types, Collection, and Sharing Declarations

Based on your app's libraries (READ_SMS, READ_CONTACTS, Firebase Analytics, Crashlytics, and Google Mobile Ads SDK), you must declare the following data types:


1. Personal Info

Data Type: Phone Number


Collected: Yes


Shared: No


Required or Optional: Required (Core app functionality to send/receive SMS).


Purposes: App functionality.


Data Type: Contacts


Collected: Yes (Accessed via READ_CONTACTS to display names in your messaging UI).


Shared: No


Required or Optional: Optional (Users can choose to grant or deny contact permissions).


Purposes: App functionality.


2. Messages

Data Type: SMS or MMS


Collected: Yes (Processed locally to render texts). Note: If texts are processed ephemerally on-device and not sent to your own developer servers, you still declare collection if your app reads/writes them via READ_SMS / WRITE_SMS.


Shared: No


Required or Optional: Required (Core functionality).


Purposes: App functionality.


3. Photos and Videos

Data Type: Photos / Videos


Collected: Yes (Captured via built-in camera or selected from storage to send via MMS).


Shared: No


Required or Optional: Optional.


Purposes: App functionality.


4. App Activity

Data Type: App Interactions (Indexed by Firebase Analytics)


Collected: Yes


Shared: No (Collected by Google Firebase SDK on your behalf).


Required or Optional: Required.


Purposes: Analytics.


5. App Info and Performance

Data Type: Crash Logs & Diagnostics (Indexed by Firebase Crashlytics and Performance Monitoring)


Collected: Yes


Shared: No


Required or Optional: Required.


Purposes: Analytics, App functionality.


6. Device or Other IDs

Data Type: Device or other IDs (Required by Google Mobile Ads SDK and Firebase)


Collected: Yes


Shared: Yes (Because advertising SDKs transmit device identifiers to ad networks for ad targeting).


Required or Optional: Required.


Purposes: Advertising or marketing, Analytics.

Popular posts from this blog

Terms of Use

 Terms of Use Effective Date: August 19, 2026 App Name: Messages : SMS & Text Home Package Name: com.smstext.messenger.defaultapp 1. Acceptance of Terms By downloading, installing, or using Messages : SMS & Text Home, you agree to be bound by these Terms of Use. If you do not agree to these terms, do not install or use the application. These terms constitute a legally binding agreement between you and the application developer regarding your use of the app and its integrated services. 2. Changes to Terms We reserve the right to modify, update, or change these Terms of Use at any time. Any changes will become effective immediately upon posting the updated terms within or alongside the application. Your continued use of the app following any modifications signifies your acceptance of the updated terms. 3. License and App Usage Subject to your compliance with these terms, we grant you a limited, non-exclusive, non-transferable, revocable license to download, install, and use M...
Read more