← Back to the portal

Privacy Policy

Al Muhrim (mvumrah) · app, website and agency portal · Last updated —

Draft — five things must be fixed before this is published

This policy was written from an audit of what the code actually does. Five statements below are not yet true and are marked [FIX FIRST]. Publishing a privacy policy that misdescribes reality is worse than having none, because it is a public representation you can be held to. Fix those five, then delete this box. Items marked [CONFIRM] need a fact only you know.

1. Who we are

[CONFIRM: registered company name, registration number and address] operates the Al Muhrim mobile app, the mvumrah.com website and the agency portal. In this policy "we" means that company and "you" means anyone using the app or portal.

Contact for anything in this policy: support@mvumrah.com

2. The short version

  • The app has no accounts. You can read every guide, dua, prayer time and Qibla direction without giving us anything at all.
  • We only receive personal details when you deliberately do something that needs them — book a package, place a shop order, buy an eSIM, or rate an agency.
  • Your location never leaves your phone. It is used on-device to point the Qibla compass and nothing else.
  • We run no analytics. We do not track what you read, we do not build a profile of you, and we do not sell or rent anyone's data.
  • Push notifications are powered by Google Firebase, which does collect a device identifier.

3. What we collect, and only when you ask us to

Nothing in this section happens unless you actively submit the form in question.

When you… We receive Why
Book a Hajj or Umrah package Your name, phone number, national ID number, party size, an email address if you give one, and any notes you write The agency needs these to register you for the pilgrimage. The ID number is required for Hajj and Umrah registration.
Place a shop order Your name, phone number, island, delivery address, what you ordered, and an email address if you give one To take payment and deliver the goods.
Buy a travel eSIM Your phone number, and an email address if you give one To issue the eSIM and let you retrieve it later.
Upload a bank transfer slip The photograph you take, which usually shows your name, your account details and the amount To confirm your payment.
Rate an agency Your phone number, your star rating and your comment To show ratings and stop the same person rating twice.
Register as an agency Agency name, email, phone, password, your licence or permit document, and the date, time and IP address of your acceptance of the terms To create and approve the agency account, and to keep a record that the terms were accepted.

Your phone number is your key. Because there are no accounts, we use your phone number to prove an order or booking is yours when you check its status. Anyone who knows your phone number and your order reference could see that order's details, so treat your reference number as private.

4. What we do not collect

  • Your location is never sent to us. When you open the Qibla compass the app asks your phone for your position, calculates the bearing to the Kaaba on the device, and discards it. It is never stored and never transmitted. Prayer times are calculated from fixed Makkah and Madinah coordinates, not from where you are.
  • No analytics of our own. The app contains no analytics, crash-reporting, advertising or attribution software. We do not know which guides you read, how long you spend in the app, or whether you finished your Umrah.
  • No advertising identifier. The app does not read your device's advertising ID and shows no personalised advertising.
  • Your camera is used once. Only to photograph a payment slip, only when you choose to, and the photo goes nowhere except to us for that payment.
  • We never sell, rent or trade personal data.

5. Sponsored content in the app

The app shows sponsored cards. To count how many times a card was shown or tapped, the app creates a random identifier the first time it runs and stores it on your phone. It is generated on the device, is not derived from anything about you or your hardware, and is sent only with the card's identifier and whether it was seen or tapped. It tells us nothing else about you, and deleting the app deletes it.

6. Notifications

Push notifications are delivered by Google Firebase Cloud Messaging. When the app first runs it registers with Google, which issues a token identifying your installation. We store that token so we can tell you when your order status changes.

Google's push component also generates its own installation identifier and sends operational diagnostics to Google. We do not receive that information; its handling is covered by Google's privacy policy.

[FIX FIRST] You can turn notifications off at any time in the app's settings, and in your phone's system settings. Not yet true: the app subscribes every install to a promotional topic at first launch with no in-app way to opt out. Either add the opt-out or delete this sentence and describe what actually happens.

7. What stays on your phone

Your reading progress, completed guide steps, Tawaf and Sa'i counts, packing checklist, saved duas and preferences are stored only on your device. We never receive them.

