1. Who publishes the app
AWAS is published by AstafLab, an independent developer. Questions about this document can be sent to contact@astaflab.com.
2. What this document covers
This document covers the AWAS Android app, package com.astaflab.awas, distributed on Google Play.
It does not cover third-party services you use elsewhere, including Google Play itself, which applies its own rules.
3. Data collected
AWAS collects nothing. In practice:
- there is no account, no sign-up and no identifier of any kind — the app generates neither an advertising ID nor a technical one;
- it does not read your location or use the GPS;
- it does not read your contacts, files, system calendar, camera or microphone;
- it contains no analytics or measurement tooling;
- it shows no advertising and embeds no ad network;
- it makes no network requests at all. AstafLab runs no server, and so receives nothing about you.
4. Data kept on your device
The app saves your settings on your device, in four files:
- the places you have saved — name, latitude, longitude, elevation and time zone — each with its own calculation method and per-prayer minute corrections, plus which place is currently selected;
- your general preferences: the school followed for Asr, the theme, the language, and your prayer-alert settings;
- any calculation methods you have defined yourself;
- the notes you write against a date in the calendar. These are free text you type yourself; the app stores and redisplays them, and does not read or analyse them.
These files live in the app's private storage, which other apps cannot read. They are sent neither to AstafLab nor to anyone else — the app makes no network requests.
Android itself may include these files in your device's automatic backup to your Google account, as it does for other apps. That backup is a system feature, controlled in your Android settings; it does not pass through AstafLab, who has no access to it.
All of it is erased when you uninstall the app, or when you clear its data from the Android settings.
5. Android permissions
AWAS requests no permission that grants access to personal data: no location, no GPS, no contacts, no shared storage, no camera, no microphone, no phone.
The four permissions it declares exist only for prayer alerts:
- POST_NOTIFICATIONS — to show the alerts. Android asks you for it the first time you turn one on; declining does not stop you using the app.
- SCHEDULE_EXACT_ALARM and USE_EXACT_ALARM — to fire an alert at the minute it is due, rather than at the system's next batched wake-up.
- RECEIVE_BOOT_COMPLETED — to put the alerts back in the queue after the device restarts.
None of these gives access to anything about you, and nothing is transmitted when they are used. If you turn on no alerts, none of them comes into play.
Prayer times are computed locally from the coordinates of the place you chose, not from a position read off the device.
6. Third-party components
The app bundles open source components. All of them run locally, on the device, and open no network connection:
- the PyEphem astronomical engine, which runs on the device;
- the Flutter framework, and the flutter_local_notifications and timezone libraries, used for the alerts;
- a city database derived from GeoNames, licensed CC BY 4.0, shipped inside the app and searchable offline;
- two typefaces under the SIL Open Font License.
None of these components sends anything anywhere. Their licence texts ship with the app.
Downloading and updating the app goes through Google Play, which applies its own privacy rules to that exchange, independently of this document.
7. Children
AWAS collects no data from anyone, at any age. No separate provision for minors is therefore needed.
8. Your rights
AstafLab processes no personal data about you. There is consequently no record, no profile and no history held by AstafLab to access, correct or delete.
The settings and notes stored on your device remain entirely under your control: change them in the app, or remove them by clearing the app's data or uninstalling it.
9. Changes
Any future feature that would require a network connection, an in-app purchase or the processing of data will be reflected in an updated version of this document, published on this page before that feature ships.