Privacy Policy

1. Introduction

Welcome to the Privacy Policy for Misbaha: Digital Tasbih (the "Application"), developed and published by MK Dev Studio ("we", "us", or "our"). This policy explains how we treat your data when you use the Application, outlining our commitment to user privacy, local data storage, and the details regarding the minimal third-party integrations required to support and run our app.

2. Information We Do NOT Collect

The Application is designed to operate without accessing, retrieving, or harvesting your personal information. Specifically:

• No Account Registration: You do not need to sign up, log in, or create a profile to use the app. There is no password or authentication system.
• No Personal Identifiers: We do not collect or request names, email addresses, phone numbers, or any demographic details.
• No Location Access: The Application does not track your location. Location services and geofencing APIs are not accessed or requested.
• No Hardware Access: The app does not access your device's camera, microphone, photo libraries, or media folders.
• No Contacts Access: We do not access your contacts list or phone book.
• No Financial or Health Data: We do not request or collect any credit card details, payment data, financial records, or personal health metrics.
• No Notification Alerts: The Application does not use or configure local or push notifications.
• No Backend Server or API Calls: We do not run a custom server. The application code is completely self-contained and makes no network requests or API calls to any remote server or database host.

3. Information Stored Locally

To provide a smooth utility experience, the Application saves your zikr configurations and progress details directly on your device. This data is written to your device's sandboxed local storage, remains isolated from other apps, and is never transmitted to us or any third party. The items stored locally are:

• Counters & Progress: Your active count sessions, total completed rounds, target counts, daily streaks, and the history log of your prayer counts over time (used to compile the visual charts shown inside the app).
• Selected & Custom Prayers: The identifier of your active prayer, along with any custom zikr entries you create.
• App Preferences: Your customized theme settings (light, dark, or system selection), app display language, options to render texts in Arabic, text scaling sizes, audio toggles, sound variant selections for counting and completion alerts, haptic vibration feedback toggles, and playback rates for vocal files.
• Ad Settings: The status indicating whether you have watched rewarded video ads to unlock unlimited custom zikr slots.
• Time Logs: The timestamp of your last active session, used locally to track your daily streak calculations.

4. Backup & Restore

The Application includes export and import tools so you can safeguard and transfer your data. These features require your manual initiation and direct participation:

• Data Export: When you choose to export, the app packages your local preferences and counts into a temporary data file on your device. You can then save this file locally or share it using your device's standard share sheet.
• Data Import: When you choose to import, the app prompts you to select a previously saved data file from your storage folder. Once selected, the app updates your local progress on-device.

The Application does not perform automated cloud syncs, background backups, or remote file transmissions. You are in full control of when and where your backups are saved.

5. Advertisements (Google AdMob & Advertising ID)

To support the development and maintenance of the Application, we display advertisements served through the Google Mobile Ads (AdMob) SDK. Ads appear in the following formats:

• Banner Ads: Small banner advertisements displayed at the bottom of various screens.
• Interstitial Ads: Full-screen advertisements shown occasionally when transitioning between count sessions (configured with a 5-minute safety cooldown timer).
• Rewarded Video Ads: Optional advertisements that you can watch to unlock unlimited custom zikr slots.

Data Shared with Google AdMob

To request and render ads, the Google Mobile Ads SDK requires access to the internet and checks network availability. In doing so, the SDK automatically accesses your device's Android Advertising ID, device hardware model, IP address, and ad interaction metrics. This information is sent directly to Google's servers to serve relevant ads, monitor ad performance, and prevent fraud. This process is governed by Google's Privacy Policies.

Google Play Services components facilitate ad delivery, secure SDK operations, and verify device compatibility.

6. App Analytics & Crash Diagnostics (Firebase)

To ensure application stability, diagnose technical errors, and understand overall app performance, the Application integrates Google Firebase services.

Firebase Analytics

We use Firebase Analytics to understand user engagement and app usage trends in an aggregated, non-personally identifiable manner. Firebase Analytics collects app interaction data, feature usage events, device model information, system version details, and anonymized device identifiers (including the Android Advertising ID). This information helps us optimize app features, design improvements, and performance without linking activities to individual personal identities.

Firebase Crashlytics

We use Firebase Crashlytics to monitor, diagnose, and resolve application crashes and stability issues. When an unexpected crash or system error occurs, Firebase Crashlytics automatically collects diagnostic information including crash stack traces, device hardware state at the moment of the crash, operating system version, and unique installation diagnostics. Crash logs do not contain your personal zikr records or personal identifying data and are strictly used to fix bugs and improve reliability.

7. Google Fonts

The Application uses the Google Fonts library to display clean and readable typography. Rather than bundling large font files directly inside the app, the app downloads them from Google Fonts servers when needed and caches them locally on your device.

During this download process, the app makes a network connection to Google's font servers. Consequently, Google's servers receive standard web request information, such as your IP address and device hardware details, in order to deliver the requested font assets.

8. Third Party Services

The third-party services integrated into the Application that may process diagnostic, advertising, or layout data over the internet are:

1. Google Mobile Ads (AdMob): Connects to Google servers to load advertising media and processes Advertising IDs, hardware models, IP addresses, and ad interaction metrics.
2. Firebase Analytics (Google LLC): Processes anonymized app interaction events, feature usage analytics, and device identifiers to provide aggregated usage insights.
3. Firebase Crashlytics (Google LLC): Collects crash stack traces, diagnostic logs, and device environment state during application errors to help diagnose bugs.
4. Google Play Services (Google LLC): Provides essential background infrastructure, security APIs, and core platform capabilities supporting Google SDK integrations.
5. Google Fonts SDK: Establishes temporary connections to Google Fonts repositories to download text font styles.

We do not share your prayer logs, counters, custom zikrs, or settings with these or any other third parties. We recommend reading Google's Privacy Policies to learn more about how Google handles data collected through its SDKs:

Google Privacy & Terms Policy | Firebase Privacy & Security Documentation

9. Data Security

Because your counts and settings are stored locally on your device, their security depends on the physical security of your phone and the security configurations of your operating system. All network transmissions conducted by integrated Google SDKs (such as AdMob, Firebase Analytics, and Firebase Crashlytics) are encrypted in transit using industry-standard HTTPS protocol.

Please note that exported backup files are saved in an unencrypted format. We recommend storing your exported files in a secure location to protect your data privacy.

10. Children's Privacy

Our Application does not collect or request personal information, and we do not knowingly process personal data from children. However, integrated third-party SDKs (including Google AdMob and Firebase services) may collect anonymized device identifiers, analytics events, and diagnostic logs in accordance with Google's child safety advertising policies and Google Play Families guidelines.

11. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with the revised "Last Updated" date at the top. We encourage you to review this policy periodically to stay informed about how we protect your privacy.

12. Contact Us

If you have any questions, suggestions, or feedback regarding our privacy policy or practices, please get in touch with us:

Developer: MK Dev Studio
Support Email: mohin.malek1999@gmail.com