Short version: Muffle stores almost everything exclusively on your own device. We do not run servers, we do not sell your data, and we do not collect personal information for our own purposes. The only data that ever leaves your device goes to Google services you choose to interact with (AdMob ads, Google Play billing, and the Android Geofencing API), as described below.
This Privacy Policy explains how DevByyte ("we", "us", "our") handles information in connection with the Muffle mobile application ("App") on Android. By installing or using the App you agree to the practices described here. If you do not agree, please uninstall the App.
1. Who We Are
Muffle is an independent ("indie") Android application developed and maintained by a sole developer operating under the name DevByyte. Contact: haseebthedev0@gmail.com.
We are not a company incorporated in any particular jurisdiction. We operate globally through the Google Play Store. For EU/EEA users, we act as the data controller for any personal data processed as described in this policy.
2. What Data Muffle Accesses — and Where It Goes
The table below covers every category of sensitive data the App can access. Read the "Leaves your device?" column carefully.
2.1 GPS / Precise Location
Why: To trigger location-based routines (geofences) and to auto-calculate Islamic prayer times based on your coordinates.
When: Only when you create a location-based routine or enable "Auto Prayer Times". Background location access is used only to fire geofence triggers while the App is not open.
Stored: Latitude and longitude of geofence centres are stored locally on your device inside the App's private storage (Hive database and SharedPreferences). They are never uploaded to our servers (we have none).
Leaves your device? Yes — in two limited ways: (a) the Android OS Geofencing API (operated by Google) receives geofence coordinates to monitor them; (b) prayer time calculation is performed fully on-device using the open-source Adhan library — no location data is sent to any server for this purpose.
2.2 Contacts
Why: The "Emergency Bypass Contacts" feature lets you nominate contacts whose calls will always ring through even when a silent routine is active.
When: Only when you explicitly tap to add a contact.
Stored: Only the phone number (not the name) is stored locally in the App's private SharedPreferences storage.
Leaves your device? No. Contact data never leaves your device.
2.3 Phone State and Call Log
Why: To detect when a bypass contact is calling (so the routine can pause temporarily) and to send auto-SMS replies on missed calls.
When: The App listens for incoming and missed calls only while a routine is active.
Stored: No call history is stored by the App. The App reads the incoming caller ID in real time and immediately discards it after checking against your bypass contacts list.
Leaves your device? No. Call data never leaves your device.
2.4 Calendar
Why: The calendar trigger feature reads your upcoming calendar events to schedule routines around them (e.g. silence during a meeting).
When: Only when you create or edit a calendar-based routine. The App reads events for the next 7 days to schedule alarms.
Stored: Event IDs, calendar IDs, and start/end times are stored locally in the App's private Hive database to schedule alarms. Event titles or content are never stored.
Leaves your device? No. Calendar data never leaves your device.
2.5 SMS
Why: The "Auto SMS Reply" feature sends a message you compose to callers who are missed while a silent routine is active.
When: Only when you have configured an auto-reply message and a call is missed during an active routine.
Stored: The message text you write is stored locally in the App's private SharedPreferences. The App sends the SMS using Android's built-in SmsManager on your behalf — it passes through your mobile carrier's network as any normal SMS would.
Leaves your device? The SMS message content is sent via your carrier as a standard SMS to the caller. It is not transmitted to us or any third party.
2.6 Activity Log (Routine History)
Why: The App maintains a local log of when your routines activated and deactivated so you can review them in the Activity Log screen.
Stored: Routine name, trigger type, action taken, and timestamps — all stored locally in the App's private Hive database on your device.
Leaves your device? No.
2.7 Advertising (AdMob) — Free Tier Only
Why: The free tier of the App shows advertisements served by Google AdMob to support development.
Consent first: Before any advertisement loads, users in the EU, EEA, and UK are shown an explicit consent dialog (powered by Google's User Messaging Platform SDK) asking for permission to use their data for personalised advertising. Ads are only personalised if you actively consent. You can withdraw or change your consent at any time via the Privacy Settings option in the App.
What AdMob collects: AdMob may collect your device's advertising ID, IP address, general location, and information about ads shown and interacted with. This is governed entirely by Google's own privacy policy.
Leaves your device? Yes — AdMob data is transmitted to Google's servers. We receive only aggregate, anonymised revenue reports. We do not receive any individually identifiable data from AdMob.
Premium users: No advertisements are displayed to premium users.
Why: Premium upgrades are processed through Google Play's billing system.
What we receive: We receive only a confirmation that a purchase was made (a purchase token). We do not receive your payment card details, billing address, or Google account information.
We do not collect, store, or transmit: your name, email address, account credentials, the content of your calendar events, the content of your SMS messages, your browsing history, your precise location history, or any analytics about how you use the App. We have no backend servers and no user accounts.
3. Religious Data (Special Category)
If you use the Islamic Prayer Times trigger, the App uses your location to calculate prayer times locally on your device. Your use of this feature may implicitly indicate your religion. This information is processed solely on-device, is never transmitted to us or any third party, and is never used for any purpose other than calculating prayer times for your routines.
Under GDPR Article 9 and equivalent laws, religious data is "special category" data. We handle it with extra care: it never leaves your device.
4. Legal Bases for Processing (GDPR — EU/EEA Users)
If you are located in the European Union or European Economic Area, our legal bases for processing personal data are:
Contractual necessity (Art. 6(1)(b)): Location data (geofencing), contact numbers (bypass feature), phone state (bypass/auto-SMS), calendar data, and SMS — processed to deliver the core features of the App you have chosen to use.
Legitimate interests (Art. 6(1)(f)): Activity logs processed locally to provide you with a history of your routines.
Consent (Art. 6(1)(a)): Advertising (AdMob) — before any ad loads, free-tier users in the EU/EEA/UK are shown an explicit consent dialog through which they actively grant or deny permission for personalised advertising. Consent can be withdrawn at any time via the Privacy Settings option in the App.
5. Data Storage and Security
All App data (routines, settings, activity logs, bypass contacts, SMS templates) is stored exclusively in the App's private, sandboxed storage on your device. Other apps cannot access this data.
We do not operate any servers or cloud storage.
Data is protected by Android's built-in application sandboxing and your device's screen lock / encryption.
We recommend keeping your device OS and the App up to date to benefit from the latest Android security patches.
6. Data Retention
All data persists on your device until you delete it (by deleting a routine, clearing the activity log) or uninstall the App.
Uninstalling the App removes all locally stored data. We have no copy of it.
To delete bypass contacts or SMS templates, use the Settings screen inside the App.
7. Children's Privacy
The App is not directed at children under 13 years of age. We do not knowingly collect personal data from children. If you believe a child has provided information through the App, please contact us at haseebthedev0@gmail.com and we will take appropriate steps.
For EU users: we do not knowingly process data of children under 16 without verifiable parental consent, in accordance with GDPR Article 8.
8. Your Rights
Depending on your location, you may have the following rights:
Access: You can view all your data inside the App at any time (routines, settings, activity log).
Deletion: You can delete individual routines, clear the activity log, and remove bypass contacts from within the App. Uninstalling the App deletes all data.
Portability: Because we hold no server-side data, there is nothing to export from our end.
Opt-out of advertising: Upgrade to premium to remove all ads and prevent AdMob from running.
Opt-out of location: Revoke location permission from Android Settings → Apps → Muffle → Permissions at any time. Location-based and prayer-time features will stop working.
California residents (CCPA/CPRA): We do not sell personal information. We do not share personal information for cross-context behavioural advertising (AdMob serves ads; the data goes to Google, not to us). You may contact us to request disclosure of any information we hold about you — which, given our architecture, will be none.
EU/EEA residents (GDPR): You have the rights of access, rectification, erasure, restriction, and objection under GDPR. Since we hold no server-side data, exercising most of these rights means acting within the App or uninstalling it. You also have the right to lodge a complaint with your local data protection authority.
9. Third-Party Services
The App integrates the following third-party services. Each has its own privacy policy:
Android OS Geofencing API (part of Google Play Services)
Adhan prayer time library — open source, runs fully on-device, no network calls
10. International Data Transfers
Because almost all data is stored on-device, there are no international data transfers by us. Google AdMob and Google Play Services may transfer data internationally in accordance with Google's own data transfer mechanisms (Standard Contractual Clauses for EU users). Refer to Google's privacy policy for details.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. We encourage you to review this page periodically. Continued use of the App after a change constitutes acceptance of the updated policy.
For material changes, we will make reasonable efforts to notify users (e.g. via a notice in the App on next launch).
12. Contact
If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please contact: