Awwab Privacy Policy
Last updated: 19 October 2026
What the app stores on your device
- Your prayer log, the status you record for each prayer.
- Your settings, including reminder times and your answer about gender, which sets the statuses the app offers.
- Your coordinates, if you allow location access.
Location
If you allow location access, the app reads your coordinates to calculate prayer times and the Qibla and to suggest a calculation method, and reads them again each time it comes to the front, so the times follow you when you travel. On iPhone its widgets can read your location too. Location is optional, but without it the app cannot show prayer times for where you are.
What leaves the device, and to whom
Place names. To name your city, the app sends your coordinates to the phone's geocoding service: Apple's on iPhone, and on Android the one the phone provides, usually Google's.
Backup, if you turn it on. The app keeps a copy of your prayer log in a folder of its own, in your iCloud Drive on iPhone or in the Google Drive of the account you choose on Android, and reads it back to bring in what your other devices logged. Apple or Google holds it under your own agreement with them until you delete it.
Crash reports, usage and feedback: Google. Each install is known to Google's Firebase services by a random identifier, and each service receives the device and app version. Crashlytics receives a record of each launch, and a report when the app crashes or hits an error: what failed, the events just before it, and the app's language and appearance. Analytics counts how often and how long the app is used, with your language and a city worked out from your IP address. Remote Config sends the app settings that can change without an update, such as which versions are still supported, and receives the phone's regional settings and when the app was first opened. Feedback you send from Settings is kept on Google's servers, with what it is about, the email address you add for a reply, if any, and the app's version, the system's version and the phone's model, until the developer deletes it. Google keeps crash reports for 90 days, usage data for at most 14 months after the app was last used, and the identifier until 270 days after its last use.
Updates and downloads. Each time the app starts, it asks Expo's update server whether newer app code exists, sending app and platform details, a random install identifier and your IP address, and after a launch that ended in a fatal error, that error's text, so a broken version can be replaced. Expo keeps these records for as long as its update service needs them. The app asks the store it came from whether a newer version is out: on iPhone the App Store, run by Apple, which receives the app's identifier, your region and your IP address, and on Android Google Play, which receives the device's details and the app's version. Adhan voices beyond the one built in, and the list of them, download from GitHub (GitHub, Inc.), which receives your IP address and which file was asked for, and keeps it as its own privacy statement describes.
Why this is allowed. The backup and any feedback you send rest on your consent, given when you turn backup on or send it. Everything else here rests on legitimate interest in an app that works, keeps working and is known to be used: naming your city, the crash reports, the usage counts, the checks for newer versions and the adhan voices you download.
Your right to object. You can object at any time to what rests on legitimate interest, at the address below. None of it can be matched to you, so deleting the app is how it stops, after one last report on Android that notes the removal. What was already sent is kept for the periods above.
Turning it off. Location access can be withdrawn at any time in the system settings, and backup turned off with its switch in the app's Settings. None of this is required by law or contract: location and backup are optional, and the reports and checks come with using the app.
Everyone named here receives this data only under terms that protect it at least as this page describes. Google, Expo and GitHub process it in the United States and other countries where they run servers, under the EU-US Data Privacy Framework and its UK extension, which all three are certified under. Everything that leaves travels over an encrypted connection.
Your choices
Deleting the app removes your log, settings and coordinates from the device. A backed-up copy stays until you delete it, in iCloud's storage settings or, for Google Drive, on the web under Settings, Manage apps. Export, in the app's Settings, gives you your prayer log as a file.
You have the right to see, correct or erase what is held about you, to restrict or object to its use and to receive it in a portable form. What reaches Google, Expo and GitHub is not tied to your name or any account, so a request to see, correct or erase it cannot be matched to you. Feedback you sent can be found by the email address you gave with it. You can still write to the address below, and you can complain to the data protection authority where you live.
Who is responsible, and how to get in touch
Awwab is made by Ahmed Nabil.
Questions about this policy: ahmednmourad.dev@gmail.com