About this policy
Dawaaf helps customers arrange Cumro (Umrah Badal) for a beneficiary and allows assigned performers to document the service. This policy explains how Dawaaf handles personal information when you use the app, including information about someone other than the account holder.
Account and profile information
We process your name, email address, account identifier, role and authentication information to create and secure your account, sign you in and provide the correct customer or performer experience. Supabase Authentication handles sign-in credentials. Session information is stored on your device to keep you signed in.
We use account and service records to operate the app, respond to support requests, investigate problems and protect accounts and transactions.
Supabase also processes authentication session identifiers, IP addresses and authentication audit records to manage sign-in sessions, investigate access problems and protect accounts.
Orders and information about a beneficiary
Customer orders include the selected performer, order identifiers, service status, progress and relevant dates. They also include the beneficiary’s name, status or eligibility and relationship to the customer. We use these details to arrange, perform and document the requested Cumro.
A beneficiary may be another person, including someone who is unable to perform Cumro or has died. The nature of this service may reveal religious beliefs or other sensitive information. The “permanently unable” status does not record why someone cannot perform Cumro and is not limited to illness or disability. We do not request diagnoses or medical details in the order form. Provide only the information requested, and make sure you are entitled to provide another person’s information. Where appropriate, tell them how Dawaaf will use it.
The assigned performer receives the beneficiary and assignment information needed to perform the service. The customer can view their order, progress and associated evidence.
Performer profiles and assignments
Performer information includes name, profile photo where provided, city, country, biography and verification status. Customers can view performer profile information when choosing a performer or viewing their order.
We process assignment identifiers, acceptance and service timestamps, step progress, evidence records and earnings or payment status to coordinate work and maintain service and financial records.
Payments
Stripe processes payments. Payment details entered into Stripe’s payment interface are handled by Stripe; Dawaaf does not store full payment card numbers or card security codes.
Stripe may process billing country and postal code entered in the payment interface. If you choose Stripe Link, Stripe/Link may also process contact details, including your email address and phone number, to recognize your Link account, verify access and support checkout. Using Link is optional.
Stripe’s payment SDK sends payment-interface interaction events and technical information, such as app and SDK versions, operating system and device characteristics, to Stripe. It uses session identifiers for product analytics and payment-feature operation and improvement, and fraud-detection identifiers such as muid and sid to help detect and prevent fraudulent payments. These identifiers are distinct from your Dawaaf account ID and notification identifiers.
Stripe processes this information to provide payments and also for its own analytics, service improvement, fraud prevention, security and compliance purposes under its privacy policy. This SDK processing is separate from the choice to use Link and is not controlled by notification permission. Dawaaf does not use these records for advertising or customer segmentation.
Dawaaf stores and uses payment references, order links, amounts, currency and payment status to confirm purchases, reconcile transactions and handle payment issues. Stripe also handles transaction data under its own privacy practices and may retain records for its processing, fraud prevention and legal obligations.
Evidence video, audio and metadata
Performers record and upload evidence videos, including audio, for service steps. We process these files and related metadata, such as order and step identifiers, storage paths, recording or upload timestamps, duration and submission status, to document the service and make evidence available to the relevant customer.
Evidence may contain the performer’s image or voice, spoken beneficiary details and incidental images or voices of other people. Avoid recording unnecessary personal information or bystanders. Authorized service administration may access evidence when needed to operate the service or investigate issues.
Customers can save evidence to their device. Saved, exported or subsequently shared copies are outside Dawaaf’s app storage and are not removed by deleting an account or the original evidence. Device backups and services used to share those copies have their own privacy practices. Handle these copies carefully, especially when they identify another person.
Performer location during an active Cumro
With foreground and background location permissions, the app collects the performer’s precise GPS coordinates, accuracy and timestamps during an active Cumro assignment. Collection can continue while the app is in the background or the screen is locked. Location is used to document service activity and provide progress and location-update status.
The app temporarily buffers location points on the device and sends them to the backend. Tracking is tied to the active assignment; the app stops tracking when the assignment is submitted or the performer logs out, and checks for assignments that are no longer active.
Customers receive a limited status summary, such as when location was last updated and its accuracy. They do not receive raw GPS coordinates. Raw location records are restricted in the backend. Customer use of the app does not require this performer tracking.
Performers can change location permissions in device settings. Background location is required by the current app to start a Cumro; disabling permissions can prevent starting an assignment or interrupt its tracking.
Notifications and device records
When you allow notifications and the app registers for order and assignment updates, it obtains an Expo push token. Dawaaf stores this token, a randomly generated Dawaaf installation ID, device platform and account association in its Supabase backend. The installation ID is also saved in secure storage on your device. Notification events and delivery status support dispatch and help avoid duplicate messages.
Expo processes push registration and delivery information. On Android, Google/Firebase Cloud Messaging (FCM) and Firebase Installations process a Firebase installation ID and FCM registration token, together with technical app and SDK information, to identify the app installation and support messaging. Apple’s push notification service supports delivery on iOS. These installation and push identifiers are not advertising IDs.
On Android, Firebase messaging registration and installation-ID processing can occur automatically even if you deny notification permission. Denying permission controls notification display and prevents Dawaaf’s permission-dependent Expo registration flow, but does not stop all identifier processing. The app also sends its Dawaaf installation ID to Supabase when deactivating push registration during sign-out; this path can create an installation ID even without a previous notification registration.
Push delivery is an app function. Stripe’s separate analytics and payment-security processing can also occur independently of your notification choice. Notification content may be visible on your lock screen depending on device settings. You can disable notification display or change previews in those settings.
Service providers and support
Dawaaf uses Supabase for authentication, backend database services and file storage, including account and session records, profiles, orders, evidence, location and Dawaaf push-registration records. Expo, Google/Firebase and Apple process push registration or delivery information as described above. Stripe, including Link when used, processes payment information, SDK identifiers, technical information and interaction events for the purposes described in Payments.
These identifiers and related information are transmitted off your device to the recipients described above. Supabase and the push-delivery providers support Dawaaf’s app functions. Stripe also receives and uses information for its own analytics, fraud prevention, security and compliance purposes. Notification permission does not make all of this collection optional.
Information is made available to the relevant customer or performer as described above and to authorized people who need it to operate or support Dawaaf. Information may also need to be disclosed to address fraud, disputes or applicable legal requirements.
Support opens WhatsApp, an external service, using the existing Dawaaf support number. If you choose to contact support, WhatsApp processes your interaction under its own privacy practices, and Dawaaf receives the information you send. Send only what is needed for your request; never send your password or full card details.
Retention and account deletion
Information is kept according to its purpose: providing active services, resolving support or payment issues, maintaining necessary financial records and meeting applicable obligations. Retention depends on the record type, order status and any unresolved dispute or obligation; this policy does not promise a fixed deletion period.
Dawaaf’s push tokens and installation IDs are stored and reused rather than processed only in memory. Signing out deactivates the corresponding backend push record; deactivation does not itself erase it or the installation ID in secure device storage. The customer account-deletion processing removes that customer’s push-registration records. No fixed automatic expiry for inactive Dawaaf push records is promised.
Expo states that notification contents are held only in memory and queues for delivery to Google or Apple, rather than stored in databases. This describes message contents, not a deletion deadline for push tokens or registration records.
Firebase manages its installation and messaging identifiers separately from your Dawaaf account. Dawaaf’s account-deletion flow does not itself request deletion of a Firebase installation ID. Disabling notifications or deleting a Dawaaf account therefore must not be understood as immediate deletion of all Google/Firebase records. Contact Dawaaf for help with identifier-related privacy requests.
Stripe retains information as needed to provide its services and may keep it afterwards for fraud prevention, legal, regulatory, tax, accounting and financial-reporting obligations. Dawaaf account deletion does not automatically erase Stripe’s SDK or transaction records. You can raise requests with Dawaaf and, for Stripe’s own processing, through Stripe’s privacy channels. No single retention period is promised for Stripe identifiers.
Customers can request account deletion in Account → Delete account. The current flow verifies the request and may require active orders, payments or other unresolved issues to be reviewed before finalization. A deletion request does not itself cancel or refund an active paid Cumro.
The deletion process removes the account and profile, clears beneficiary details from retained orders and removes customer links through controlled processing. Some order, performer earnings and financial records may remain where needed. Evidence, GPS and payment-related records are handled through controlled retention and cleanup, rather than an immediate blanket deletion.
Remaining evidence or Stripe records can still identify people and must not be treated as anonymous merely because the customer link has been removed. Stripe’s own transaction records and copies saved or shared outside Dawaaf are not erased by Dawaaf account deletion.
Performers can contact Dawaaf through Support about closing their account or handling their data. The app’s current self-service deletion flow is for customers.
Security
Dawaaf uses authenticated access, role-based database and storage restrictions, time-limited links for viewing stored evidence. These safeguards help limit access to personal information. No app, device or online service can guarantee absolute security. Keep your device and sign-in credentials secure.
Permissions, choices and privacy requests
Camera and microphone permissions enable performer evidence recording. Photo-library permission is requested when saving evidence to your device. You can deny or revoke permissions in device settings, but the related recording, saving, notification or location feature may then be unavailable.
You can contact Dawaaf through Support to ask about your information, request correction or access, or raise a deletion or privacy concern, including a concern about beneficiary information supplied by someone else. Depending on applicable law, you may also have rights to restrict or object to processing, request a portable copy or complain to a data protection authority. Requests may require identity or authority verification.
Contact Dawaaf
For privacy questions or requests, use Support in Customer Account or Performer Profile to contact Dawaaf through WhatsApp at +46 73 568 87 49. This opens an external service.
Policy updates
We may update this policy as the service or its data handling changes. The latest published policy is available at https://mhadann.github.io/dawaaf-privacy/ with its last-updated date. The app contains a policy copy that is updated with app releases and may have an earlier date.