This policy explains what data the app uses, which optional external services it uses, and how data can be controlled and deleted.
1. Data stored on the device
The app may store the following data locally:
- Profile names, gender, date of birth or age, and personal photos or avatars.
- Tracking of prayers, adhkar, fasting, Quran reading, activities, plans, lessons, and progress.
- Notes, private entries, and zakat reminder information.
- Notification, sound, location, and prayer-time settings.
- Mosques added by the user and the visit history associated with the mosque-tracking feature.
- Audio files imported by the user.
This data is used to provide the features selected by the user. Rafiki does not upload users’ names, photos, worship records, or notes to Nour El Islem’s servers.
2. Optional Internet connection
Some features connect to external services:
- City search: sends the entered city name and search language to geocoding-api.open-meteo.com to obtain coordinates.
- Map display: requests map-tile images from tile.openstreetmap.org. These requests reveal the area being displayed.
- Nearby mosque search: sends the coordinates of the map’s center and the search radius to overpass-api.de. These coordinates may be the device’s location if the user chooses that option.
These services also receive the IP address when a connection is made. These requests do not include profile names or photos, worship records, or mosque visit history.
The service providers’ own policies govern how they process and retain requests. Storing data locally does not mean that optional services send no information over the Internet.
The location can be entered manually, and the core features can be used without opening maps or performing an online search for mosques. Links opened by the user in a browser or in external apps are also subject to the policies of the respective parties.
3. Device permissions
Depending on the operating system and the selected features, the app may request:
- Location: to determine coordinates, calculate prayer times and the qibla, and add a mosque.
- Background location: to track arrival at and presence in a mosque when this feature is enabled, even when the app interface is not open.
- Notifications and exact alarms: to display alerts at their scheduled times.
- Full-screen alerts, Do Not Disturb, and background operation permissions: to provide the adhan and alert options permitted by the system.
- Camera or photo and file selection: when the user chooses a profile picture or imports a file.
Mosque visits are analyzed on the device. Rafiki does not upload movement or visit history to Nour El Islem’s servers. On Android, the mosque-tracking service is shown through an ongoing notification and can be stopped.
Permissions can be refused or withdrawn in the device settings. The part of the app that depends on them may then stop working. The qibla is calculated locally using the coordinates and the sensors available on the device.
4. Children and family profiles
Parents can create local profiles for family members and track their activities within the app. Rafiki does not create cloud accounts for children and does not show them targeted advertisements.
We recommend that a parent or guardian manage children’s profiles and device permissions, enter the location manually when they wish to avoid online services, and disable mosque tracking when it is not needed. The information stated about external services applies whenever those services are used with any profile.
5. Connection with the Tahzib tadabburi Quran app
The user may choose to open the Tahzib app to continue reading and then send the result of the reading session to Rafiki through the connection between the two apps on the device.
The result may include the amount or range read, the time, and identifiers for the connection session. This does not require sending the name, photo, or the rest of the worship record to a Rafiki server. The reading is sent when the user chooses to do so, and its receipt is confirmed within Rafiki.
6. Advertising and analytics
The current version does not include advertisements, usage analytics tools, or advertising tracking. Nour El Islem does not sell Rafiki users’ data.
7. Backup and export
Automatic cloud backup and automatic app-data transfer are disabled in the current Android version.
The user can manually create a backup in JSON format. It may contain profiles, records, and settings. Private entries are excluded by default and are included only when the user chooses to include them. The backup does not contain profile pictures or their file paths.
The exported file is human-readable and is not encrypted. If the user chooses to save or share it through an external service, that copy is subject to the selected service’s policy. Earlier backups are not deleted automatically when data is deleted from the app.
8. Data retention and deletion
Data remains stored locally until the user deletes it. The mosque visit history retains the most recent one thousand visits for each profile.
Deleting a profile deletes its local records and the app’s copy of its picture if no other profile uses it. This does not delete the original picture from the gallery or any previously exported backups.
App data can be deleted from the Android settings. External copies must be deleted separately. There is no user-account database on Rafiki’s servers that would require a request to delete a cloud account.
9. Data protection and on-screen visibility
Data storage relies on the app’s storage area and the protections provided by the device’s operating system. Users are advised to enable the device lock and keep backups in an appropriate location.
Information about the active profile or alerts may appear in the widget and notifications. This can be controlled through the app and system settings.
10. Contact and policy updates
For questions concerning privacy in Rafiki:
When you contact us, we receive your email address and the content of your message so that we can process and respond to your request.
We may update this policy when the app’s features or data-processing practices change. We will publish the updated version on this same page and change the update date.