Privacy Policy
Last updated: 17 November 2026
This Privacy Policy explains how Dawa Time (“the App”) handles information. The App is operated by Anas Qazzaz. Contact: anasharith2@gmail.com.
1. What the App is for
Dawa Time helps people manage medication reminders and, if they choose, share limited reminder information with caregivers. The App is not medical advice and does not replace a doctor or pharmacist.
2. Information we collect
Depending on how you use the App, we may process:
- Account details: email address and password, or sign-in through Google or Apple.
- Profile details you enter: name (optional), age or date of birth, phone number, and other profile fields if you provide them (such as gender, city, or health conditions).
- Medication information: medication names, dosage, schedules, instructions/notes, and dose history (taken, skipped, or snoozed).
- Caregiver links: invitation codes and the relationship between a patient account and a caregiver account, including a caregiver display name.
- Research questionnaire answers: optional OMAR-7Qs weekly responses if you submit or skip them in the App.
- Research contact preference: a research-contact preference stored with your account (off by default).
- App settings: preferences needed to run reminders and sync.
- Technical identifiers needed for the service: account identifiers created by our authentication providers. The App may also create an anonymous Firebase authentication identifier during start-up. We do not use a separate analytics or crash-reporting SDK in the current App.
The App does not request access to your location, contacts, camera, microphone, or photos.
3. Why we use this information
- To create and secure your account.
- To schedule and show medication reminders on your device.
- To sync your data across your signed-in devices when online.
- To let you invite a caregiver and, if linked, let that caregiver see the limited information described below.
- To store optional research questionnaire responses and to honour the research-contact preference stored with your account.
- To delete your account and related data when you request deletion.
4. Where information is stored
- On your device: medication, profile, reminder, and related data are stored locally so the App can work offline. Sensitive fields on the device are protected with application-level encryption; the whole local database file is not encrypted as a single block.
- On our cloud backend (Supabase): when you use an account that syncs, the same categories of account, profile, medication, dose, caregiver, consent, preference, and questionnaire data are stored on Supabase so sync, caregivers, and research tools can work. Server-stored product data is protected with access controls (including database row-level security) and encrypted connections (HTTPS/TLS). We do not claim that every server field is encrypted at rest beyond what the hosting provider applies.
- Firebase: the App initialises Firebase Authentication and may create an anonymous Firebase user ID. Caregiver features in the current App run through Supabase, not Firestore.
- Google / Apple: if you sign in with Google or Apple, those providers process the sign-in information needed to authenticate you.
5. Sharing with caregivers and others
- Caregivers you link: an active caregiver can see limited patient information needed for monitoring, including name, phone number (if provided), listed health conditions (if provided), medications, schedules, and dose events. Date of birth, gender, and city are not shared with caregivers through the App’s caregiver views.
- Service providers: Supabase hosts authentication and synced data. Google and Apple process OAuth sign-in when you choose those methods. Firebase Authentication may receive an anonymous identifier as described above.
- Research administrators: authorised research staff can view aggregate questionnaire analytics. Identifiable research exports are available only through server controls that require the relevant research consent to be active.
- We do not sell your personal information.
6. Account and data deletion
You can request deletion of your account from the App’s account settings. When deletion succeeds, the App asks the server to remove your synced account data (including profile, medications, dose history, caregiver links you own, preferences, consent, and questionnaire responses) and your authentication user. Local data on a device is cleared as part of the App’s account/sign-out flows. Some patient-owned caregiver notification audit records may retain a detached reference after a caregiver account is deleted, as designed for the patient’s own audit history.
We do not currently publish a separate automatic retention period for active accounts. Cloud provider backups may retain copies for a limited time according to the provider’s backup process.
7. Children
The App is designed for medication reminder use by adults and caregivers. Do not use it to create an account for a child if you are not permitted to do so.
8. Changes
We may update this Privacy Policy when the App’s data practices change. The “Last updated” date at the top will change when we do.
9. Contact
Privacy questions or deletion requests: anasharith2@gmail.com (Anas Qazzaz).