Overview
ReplyBro ("we", "our", "the app") is an automated notification-reply assistant for Android. We are committed to your privacy. This policy explains what data the app accesses, what stays on your device, and what (if anything) leaves it.
1. Data We Access — and Where It Stays
ReplyBro uses Android's Notification Listener Service to read incoming notifications from supported messaging apps — currently WhatsApp, WhatsApp Business, Telegram, Instagram, and Facebook Messenger — so it can send automated replies on your behalf.
- On device only Notification content (sender name, message text from supported apps: WhatsApp, WhatsApp Business, Telegram, Instagram, and Facebook Messenger) — read in memory to match your rules and compose a reply. Never stored beyond the moment the reply is sent, except in the in-app reply log visible to you.
- On device only Reply rules & settings — stored in the local app database (Room/SQLite) and SharedPreferences. Never synced or uploaded.
- On device only Reply log — a history of sent replies stored locally so you can review them. Cleared when you uninstall the app.
- On device only Wallet / diamonds balance — stored locally in DataStore. Not linked to any account or server.
2. Third-Party SDKs That Collect Data
The following third-party services are integrated in the app. Each operates under its own privacy policy.
Firebase Analytics (Google)
We use anonymous, aggregated usage events (e.g. "rule created", "paywall opened")
to understand how the app is used. No message content or personal data is included
in any analytics event. Analytics is tied to a random app-instance ID, not to your
name or Google account.
Firebase Privacy Policy →
Firebase Crashlytics (Google)
Automatically collects crash reports to help us fix bugs. Reports include device
model, OS version, stack trace, and app state at the time of the crash. They do
not include notification content or reply text.
Crashlytics Privacy Policy →
Google AdMob & User Messaging Platform (Google)
Free-tier users may see ads served by AdMob. Google may use device identifiers
(Advertising ID) to serve relevant ads, subject to your device's ad personalisation
settings. The UMP SDK is used to collect consent in applicable regions (GDPR/CCPA).
Google Ads Privacy Policy →
Google Play Billing (Google)
In-app purchases (weekly, monthly, and yearly plans) are processed entirely by
Google Play. We never see or store your payment information.
Google Play Payments Privacy →
Firebase Cloud Messaging (Google)
We may send you push notifications via FCM — for example, to remind you to
claim your daily diamond reward or to announce new features. FCM assigns
your device a registration token. We do not store individual tokens on our
servers; notifications are delivered via topic-based broadcasts. You can
disable notifications at any time in your device's app notification settings.
Firebase Privacy Policy →
3. Permissions Explained
- Notification access (NotificationListenerService) — Required to read incoming notifications from WhatsApp, WhatsApp Business, Telegram, Instagram, and Facebook Messenger, and to send replies via RemoteInput. You grant this explicitly in Android Settings. You can revoke it at any time; the app will stop working but your data is unaffected.
- POST_NOTIFICATIONS — Used to show you status notifications (e.g. "reply sent", "service running", daily diamond reminders, and updates).
- FOREGROUND_SERVICE / FOREGROUND_SERVICE_SPECIAL_USE — Required on Android 14+ to keep the reply service alive in the background. No extra data collection occurs.
- REQUEST_IGNORE_BATTERY_OPTIMIZATIONS — Lets you exempt ReplyBro from battery optimisation so the listener keeps running. You choose whether to grant this; replies still work without it, but may be delayed when the device is idle.
- ACCESS_NOTIFICATION_POLICY — Lets ReplyBro detect whether your phone is in Do-Not-Disturb mode so it can skip replies when you've asked the device to stay silent.
- INTERNET / ACCESS_NETWORK_STATE — Used only by Firebase (analytics, crash reporting, cloud messaging) and AdMob. Not used to upload your messages or rules.
- BILLING — Required for Google Play in-app subscription purchases.
4. Data Retention & Deletion
All personal data (reply log, rules, settings, wallet balance) is stored solely on your device. To delete it completely, uninstall the app. You can also clear the reply log from within the app at any time.
Anonymous analytics and crash data retained by Google/Firebase is subject to their respective retention policies (typically 14 months for Analytics).
5. Sensitive Information We Do Not Collect
ReplyBro does not request, collect, or transmit sensitive personal information such as your real name, phone number, email address, precise location, contacts list, photos, financial details, health data, religious or political opinions, or biometric identifiers. Notification content is processed in memory on your device only and is never uploaded.
6. Disclosure of Personal Information
We do not sell, trade, rent, or otherwise transfer your personal information to outside parties. The only data that leaves your device is the anonymous, aggregated telemetry described in Section 2, sent directly to the respective third-party services (Google/Firebase, AdMob) under their own privacy policies.
7. Interest-Based Advertising
Free-tier users may see ads served by Google AdMob. Google may use your device's Advertising ID to personalise these ads. You can reset your Advertising ID or opt out of interest-based ads at any time:
- Android: Settings → Google → Ads → "Delete advertising ID" / "Opt out of Ads Personalisation".
- Google account-wide: adssettings.google.com
- Industry-wide opt-out: aboutads.info/choices and youradchoices.com
In regions covered by GDPR or CCPA, the Google User Messaging Platform (UMP) consent form is shown on first launch so you can choose between personalised and non-personalised ads.
8. Children's Privacy
ReplyBro is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided personal information through the app, please contact us so we can address it.
9. Changes to This Policy
We may update this policy as the app evolves. The "last updated" date at the top of this page reflects the most recent revision. Continued use of the app after changes constitutes acceptance of the updated policy.
10. Contact Us
Questions about this policy?
Email: ishubhamx0@gmail.com