Privacy Policy
Last updated: April 30, 2026
This Privacy Policy explains how Umrah & Hajj Companion handles information when you use the mobile application on iOS and Android. The app is developed by Lumina Dev.
1. Information We Handle
- The app is designed to be offline-first. Most information you create is stored on your device.
- On-device information may include ritual progress, Tawaf and Sa’i counter sessions, saved du’a, checklist items, saved map pins, emergency contacts, group safety details, language, text size, theme, offline pack status, purchase status, and support light history.
- If you use map, Qibla, or “my location” features, the app may request location permission to calculate direction, show your position, save pins, or help you orient yourself.
- If you use support history QR transfer features, the app may request camera access to scan QR codes.
- If you make an in-app purchase, app stores and purchase services may process transaction information. The app may store purchase status and anonymous supporter identifiers to restore or verify purchases.
- Advertising delivery information may be handled through Google AdMob where ads are shown.
- On Android, Firebase Analytics may collect app interaction and device information such as app opens, sessions, device model, operating system, approximate geography, app updates, and in-app purchase events.
- On Android, Firebase Crashlytics may collect crash reports, stack traces, relevant app state, device metadata, Firebase installation identifiers, and Crashlytics installation identifiers to help diagnose crashes and stability issues.
2. How We Use Information
- To provide ritual guidance, offline content, counters, du’a, checklists, maps, Qibla, emergency organization, and other app features.
- To save your preferences and progress locally on your device.
- To show maps, saved places, offline map packs, and location-based orientation when you grant permission.
- To support in-app purchases, ad removal, support light history, and optional transfer of support history between devices.
- To display advertising only in allowed, low-stakes placements.
- To understand broad feature usage, app health, and stability, and to diagnose crashes or errors through Firebase Analytics and Firebase Crashlytics on Android.
3. Local Storage
The app uses local device storage, including Isar, SharedPreferences, secure storage, and files for offline packs. Local data remains on your device unless you share it, transfer it, use an optional configured backend feature, clear app data, or uninstall the app.
4. Third-Party Services
- The app may use Google AdMob for ads, Firebase Analytics for usage analytics, Firebase Crashlytics for crash reporting, Mapbox for maps and offline map resources, app store purchase systems for in-app purchases, and optional backend services such as REST APIs or Supabase for support purchase verification and transfer features when configured.
- These services may process data under their own privacy policies.
5. Location, Camera, and Sharing
Location access is optional and can be changed in your device settings. Camera access is used for QR scanning only when you choose to scan. Native share actions may send meeting point, saved pin, hotel, bus, camp, guide, or similar details to the app or person you select.
6. Advertising
Ads may appear on Home and Map, which are non-sacred, non-active ritual surfaces. The app is designed not to show ads during active Tawaf or Sa’i counting sessions or interrupt ritual flows.
7. Analytics and Crash Reporting
Firebase Analytics and Firebase Crashlytics are used on Android to understand general app usage and improve reliability. We do not use these tools to intentionally collect your ritual notes, emergency contact details, saved places, medical notes, or free-form personal content. Firebase data is processed by Google under Google and Firebase privacy terms and retention practices.
8. Children
The app is not designed specifically for children. If you believe information was provided inappropriately, contact us.
9. Retention and Deletion
Locally stored data remains until you delete it in the app, remove offline packs, clear app data, or uninstall the app. Purchase records may also be retained by app stores or optional backend services according to their policies.
10. Changes
We may update this Privacy Policy from time to time. The latest version will be posted on this page with an updated date.
11. Contact
For privacy questions, contact machealmaxin83@gmail.com.