Android backup is switched off for this app, so that on-device data is not copied to Google Drive and does not transfer to a new phone. Uninstalling the app erases all of it.

8. Who else sees your data

  • The travel agency you book with. When you book a package, that agency receives your name, phone number, national ID number and party size so it can register you. Agencies are bound by our terms to use it only for your booking. Until an agency responds to your booking it sees only the package and party size, not your identity.
  • Google. For push notifications, as described above. The app also downloads a display font from Google's font servers, which means Google sees your device's IP address when the app first loads it.
  • Telegram. Our staff receive an alert in a private Telegram channel when an order is placed, so we can act on it quickly. For shop and eSIM orders that alert contains your name and phone number, and for shop orders your island.
  • eSIM suppliers. When you buy an eSIM we send our supplier only the plan and an internal reference number. We do not send them your name, phone number or email. [CONFIRM] One eSIM route is fulfilled by a related service operated by us, which does receive your phone number and email — name it here and state whether it messages you.
  • Our hosting provider. The app's data is held on servers operated by Hostinger. [CONFIRM: which country those servers are in, and Hostinger's access-log retention period — ask them.]

We do not send marketing email or SMS. We have no email or SMS system connected at all.

9. Payment slips

[FIX FIRST] Payment slips you upload are stored privately and are visible only to our staff.

Not yet true. Slips are currently written to a public folder and can be opened by anyone who guesses the filename, which is derived from a sequential reference and a timestamp. This must be fixed before this policy is published — see the note at the end.

10. How long we keep things

[FIX FIRST] We keep booking, order and eSIM records for [CONFIRM: how long — a common choice is 24 months after the trip, or 7 years if Maldivian tax law requires it], then delete them. Payment slips are deleted once the payment is confirmed and any refund window has closed.

Not yet true. Nothing is deleted today — there is no retention period and no deletion job anywhere in the system, so records accumulate indefinitely. Decide a period, implement it, then state it here.

11. Your choices

  • Use the app anonymously. Every guide, dua, prayer time, counter and the Qibla compass work without giving us anything.
  • Ask for a copy of your data, or ask us to delete it. Email support@mvumrah.com from the address you gave us, or write from the phone number on the order. We will respond within [CONFIRM: 30 days is the usual commitment]. [FIX FIRST] There is currently no way to action a deletion request — no endpoint, no admin control. Build at least a manual process before promising this.
  • Turn off notifications in your phone's settings at any time.
  • Refuse location — only the Qibla compass will stop working. Nothing else in the app depends on it.

12. Children

The app is intended for adults arranging their own pilgrimage. We do not knowingly collect data from children. A booking may include children in the party size, but we collect no personal details about them beyond the count.

13. Security

Traffic between the app and our servers is encrypted in transit. Agency and staff accounts are password-protected and passwords are stored hashed, never in readable form.

No system is perfectly secure. If we become aware of a breach affecting your data we will tell you [CONFIRM: by what means].

14. Changes to this policy

We will update this page when our practices change, and change the date at the top. Material changes will be announced in the app.

15. Contact

support@mvumrah.com

Delete this box before publishing — fix list

  1. Payment slips are publicly readable. Move them out of public/ and serve them through an authenticated route. Verified live: an unauthenticated request returns the image.
  2. Set and implement a retention period, plus a way to action a deletion request. Nothing is deleted today.
  3. Add a notifications opt-out in the app, or reword section 6.
  4. An agency sees the pilgrim's phone and national ID as soon as it changes the booking status — including when it rejects the booking. Decide whether that is intended; the policy currently implies contact is revealed only on acceptance.
  5. The eSIM lookup accepts a phone number alone and returns that person's eSIM history including the SIM's activation credentials. Add the order reference as a second factor.

Separately, not a policy matter but an App Store blocker: the iOS app has no PrivacyInfo.xcprivacy manifest, and the full APNs device token is printed to the system log in release builds (ios/Runner/AppDelegate.swift:28).

Al Muhrim · mvumrah.com