TAZA Prayer Data & Permissions — TAZA Innovative Tech

Last updated: 16 September 2026

Current data-safety snapshot

Data / permissionCurrent useTAZA server

Approximate locationOptional foreground functionality for timetable/QiblaNot automatically uploaded

Precise locationOptional foreground functionality when grantedNot automatically uploaded

Location search textPassed to Android Geocoder to resolve a placeNot sent to a TAZA server

Prayer preferencesStored in local app storageNo

Timetable cacheStored locally for app functionalityNo TAZA account storage

Crash diagnosticBounded local diagnostic; user may choose to share with supportNo automatic upload

This page describes the current release-preparation source. The final Google Play declaration must be completed from the exact shipping AAB and all bundled SDKs.

Android permissions

INTERNET — permitted network prayer-source requests and system/service connectivity where required.
ACCESS_COARSE_LOCATION / ACCESS_FINE_LOCATION — optional foreground device location for timetable/Qibla features.
POST_NOTIFICATIONS — prayer/azan notifications on supported Android versions.
SCHEDULE_EXACT_ALARM — timely prayer alarms where Android requires exact scheduling access.
RECEIVE_BOOT_COMPLETED — restore schedules after reboot.
WAKE_LOCK — support time-sensitive alarm/audio execution.
FOREGROUND_SERVICE / FOREGROUND_SERVICE_MEDIA_PLAYBACK — azan playback while a foreground media service is active.
VIBRATE — optional haptic feedback.

The device compass is declared as an optional hardware feature; the app can still install on devices without it.

Collection versus on-device access

Google Play distinguishes data that stays on-device from data that is transmitted off-device. TAZA Prayer’s device location is currently used on-device and is not automatically sent to a TAZA server. Location search may be processed by Android’s platform geocoding service, which is separate from TAZA’s own servers.

Ads and tracking

The current release preparation contains no advertising SDK and no TAZA analytics/tracking SDK. If that changes, this page, the Privacy Policy and the Play Console declaration must be updated before release.

Account and deletion

The current release preparation has no user account system. Local app data can be removed by clearing the app’s storage or uninstalling the app. If a future account feature is introduced, TAZA will add the required account-deletion process and public instructions before release.

Release audit rule

Before every production submission, TAZA must audit the final bundle for permissions, bundled SDKs, endpoints, account features, payment flows and any new data transmission. Public disclosures and Play Console answers must match the shipping version.