Max Messages — Privacy Policy

This Privacy Policy describes how Max SMS ("we", "us", "our") collects, uses, and shares information when you use the Max SMS Android application (the "App"). It is tailored for distribution on Google Play and complements the Data safety section you see on the store listing.

By using the App, you agree to this Policy.

Overview

• Core purpose: provide SMS/MMS messaging features on your device, plus an optional "Wishes" library you can browse and share as text.
• No ads. We do not sell your personal data.
• Message content stays on your device and is not uploaded to our servers.
• We integrate Google Firebase services for analytics (may be enabled depending on build), crash reporting, performance monitoring, and to deliver the Wishes content using anonymous sign‑in.

Data We Process

On your device (not sent to our servers)

• SMS/MMS content and attachments: message bodies, media, timestamps, thread participants, and statuses for sending/delivery.
• Contacts data: names, phone numbers, and vCards used for matching and display.
• App settings and preferences: UI theme, notification preferences, categories, and similar configuration.
• Local backups/exports you trigger.

These are stored in Android's SMS/MMS provider and the App's local storage/Room database, and remain on your device unless you choose to export/share them.

Through third‑party services (Google Firebase)

Depending on the distributed variant and configuration, the App may send limited information to Google Firebase services:

• Analytics events (Firebase Analytics): in‑app events, app opens, device model, OS/app version, language, approximate location (inferred), and device identifiers used by Firebase.
• Crash reports (Firebase Crashlytics): stack traces and diagnostics (state surrounding a crash, device model, OS/app version, limited device identifiers).
• Performance metrics (Firebase Performance): app start time, screen render times, network request timings and metadata (not message content), device and app info.
• Wishes content access (Firestore + Firebase Auth): anonymous authentication and read‑only fetches of wishes/templates. No personal SMS/MMS content is written to Firestore.

Provider: Google LLC. Data may be processed outside your country.

Permissions We Request (Why)

• READ_SMS, WRITE_SMS, SEND_SMS, RECEIVE_SMS, RECEIVE_MMS, android.provider.Telephony.SMS_RECEIVED: core messaging.
• READ_CONTACTS: show contact names/avatars and vCard viewing.
• READ_PHONE_STATE: SIM handling and reliability.
• POST_NOTIFICATIONS: message alerts and quick actions (reply, mark read, delete).
• WRITE_EXTERNAL_STORAGE (maxSdkVersion 28): backups/exports on older Android versions.
• WAKE_LOCK: reliable message sending/receiving.
• SCHEDULE_EXACT_ALARM: schedule messages precisely.
• READ_SYNC_SETTINGS: Android sync-related behavior.

How We Use Information

• Provide and improve messaging features: compose, send, receive, search, schedule, and manage threads; notifications; dual‑SIM support.
• Reliability and performance: diagnose crashes and measure performance to improve stability.
• Wishes feature: anonymously fetch and display wish templates stored in Firestore.

Google Play Data Safety Mapping

• Data collection:
  • App activity and device/app info may be collected by Firebase Analytics .
  • Crash logs/diagnostics collected by Firebase Crashlytics.
  • Performance data collected by Firebase Performance.
  • Anonymous authentication and content fetches for Wishes via Firebase Auth/Firestore.
• Data sharing: We do not sell data. Limited sharing with service providers (Google Firebase) to operate analytics, crash, performance, and Wishes.
• Data handling:
  • Data is encrypted in transit.
  • You can request deletion of analytics identifiers via Google Play Services settings where supported; Crashlytics/Performance data retention is governed by Firebase policies.
  • Message content remains on your device; you control deletion in the App/OS.

Your Choices and Controls

• Permissions: manage in Android Settings. Some features may not work without certain permissions.
• Messages and attachments: view/delete within the App or using your device's default messaging provider.
• Backups/exports: you decide if/where to create and store them.

Data Retention

• On‑device data: kept until you delete it or uninstall the App.
• Firebase analytics/crash/performance: retained per Google Firebase's retention policies.
• Firestore (Wishes): category and template content we publish; does not include your personal messages.

Security

We apply reasonable technical and organizational measures to protect information. No method of transmission or storage is 100% secure.

Children's Privacy

The App is not directed to children under 13 (or the age required in your jurisdiction). We do not knowingly collect personal data from children. If you believe a child provided personal data, contact us to request deletion.

International Transfers

Firebase may process data on servers outside your country. Google applies its own safeguards as described in its policies.

Third‑Party Services and Libraries

• Google Firebase: Analytics, Crashlytics, Performance, Firestore, Auth
• Klinker android‑smsmms: MMS transport via your carrier's MMSC (uses your mobile data; we do not route your messages through our servers)
• Glide (image loading), Gson (serialization), Room (local database), EventBus, AndroidX/Material, Joda‑Time, Biometric KTX: operate locally in‑app

Each provider's privacy practices are governed by its own policy.

Contact Us

Email: madfoxdeveloper@gmail.com

Changes to This Policy

We may update this Policy from time to time. We will post the new version here with an updated "Last updated" date. Material changes may be communicated within the App or by other reasonable means.