Hidayah Privacy Policy
App: Hidayah (package com.aistudio.deencompanion.quranj) · Effective date: 13 October 2026
1. Scope, construction and application of this notice
This Privacy Policy constitutes the disclosure of information-processing practices applicable to Hidayah, a Quran, prayer-times and Islamic learning application maintained by Muhammad Garana. References herein to the “Application” encompass its installed Android software, locally bundled resources and those network-dependent functions described below; references to “we”, “us” and “our” identify the application's developer. References to “you” identify the individual using the Application, irrespective of whether an anonymous community identity has been established.
The Application operates substantially through device-resident resources, but its offline-oriented architecture does not imply an absence of information collection. Analytics, crash reporting and performance monitoring commence automatically when the Application is used, without a separate in-app permission prompt. Community functions, nearby-masjid discovery, requested downloads and speech recognition involve additional processing according to the function invoked. The Application displays no advertisements and we do not sell your data.
This notice distinguishes information retained within the Application's device storage, information transmitted to our Firebase-backed community services, information processed by Google measurement and diagnostic services, and information received by independent providers to which your device connects. These categories may coexist during a single session. A statement that a particular item is excluded from our custom analytics does not mean that the same item is never processed for an expressly described functional purpose.
This document describes processing practices; it does not, merely by being displayed or by your continued use, establish consent for every processing operation or displace rights available under applicable law. Android permission decisions, application functionality and third-party service terms must be considered in conjunction with the particular processing activity to which they relate.
2. Categories of information and processing terminology
For the purposes of this notice, “local information” means information retained in application preferences, databases, files or caches on your device. “Usage information” means structured events concerning screens, controls, settings and feature outcomes. “Diagnostic information” means crash, responsiveness and performance measurements. “Community information” means contributions, votes, moderation reports, participation records and associated technical records maintained for shared features.
An app-instance identifier, installation identifier or anonymous authentication identifier is a technical reference that can distinguish an installation or account without requiring a name, email address or telephone number. Such an identifier should not be understood as a guarantee that the associated information is irreversibly anonymous. In particular, community authentication identifies a pseudonymous account for service operation, whereas Analytics and Crashlytics use their own measurement or installation references.
Information can arise from a choice you make, an operation requested by you, an automatically generated event, a network connection or a service's technical processing. The absence of a registration form does not preclude these categories of collection. Likewise, a permission being optional means that you can withhold it, although the feature dependent upon that permission may then be unavailable or require a manual alternative.
3. Automatic usage analytics and collection configuration
Google Analytics for Firebase receives structured information concerning application usage. Collection is enabled automatically in the current Application configuration and the Application does not expose an Analytics collection switch. Settings & Privacy provides a disclosure of this processing. Denying location, microphone or notification permission does not, by itself, disable the separate Analytics collection mechanism.
Usage events encompass screen views and screen-open durations, interaction identifiers, search usage without the entered query, scroll milestones, audio actions and playback states, download outcomes and duration measurements, permission outcomes, setting changes, and network status and latency measurements. Instrumentation describes supported event sites rather than representing a comprehensive recording of every gesture, every screen element or every network client.
Firebase also processes an app-instance identifier and standard application and device information. Google may derive approximate geographic information from network connections. Consequently, these measurement operations are not described as zero-data collection. Our custom event exclusions, set out below, concern the payloads configured by the Application and should be read separately from the standard technical metadata processed by the relevant SDK.
The operational purposes of these measurements are to understand feature use, identify unsuccessful interactions and downloads, assess navigation and reader behavior, and determine where application reliability or performance requires improvement. Events concerning religious learning or prayer-related features can indicate which features a person uses, even though the underlying private entries and excluded values are not transmitted in our custom events.
4. Content identifiers, setting properties and feature outcomes
When built-in content is opened or played, the Application may report its fixed catalog identifier. Examples include the surah or para number, Quran edition, book collection, naat reciter, azan recording and dua category. Books obtained through the open World Library are identified in custom measurement only as “World Library”, rather than through their individual titles or download addresses.
Configuration information includes the selected app language, prayer calculation method, Asr method, high-latitude rule, Hijri calendar, madhhab and Quran reader mode. Properties also describe whether prayer alerts or an azan alert are enabled, whether the home-screen widget is present, whether exact alarms are available, and whether location is supplied through GPS or a manually selected city. The location-source property identifies a mode; it does not contain the actual city or coordinates.
Selected configuration values are retained as Analytics user properties so that usage reports can be grouped according to those settings. The properties use predefined options rather than arbitrary text entered by a user. A property describing madhhab or prayer preferences may nevertheless convey information about religious practice, and its exclusion of direct contact information does not remove that implication.
Feature milestones can identify completion of a Quran khatm, Hifz Coach session, tasbeeh round, dhikr, quiz round or zakat calculation, or that a masjid timing, vote or City Challenge join was saved. These milestone events omit the private counts, financial amounts, prayer statuses and other excluded details. A reading-session event describes reader-open duration and page-turn quantity, rather than the identity of individual pages.
Prayer-alert measurements identify delivery, opening or stopping of an alert for a named prayer. Widget events describe adding, removing or opening the home-screen widget. Launch-source events distinguish opening from the launcher, a prayer notification or the widget. These events describe use of the delivery mechanism rather than uploading the local prayer timetable or city.
5. Custom-event exclusions and advertising configuration
Our custom Analytics events do not contain names, email addresses, telephone numbers, your city, precise GPS coordinates, masjid names, search text, URLs, recordings, notes or authentication identifiers. They also exclude which prayers you marked and their status, tasbeeh and dhikr counts, the Salah guide's man/woman choice, Muslimah-mode values, financial amounts and whether zakat is due.
Interaction events use fixed control identifiers, and permitted catalog and setting values are constrained by the Application's event schema. Search measurement concerns use of search rather than transmission of the words searched. Tracking a control or recording a completion milestone must therefore be distinguished from copying the underlying private record into a measurement event.
Advertising ID collection and advertising personalization are disabled. We do not attach your Firebase community account identifier to Analytics events or link Analytics to that community account. These configuration choices do not eliminate Google's processing of the standard app-instance, device and diagnostic metadata described elsewhere in this notice.
6. Crash reports, responsiveness and performance measurements
Firebase Crashlytics processes reports of crashes and application-not-responding conditions. Such reports include stack traces, application version, device model, Android version, available memory and storage, a Crashlytics installation identifier, and a breadcrumb trail containing recent screen names and the structured interaction identifiers described above. These records help identify the affected code path and circumstances surrounding a failure.
Firebase Performance Monitoring processes application-start measurements, screen-rendering information including slow and frozen frames, and the Application's content-download duration trace. Associated information includes device and application metadata and approximate country information. The current instrumentation does not use the Performance Gradle plugin for automatic network tracing; the expressly configured download measurement should not be construed as a recording of all network requests.
The Application does not intentionally include your private content, precise location or search text in these diagnostic payloads. Crash and performance processing remains distinct from the records held for functional community operations. Additional provider-level details, retention practices and security information are described in Firebase's privacy and security documentation; Google Analytics is also subject to its separate service terms and Google's privacy policy.
7. Local prayer calculations, Qibla and location permission
Prayer times, Qibla and the Ramzan timetable are calculated on your device using the location available to the Application. The calculation operation itself does not transmit its input coordinates to us. Location permission is optional, and manual city selection is available for supported location-dependent functions. Permission can be reviewed or revoked through Android settings.
This local-calculation statement is limited to the calculation operation. Invoking nearby-masjid discovery or a community contribution produces the additional processing described in the following section. It would therefore be inaccurate to infer that coordinates always remain on the phone merely because prayer-time calculations are device-local.
Actual coordinate precision depends on the information supplied by Android or the manually selected location. A coordinate used for a search can be precise when precise device location has been granted. Approximate country information derived by Google for diagnostics is a separate category and is not a substitute description for the coordinates transmitted in nearby search.
8. Nearby-masjid discovery, search accounting and presence checks
In the current implementation, configured nearby-masjid discovery uses Google Places. The Application submits the latitude and longitude of the search center and a search radius to Google to request nearby mosques. Google receives the corresponding network request and processes it according to its applicable service terms and privacy practices. Availability depends on the build's configuration and the applicable search limits.
Before a Google search, the Application reserves a search allowance in Firebase. A search-quota record associated with the anonymous community account stores a day value, attempt count, last-search timestamp, and latitude and longitude for search-limit and movement checks. Search accounting is also retained in local preferences. A failed or timed-out Google request can still consume an allowance because reservation precedes the request.
Google search results are retained in process memory rather than written to the Application's local community-results database. Community-provided masjid entries and search-area information can be cached locally to support subsequent discovery. The last-search coordinates stored for quota enforcement are a separate record from Google's result content and from the custom Analytics payload.
Community contributions may include a masjid's name, address and map coordinates. Timing and voting operations also use presence information, including distance from the masjid and reported location accuracy, to support the requirement that contributions be made from within 200 metres. Distance and accuracy fields can be stored with contribution or vote records. They are not equivalent to an assurance that no location-related information is retained.
The Application's local prayer calculations, Google search coordinates, Firebase quota coordinates, public masjid coordinates and stored presence measurements have different purposes and destinations. The exclusions applying to Analytics do not prohibit these location-related records from being processed for the functional services expressly described here.
9. Microphone access and Hifz Coach recognition
Hifz Coach invokes your device's speech-recognition service, commonly provided by Google, to assist with checking recitation when you activate the microphone control. The Application does not itself record, store or upload your recitation audio. Recognition is performed by the selected device speech service under that provider's own privacy terms and device configuration.
Whether recognition is processed entirely on the device or involves the provider's servers depends on the recognizer available on your device. Our statement about not uploading recordings concerns the Application's own handling and is not a representation that the independent speech service never transmits audio. You may withhold or revoke microphone permission; functions requiring recognition will then be limited.
10. Anonymous community identity and shared records
Community Masjid and City Challenge use Firebase Anonymous Authentication to establish an account reference without collecting a name, email address or telephone number through registration. Establishment of that reference may occur as part of a supported feature without displaying a conventional login screen. Google processes the technical information needed to operate authentication.
Google Cloud Firestore stores community masjids and timings you submit, votes, timing histories, content reports, participation information and service-operation records such as search quotas and contribution-rate information. Records can contain anonymous account references and timestamps so that the service can associate writes, maintain versions, restrict repeated actions and apply access rules.
Other users can see shared community contributions and the outcomes presented by the Application. Your anonymous account identifier is not displayed to them as a profile identity. Moderation reports are submitted for review rather than offered as a public user profile. Information entered into publicly visible contribution fields should be limited to the intended masjid and timing information.
Firebase App Check uses Google Play Integrity to help verify that requests originate from the intended application environment. Attestation and related technical verification are separate from the substantive masjid contribution. These checks support abuse prevention and do not require a named community profile.
11. Requested downloads and independent content hosts
Some Quran data, recordings, PDFs, books and rate information are obtained through direct connections from your device to third-party hosts. A host can receive your IP address and the technical request information necessary to return the requested resource. This remains the case where the downloaded file is subsequently retained and read offline.
- GitHub, including github.com and raw.githubusercontent.com, supplies Quran PDFs, word-by-word audio, hadith PDFs and naats.
- Quran.com, QuranCDN, EveryAyah, QuranicAudio and AlQuran Cloud supply Quran data and recitation resources.
- Dawat-e-Islami, Internet Archive, Google Drive and Emaan Library host books and hadith PDFs.
- jsDelivr CDN and currency-api.pages.dev supply currency and metal-rate resources used by the Zakat calculator.
Provider processing is governed by the destination service's own practices. Our omission of resource URLs from custom Analytics events does not prevent the resource host from receiving the address requested by your device. Opening an external link or another application similarly places the subsequent interaction within the receiving service's environment.
12. Device storage, backup and restored installations
Settings, bookmarks, reading progress, prayer tracking and downloaded resources are maintained locally for their respective functions. Local storage permits preferences and progress to persist across sessions and supports offline access to content already available on the device. Such storage is distinct from the measurement events and community records described above.
The Application enables Android backup and device-transfer support for included preferences and databases, subject to Android settings and platform behavior. Its backup rules exclude installation-onboarding state, legacy Analytics consent preferences and the local community search-budget preferences. The rules do not represent a promise that all downloaded files are copied into backup.
Uninstalling normally removes application-private local storage. It does not automatically erase an existing Android backup, an exported file stored outside the Application's private directory, or records already received by Google or a community backend. A restored installation can recover eligible preferences and databases according to the operating system's backup or transfer mechanism.
13. Notifications, alarms and home-screen widget
Prayer alerts are scheduled on the device using the timetable calculated for your selected location and settings. Notification permission and exact-alarm availability determine which delivery functions Android allows. Withholding such access can affect timely delivery, without constituting a change to the separate configuration of Analytics collection.
The local timetable and city are not uploaded through the prayer-alert Analytics events. Measurements nevertheless record the alert's named prayer and whether delivery, opening or stopping occurred, as described above. Widget presence and opening can likewise generate the corresponding usage events even though the widget's prayer calculations use local information.
14. Retention and separation of deletion mechanisms
Local records generally persist until removed through an available feature, cleared through Android application settings or removed with the installation, subject to backup and externally stored-file qualifications. Community records persist within the backend until removed or changed through the applicable service or administrative process. This notice does not specify an unverified automatic expiry period for every community record.
Google measurement and diagnostic information is subject to the applicable service configuration and provider retention practices. Uninstalling stops further collection by that installation but does not retroactively remove events already transmitted. Deleting an anonymous community account does not itself identify or delete separate Analytics or Crashlytics installation records.
Deletion may involve different records and different technical systems; removal from an active account should not be treated as immediate removal from every provider backup or retained diagnostic system. Provider-specific handling is described in the linked Firebase documentation. Requests concerning information already transmitted should identify the relevant feature and type of record rather than assume all information shares one identifier.
15. Community account deletion and privacy requests
Within Community Masjid, the menu item “Delete my community data” invokes deletion of the current anonymous Firebase authentication account and signs that account out. In the current implementation, this action does not automatically purge all previously written Firestore documents. Votes, timings, masjid contributions, histories, moderation reports and search-quota records may remain in the backend, including stored references to the former account identifier.
Deletion of the authentication identity means the former identifier no longer maps to that active authentication account; it does not by itself rewrite every contribution or establish that all retained records are irreversibly anonymized. Shared masjid and timing information can remain available for community use. Using community functions subsequently may establish a new anonymous identity.
You can contact us to request deletion or clarification concerning retained community, measurement or diagnostic information. We handle requests within 30 days. Our ability to locate a particular record may depend on the identifiers or circumstances available; please do not send passwords, recordings or unrelated sensitive material when making a request. If your concern involves a backup or independent provider, the relevant provider's controls may also be necessary.
Where applicable law provides rights concerning access, correction, deletion, objection or restriction, contact the address below to exercise the relevant right. The scope and handling of a request depend on the information concerned and the applicable requirements. Nothing in this notice purports to waive those rights or guarantees technical access to identifiers that the Application does not retain.
16. Children and age-related handling
The Application is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe that a child under that age has supplied personal information through the Application, contact us with enough context to identify the relevant interaction so that the matter can be reviewed.
The religious or educational subject matter of a feature does not alter the automatic collection configuration disclosed above. A parent or guardian seeking clarification can use the same privacy contact channel. Please avoid including unnecessary information about the child in the initial correspondence.
17. Security measures and operational limitations
Application service connections use HTTPS, and Firestore access is governed by security rules that restrict supported writes, including a user's ability to modify votes associated with their own account. App Check, contribution limits and presence requirements provide additional controls for shared services. These mechanisms serve different purposes and should not be read as making every stored field public or making all processing anonymous.
Security also depends on device integrity, operating-system protections and the independent providers operating network services. No description of these measures constitutes an absolute guarantee against unauthorized access, failure or data loss. If you encounter a suspected privacy or security issue, contact us with the affected feature and circumstances so that it can be investigated.
18. Third-party terms, service availability and policy revisions
The terms and notices of Google, Firebase, speech-recognition providers and independent content hosts apply to their own processing. A reference to a provider in this document explains its role in a described function and does not imply that we control every aspect of that provider's logging, infrastructure, retention or account settings.
Features and integrations may change between builds or become unavailable when a service is unconfigured, inaccessible or subject to a request limit. This policy will be updated when the described processing practices change, with the effective date revised on this page. The hosted and bundled copies should be read with regard to the version made available to you; updating a source file does not itself replace a previously installed application or publish a hosted deployment.
19. Privacy contact and correspondence
For questions about this notice, clarification of a processing operation, or requests relating to your information, contact Muhammad Garana at muhammadgarana@gmail.com. State the relevant Application feature and whether the request concerns local storage, community records, analytics, diagnostics or an external service, where known.
Information you voluntarily include in an email becomes part of that correspondence and is used to address your enquiry or request. Providing sufficient context assists identification of the issue, but direct identifiers or private content that are unnecessary for that purpose should be omitted.