Mihrab Privacy Policy

1. Information processed

• Location: precise or approximate device location when permission is granted, or coordinates of a city selected manually.
• Preferences: language, theme, city, madhab, calculation method, time format, notification choices and widget configuration.
• Local worship records: prayer check-ins, qada plans, streaks, tasbih counts, Quran reading progress, favorites and similar app activity.
• Cached content: prayer calculations, Quran and hadith content, market prices and other data cached to improve speed and offline use.
• Purchase records: product and transaction status supplied by Apple App Store or Google Play for optional, consumable support purchases. Mihrab does not receive payment-card details.
• Stability diagnostics: crash stack traces, non-fatal error reports, relevant app state, app version, device model, operating-system information, technical diagnostics and Firebase installation, session and Crashlytics identifiers.

2. Location, qibla and nearby mosques

Location is used to calculate prayer times and qibla, resolve a city name, and find nearby mosques when you request that feature. Mihrab does not use location for advertising or continuous movement tracking. You may select a city instead of granting device-location permission. Depending on the requested feature, precise or approximate coordinates, or coordinates of a manually selected city, may be sent over HTTPS to AlAdhan, BigDataCloud, NOAA geomagnetic services, and OpenStreetMap Overpass services. Choosing directions opens Google Maps, Apple Maps or another installed map application, whose own privacy terms then apply.

3. Notifications and audio

With permission, Mihrab schedules prayer-time, advance reminder, Friday and spiritual-content notifications on the device. Notification choices, including individual prayer toggles and sound selection, are stored locally. Adhan audio is used only for prayer-time notifications configured to use it; advance reminders use the applicable reminder sound. iOS and Android may delay or suppress notifications because of system settings, battery policies or device limits.

Quran audio may continue while the app is in the background and may appear in system media controls. Audio is streamed from the Islamic Network Quran CDN unless already cached by the operating system.

4. Widgets and shared app storage

On iOS, the app and its WidgetKit extension use an Apple App Group to share only the information needed to render Mihrab widgets, such as selected language and theme, prayer times, next-prayer countdown, daily verse, hadith or dua, and tasbih count. This shared container stays on the device and is not a Mihrab cloud account. Removing a widget does not necessarily delete the underlying app preferences; uninstalling the app removes them subject to operating-system behavior.

5. Sharing and generated images

Mihrab can generate share cards for verses, hadiths, duas and prayer times. Nothing is shared automatically. A file leaves the app only after you choose Share and select a recipient or third-party application. The selected recipient's privacy policy applies after the transfer.

6. External content and data providers

• AlAdhan: prayer-time and Hijri-date requests that may include coordinates, calculation method, school and date.
• BigDataCloud: reverse geocoding used to resolve a location into a locality or country.
• NOAA geomagnetic services: magnetic-declination information used to improve compass guidance.
• AlQuran Cloud and Islamic Network CDN: Quran text, translations and audio.
• Hadith API content distributed through jsDelivr/GitHub: hadith-library content.
• OpenStreetMap Overpass: nearby-mosque searches.
• Apple Maps or installed map providers: navigation requested by the user.
• Gold API, Binance, GoldPrice.org, ExchangeRate-API and open.er-api.com: gold, silver and exchange reference data for informational zakat calculations.
• Apple App Store and Google Play: optional in-app support purchases and store transaction processing.
• Google Firebase Crashlytics: crash reporting, non-fatal error reporting and app-stability diagnostics.

Network requests expose normal technical data such as IP address, device network information, requested URL and request time to the relevant provider. Mihrab does not send prayer check-ins, qada records, tasbih history or Quran progress to these content providers.

7. Crash reporting, analytics and tracking

Mihrab uses Google Firebase Crashlytics to detect crashes, record selected non-fatal technical errors and improve app stability. Crashlytics may automatically process stack traces, relevant application state, app version, device manufacturer and model, operating-system version, memory or storage diagnostics, timestamps, network connection type, Firebase installation ID, Firebase session ID and Crashlytics installation UUID. Developer-defined error reports include a technical error context but are not intentionally populated with names, email addresses, worship records, precise location or user-entered religious content. Firebase Sessions may record technical session information such as when the app is brought to the foreground so crash-free and reliability metrics can be calculated.

Google processes Crashlytics data as a service provider on behalf of Vibe Coding Studios. The current Mihrab release contains no advertising network, no Firebase Analytics, no cross-app tracking SDK and no sale of personal information. Mihrab does not create behavioral advertising profiles. If Mihrab later introduces advertising, account-based cloud services or additional analytics, this policy and store disclosures will be updated before release.

8. Storage, security and retention

Local records are stored in the app's protected storage and iOS App Group container where widgets require access. Network requests use HTTPS. Local data remains until you clear it, reset the relevant feature or uninstall the app, subject to device backup and operating-system behavior. Cached remote content may be replaced when refreshed. Mihrab currently has no server-side user account or account-deletion database. Google states that Firebase Crashlytics keeps crash stack traces and associated identifiers for 90 days before beginning removal from live and backup systems. External providers may retain technical request logs under their own published policies.

9. Your choices and rights

• Use a manually selected city instead of device location.
• Change or revoke location and notification permissions in system settings.
• Enable or disable prayer and spiritual reminders inside Mihrab.
• Remove local records by using available reset controls, clearing app data or uninstalling the app.
• Contact us to ask privacy questions or report an incorrect disclosure.

Because Mihrab does not maintain user accounts or a server-side worship-history database, we normally cannot identify or delete device-local data remotely.

10. Children

Mihrab is a general religious utility and is not directed at collecting personal information from children. It does not require an account for core use. Parents and guardians should manage device permissions, purchases and sharing controls where appropriate.

11. International processing and changes

External providers may process network requests in countries outside your own under their respective policies. We may update this policy when features, providers or legal requirements change. The effective date above identifies the current version.

Türkçe özet

Mihrab Android ve iOS'ta reklamsız, kullanıcı hesabı gerektirmeyen ve temel ibadet verilerini cihazda tutan bir uygulamadır. Yaklaşık veya tam konum; namaz vakti, kıble, şehir çözümleme ve isteğe bağlı yakındaki camiler için kullanılır. İzin verilmiş cihaz koordinatları veya manuel seçilen şehrin koordinatları, ilgili özellik çalışırken AlAdhan, BigDataCloud, NOAA ve OpenStreetMap Overpass servislerine HTTPS üzerinden gönderilebilir. Bildirimler cihazda planlanır. iOS widget'ları dil, tema, vakitler, günlük içerik ve tesbih sayacı gibi gerekli verileri Apple App Group üzerinden yalnızca cihaz içinde paylaşır. Mihrab, uygulama çökmelerini ve teknik hataları incelemek için Firebase Crashlytics kullanır; kilitlenme günlükleri, teşhis bilgileri, teknik oturum bilgileri ve Firebase/Crashlytics kurulum kimlikleri Google tarafından Mihrab adına işlenebilir. İsteğe bağlı destek satın alımlarında mağaza işlem durumu işlenir ancak Mihrab ödeme kartı bilgilerini almaz. Mihrab reklam, Firebase Analytics veya uygulamalar arası takip kullanmaz; ibadet geçmişini bu sağlayıcılara göndermez. Paylaşım görselleri yalnız kullanıcı paylaşmayı seçtiğinde cihaz dışına çıkar. Sorularınız için vibecodingstudios@gmail.com adresine yazabilirsiniz.