Privacy Policy
Najat Bangla – Path to Salvation
Developer/Publisher: Rashed Hossain Najafi
Najat Bangla – Path to Salvation does not require a user account. We do not ask users to provide a name, email address, phone number, contacts, photos, private messages, health information, payment information, or banking information. Google AdMob banner advertising is used. Firebase Analytics is enabled only after the required first-run acknowledgement. Firebase Crashlytics is optional. Google UMP may provide advertising privacy choices where required.
1. Scope of this Policy
Najat Bangla – Path to Salvation is an Islamic reference and utility application that includes Qur'an content, duas, ziyarat, sahifa, prayer times, Hijri information, Qibla, tasbih, Islamic events, online audio, bookmarks, favourites, continue-reading, copy/share, Today's Verse, notification features, and related tools.
This Privacy Policy explains how data may be accessed, collected, processed, transmitted, stored, or shared by the app, its integrated SDKs, and third-party services.
2. Data We May Use or Process
| Data type | When | Purpose / destination |
|---|---|---|
| Precise or approximate foreground location | When location-based features are used and permission is available | Prayer times, Qibla, Hijri/calendar information, and location display. Coordinates used for prayer/calendar requests may be sent over HTTPS to the AlAdhan API. A recent usable location may also be stored locally on the device. |
| Approximate location derived from IP address | When AdMob or other network services are used | Google Mobile Ads may process IP address to estimate general location and for advertising, analytics, measurement, security, and fraud prevention. |
| App activity and interactions | When Firebase Analytics or advertising services are active | Screen/session measurement, app interactions, ad interactions, usage analytics, advertising measurement, and product improvement. |
| Device or other identifiers | Where applicable through Google advertising or platform services | Advertising ID, App Set ID, installation identifiers, or similar identifiers may be processed for advertising, analytics, measurement, security, and fraud prevention. |
| Crash logs and diagnostics | When Crashlytics is enabled and during SDK operation | Crash, ANR, non-fatal error, performance, and diagnostic information used to improve reliability. |
| Firebase installation / messaging token | When remote notifications are available and enabled | Push-notification delivery through Firebase Cloud Messaging. |
| Network request metadata | When online audio, GitHub remote configuration, or external web services are used | External providers may receive ordinary network information such as IP address, user-agent, and request metadata. |
| Local app data | During normal app use | Fonts, Adhan/vibration preferences, Hijri adjustment, bookmarks, favourites, continue-reading state, Today's Verse timing, notification preferences, and cached prayer/location data are primarily stored locally. |
3. Location
The app may request ACCESS_FINE_LOCATION and/or ACCESS_COARSE_LOCATION.
These permissions are used in the foreground while the app is in use for prayer times,
Qibla, and location-aware Hijri/calendar functionality.
The app does not request ACCESS_BACKGROUND_LOCATION and does not use geofencing.
Before the first Android location permission request, the app presents an in-app disclosure explaining the location use.
For prayer-time and calendar requests, latitude and longitude may be sent over HTTPS to the AlAdhan API. Qibla bearing is primarily calculated on the device. Android/device geocoding services may also process coordinates to resolve a human-readable location name.
If location permission is denied, non-location features remain available, while location-dependent results may be limited or may use previously cached information where available.
4. Google AdMob, Advertising, and Advertising ID
The app uses Google AdMob banner advertising. The Google Mobile Ads SDK may automatically collect and share certain data for advertising, analytics, measurement, security, and fraud prevention. This may include IP address, app/user product interactions, diagnostic information, Advertising ID, App Set ID, and other device/account identifiers where applicable.
The Android Advertising ID can be reset or deleted using device settings. Firebase Analytics Advertising ID collection and ad-personalization signals are disabled in the app configuration; however, Google AdMob may separately process advertising-related identifiers and data as part of the Mobile Ads service.
Where required by applicable law or Google policy, Google User Messaging Platform (UMP) may display consent or privacy messages. An Ad Privacy Choices entry may appear in Settings when required.
5. Firebase Analytics
Google Firebase Analytics is used for active-user, realtime, session, screen, engagement, and technical usage reporting. Analytics collection remains disabled until the required first-run analytics disclosure is affirmatively acknowledged.
After acknowledgement, Analytics remains enabled as part of the app's required analytics setup and there is no Analytics on/off toggle in the app Settings.
Firebase Analytics may process an app-instance identifier, app lifecycle/session/screen interactions, app version, device/OS technical information, and coarse geographic information derived by Google. The app does not intentionally send a user's name, email address, phone number, search text, custom Analytics user ID, or precise GPS coordinates to Firebase Analytics.
6. Firebase Crashlytics
Firebase Crashlytics is optional. If the user enables it, Crashlytics may process crash reports, non-fatal errors, ANRs, stack traces, relevant application state, installation/session diagnostics, and device metadata. Users can enable or disable Crashlytics from the app Settings.
7. Firebase Cloud Messaging (FCM)
Firebase Cloud Messaging may be used for remote push notifications. When notifications are available and enabled, Firebase may create or process an installation/registration token and necessary technical metadata so a notification can be delivered to a specific app installation.
When notification access is unavailable, the app is configured to avoid unnecessary FCM auto-initialization. Some event and Adhan notifications are scheduled locally on the device.
8. Today's Verse
Today's Verse selects a short Qur'an verse and its Bangla meaning from the bundled local database. Religious database content is not uploaded to a server for this feature.
To avoid immediate repetition and enforce the display interval, the app may store the last-shown time and previous tip identifier locally on the device. The feature is designed to appear no more than once every 12 hours, which means at most twice within a 24-hour period.
Users can enable or disable Today's Verse in Settings. The developer may also enable or disable the feature through a remote feature flag.
9. GitHub Remote Configuration
The app may download a public JSON configuration file hosted on GitHub to control whether advertising and certain features are enabled. As part of this configuration request, the app does not intentionally upload a user's name, phone number, email address, precise location, or religious content to GitHub.
The remote configuration is used in the current app-process memory and may be refreshed periodically in the background while the app process is running. GitHub may process standard network metadata, including IP address, under its own privacy practices.
10. Online Audio and External Web Services
When a user chooses online Qur'an, Dua, or Ziyarat audio, the app may send HTTPS requests to external
audio hosting providers such as mp3.duas.org. Those providers may receive ordinary network metadata.
The app may also open the developer website or Google Play pages when the user selects those actions.
11. Copy and Share
Copy and Share features for Arabic text, meanings, transliterations, Qur'an content, duas, ziyarat, sahifa, and other content operate only after direct user action.
Copy places selected text on the Android clipboard. Share opens the Android share sheet and sends the content to the app or service selected by the user. The app does not control the privacy practices of the selected destination app or service.
12. Local and Offline Data
The bundled religious database, bookmarks, favourites, continue-reading position, fonts, Adhan/vibration preferences, Hijri adjustment, Today's Verse timing, cached prayer/location data, and other settings are primarily stored locally on the device.
Android backup/device transfer is disabled for the app's private app data.
13. Security
The app uses HTTPS/TLS for the identified external services and is configured to block cleartext HTTP traffic. No method of electronic storage or transmission can be guaranteed to be 100% secure. The app is designed to minimize unnecessary collection of personal information.
14. Retention and Deletion
The app does not operate user accounts or an identity-linked central user-profile database. Local app data can be removed by clearing the app's data in Android Settings or by uninstalling the app.
Data processed by Google/Firebase, Google AdMob, GitHub, AlAdhan, online-audio providers, or other third-party services is subject to the applicable provider's retention and deletion practices. Removing local app data does not automatically guarantee deletion of historical records already processed by a third-party provider.
15. Data Sale and Third-Party Sharing
We do not sell or rent user information. Data may nevertheless be processed or transferred to Google/Firebase/AdMob, AlAdhan, GitHub, and online-audio providers for app functionality, analytics, advertising, notification delivery, measurement, security, and fraud prevention as described in this policy.
Google Play's formal definition of “sharing” may differ from ordinary-language use of that word. The Google Play Data Safety declaration should be maintained according to current app behavior and Google Play definitions.
16. Third-Party Services
Google AdMob Google UMP Firebase Analytics Firebase Crashlytics Firebase Cloud Messaging AlAdhan API GitHub Duas.org / Online Audio
Google Privacy Policy: https://policies.google.com/privacy
Google advertising technologies: https://policies.google.com/technologies/ads
Firebase privacy information: https://firebase.google.com/support/privacy
17. User Controls
- Revoke location permission in Android Settings.
- Disable app notifications in Android Settings.
- Enable or disable Firebase Crashlytics in the app Settings.
- Enable or disable Today's Verse in the app Settings.
- Where a UMP privacy entry point is required, open Ad Privacy Choices from Settings.
- Clear app data or uninstall the app to remove locally stored app data.
18. Children and Families
The app does not create user accounts or child profiles and does not intentionally ask children for names, email addresses, phone numbers, contacts, photos, private messages, or health information. The publisher follows the Google Play requirements applicable to the declared target audience.
19. Changes to this Policy
This Privacy Policy will be reviewed when an SDK, permission, API, advertising feature, analytics practice, account system, or other material data practice changes. The “Last updated” date above identifies the current version.
20. Contact
Privacy questions or requests can be sent to:
Email: rashednajafi@yahoo.com
Website: https://islaminbengali.org