Last updated: 16 September 2026
Scope
This Privacy Policy applies to the Android app TAZA Prayer, application ID com.tazainnovativetech.tazaprayer, published by TAZA Innovative Tech. It describes the current release-preparation architecture and will be reviewed against the exact production bundle before public release.
Privacy summary
- No user account is required in the current release preparation.
- No advertising SDK is included in the current release preparation.
- No TAZA analytics or cross-app tracking SDK is included in the current release preparation.
- Device location used by TAZA Prayer is not automatically uploaded to a TAZA server in the current implementation.
- Most settings, timetable cache and diagnostics are stored locally on the device.
Location
TAZA Prayer can request approximate or precise foreground location when you choose features that need location, including timetable selection and Qibla guidance. The app does not request Android background-location permission in the current release preparation.
Location can be avoided by using supported manual location, coordinates or prayer-zone choices where available. A location fix includes coordinates, accuracy and freshness information and is used to calculate or validate the relevant feature.
Location search and geocoding
When you search for a postcode, city, ward or locality, TAZA Prayer uses Android’s Geocoder service. Depending on your device and Android implementation, the device/platform geocoding provider may process the search query or coordinates to return a place result. TAZA Innovative Tech does not receive those geocoding queries on its own server in the current implementation.
Local storage
The app stores items such as prayer preferences, selected timetable location, cached timetable records and operational state locally using Android app storage, DataStore and Room database components. Android application backup is disabled in the current manifest.
Crash diagnostics
TAZA Prayer can keep a bounded crash diagnostic file locally on the device. It is designed to include app version, source/build reference, Android API level, manufacturer/model, exception classes, stack frames and limited process-exit information.
The diagnostic implementation intentionally omits arbitrary exception messages because they could contain coordinates, URLs or user data, and it states that coordinates, saved settings and device identifiers are not collected in the report. The app does not automatically upload this diagnostic. If you choose to send diagnostic information to support, the contents you send become part of your support correspondence.
Network access and prayer-time sources
TAZA Prayer has internet permission because some supported features may require network access. Japan prayer times in the current implementation are calculated on-device and do not require a network source. Malaysia provider access remains release-gated and will only be enabled when the required authorization and release validation are satisfied.
When a permitted remote timetable source is enabled, the app may send the supported prayer-zone identifier and requested date range to that source over HTTPS. The provider’s own policies apply to its service.
Notifications, alarms and audio
TAZA Prayer can request notification permission and Android exact-alarm scheduling to provide prayer reminders. Azan playback uses a foreground media-playback service while audio is actively playing. These functions are used for app functionality and are not advertising or tracking mechanisms.
Retention and deletion
Local app data generally remains until it is replaced, you clear the app’s storage, or you uninstall the app. Because the current release preparation has no TAZA user account, there is no cloud account profile to delete. Email support correspondence can be deleted or retained according to support, security and legal needs.
Children
TAZA Prayer is a general prayer utility and is not designed as a child-directed app. If the product’s target audience changes, this policy and the relevant store declarations will be updated before that change is released.
Security
We minimise data movement where practical and use HTTPS for supported network requests. No system is perfectly secure; please report potential vulnerabilities through our security page.
Contact
Privacy questions: privacy@tazainnovativetech.com
Product support: support@tazainnovativetech.com
Changes
We will update this policy when the app’s permissions, SDKs, server integrations, account model or data practices materially change. The Play Console Data safety declaration must be kept consistent with the exact production app.