Privacy Policy

The short version

• We collect what an Umrah travel agency needs to serve you: your phone number, the traveller and passport details you submit, your booking and payment records, and basic device data.
• We do not sell your personal data, and we do not use it for third-party advertising or ad profiling.
• Location, camera, photos, and notifications are all optional. The app works for browsing packages without any of them.
• Passport scanning happens on your device. The text-recognition step never uploads your passport to a third-party OCR service.
• You can delete your account and personal data yourself — in the app (Settings → Delete account) or from the form on this page.

1. Who we are

AoMadinah (“AoMadinah”, “we”, “us”, “our”) is the travel platform operated by Peer Bukhari Travels, a travel agency arranging Umrah and related travel services. We are the data controller for the personal data described in this policy — meaning we decide why and how it is processed.

For any privacy question, request, or complaint, write to support@aomadinah.com. We answer privacy requests within 30 days.

2. What this policy covers

This policy applies to:

• the AoMadinah mobile app for Android and iOS (package / bundle ID com.aomadinah.app);
• the website aomadinah.com, including the blog and this page;
• our backend services — the Firebase project that stores your account and booking records, and the staff admin console our team uses to fulfil your booking.

It does not cover airlines, hotels, visa authorities, banks, or other independent companies that handle your travel once a booking is made. They act as their own controllers under their own privacy policies. See section 9.

3. What we collect

We collect only what a specific feature needs. Categories marked optional are never required to browse packages or use the app's free tools.

3.1 Account and profile

We do not ask for an email address or a password. We do not collect your name from your contacts, your address book, your call log, or your SMS messages.

3.2 Traveller (Mu'tamirin) and passport details

To issue a quote and process visas and tickets, we collect for each traveller you add: full name as printed on the passport, passport number, date and place of issue, expiry date, date of birth, gender, nationality, and an image of the passport data page. You may also upload other documents we are required to collect for a specific booking (for example a vaccination record or a relationship certificate, where the destination authority requires it).

Passport data is sensitive personal data. We treat it accordingly: it is stored in access-restricted locations, readable only by you and by the staff assigned to your booking, and it is scanned for malicious files on upload (see Security).

3.3 Booking, quote, and payment records

• Quote requests and bookings — the package, city, hotel and room choices, travel dates, traveller counts, quote versions you were sent, your acceptance or rejection, cancellation and refund requests, and the status history of your booking.
• Messages and notes — what you send our team through the booking workflow, and internal staff notes about fulfilling it.
• Wallet and payments — top-up requests, the payment receipt or proof-of-transfer image you upload, the bank or method you state, amounts, ledger entries, holds against a booking, and refunds.
• Travel documents issued to you — visas, tickets, vouchers, and itineraries our team publishes to your booking.

3.4 Device and technical data

• Push token and device record — a Firebase installation ID and messaging token per device, plus platform (Android/iOS) and app version, so notifications reach the right device and stale tokens can be cleaned up.
• App version / build number — to tell you when an update is required.
• Device integrity attestation — Firebase App Check (Play Integrity on Android, App Attest / DeviceCheck on iOS) issues a token proving the request comes from the genuine app. This blocks bots and scraping of your data. It does not identify you personally.
• Crash and error reports — Firebase Crashlytics records the crash stack trace, device model, OS version, app version, and the moments leading up to a crash. Crash collection is disabled in development builds.
• App usage events — the Firebase Analytics SDK is included in the app and automatically records standard usage events such as app opens, screen views, and session length, along with device model, OS version, and a coarse region derived from your IP address by Google. We use this only in aggregate, to see which features are used and where the app breaks.
• Activity counters — we record the days on which your account was active, so we can count daily / weekly / monthly active users. This is a set of dates, not a log of what you did.
• Server logs — our backend and website record standard request logs (IP address, timestamp, endpoint, error codes) for security, abuse prevention, and debugging.

3.5 Location and sensors

• Location Optional — used only while you are using the app, for two features: the Qibla direction, and local weather. If you decline the permission, everything else in the app still works.
• Weather lookups — when you use weather, your coordinates are rounded to roughly a 1 km grid before we cache and request the forecast, so the cached record cannot pinpoint you. The request goes to WeatherAPI.com through our server, without your name, phone number, or account ID attached.
• Qibla — direction is computed on your device from the compass, magnetometer, and accelerometer. Sensor readings stay on the device and are never uploaded.
• Prayer times and Hijri dates — calculated on-device from your location or the city you pick.
• We do not collect background location. The app does not track you when it is closed.

3.6 Camera, photos, and files

Camera and photo-library access are used only when you take an action that needs them: augmented-reality Qibla, setting a profile picture, scanning or attaching a passport, and uploading a payment receipt. We access only the specific item you select. We do not scan or index your photo library.

3.7 Support and problem reports

When you use “Report a problem”, we receive your description of the issue together with your user ID, phone number, and name, so we can reproduce the problem and reply. If you contact us by email or WhatsApp, we keep that correspondence.

4. Where the information comes from

• From you — everything you type, upload, or select.
• From your device, automatically — the technical data in section 3.4, and location only with your permission.
• From our travel suppliers — booking references, ticket and visa status, and confirmations relating to your trip.
• From someone travelling with you — a group leader or family member may add your traveller details to their booking. If you were added by someone else and want your details removed, email us.

5. Device permissions

6. How we use your information

• Create your account and sign you in securely by SMS verification.
• Show you packages, fares, hotels, and travel tools.
• Prepare quotes, take bookings, collect and check travel documents, apply for visas, and issue tickets and vouchers.
• Record payments, run your wallet ledger, apply holds against a booking, and process refunds.
• Send you transactional notifications about your booking, quote, payment, and documents.
• Provide the free tools — Qibla, prayer times, duas, weather, and the blog.
• Keep the service safe and working: device attestation, abuse and fraud prevention, malware scanning of uploads, rate limiting, crash diagnosis, and aggregate usage measurement.
• Meet legal, tax, travel-agency, and immigration obligations, and handle disputes or claims.

We do not sell personal data, share it with data brokers, use it to build advertising profiles, serve third-party ads in the app, or use your passport or booking data to train AI models.

7. Legal bases

Where the GDPR, UK GDPR, or a similar law applies to you, we rely on these bases:

Where we rely on consent, you can withdraw it at any time — by revoking the permission in device settings, switching notifications off, or deleting your account. Withdrawal does not affect processing already carried out.

8. Notifications

Notifications we send are transactional: a quote is ready, a payment was recorded, documents are needed, your booking status changed. You can turn booking updates off in the app, or revoke notification permission in device settings.

We may occasionally send an announcement about the service or a new package. We do not send third-party marketing, and we do not pass your number to anyone for marketing.

9. Who we share information with

9.1 Service providers (processors)

These providers process data on our instructions, under contract, only to deliver the service:

9.2 Travel fulfilment (independent recipients)

To actually deliver your trip, we pass the traveller details a supplier requires to: airlines and their booking systems, hotels in Makkah, Madinah, and en route, ground transport and ziyarat operators, visa and Umrah processing agents, the Saudi authorities and their pilgrimage platforms, insurers where a policy is included, and correspondent agencies. They handle that data as independent controllers under their own policies and the rules of the destination country.

9.3 Legal and other disclosures

• To banks, auditors, tax authorities, regulators, courts, or law enforcement where required by law or to establish or defend a legal claim.
• To professional advisers under confidentiality obligations.
• If the business is reorganised, merged, or transferred, to the successor entity — with this policy continuing to apply until you are told otherwise.

10. International transfers

We operate from Pakistan; our infrastructure runs on Google Cloud in the United States (region us-central1) and other Google regions; and your travel data necessarily reaches the Kingdom of Saudi Arabia and any country you transit. Data protection laws in those countries differ from those where you live. Where a transfer is subject to the GDPR or UK GDPR, we rely on the European Commission's Standard Contractual Clauses (or the UK Addendum) with our providers, on the adequacy decisions that apply, or — for travel fulfilment — on the transfer being necessary to perform your contract.

11. How long we keep it

12. How we protect your information

• All traffic runs over TLS; stored data is encrypted at rest by Google Cloud.
• Sign-in is by verified phone number — there is no password to leak or reuse.
• Database and storage rules restrict every record to its owner and to authorised staff. Staff access is role-based and limited to what a role needs.
• Firebase App Check rejects requests that do not come from the genuine app, and sensitive operations run server-side with rate limiting.
• Uploads are type-checked and malware-scanned; rejected files are deleted automatically.

Full detail is on the Security page. No system is perfectly secure; if a breach affects your rights, we will notify you and the relevant authority as the law requires.

13. Your rights and choices

In the app you can, at any time:

• update your name, username, photo, language, and contact number;
• add, correct, or remove traveller (Mu'tamirin) records;
• turn booking notifications off;
• revoke location, camera, or photo permissions in device settings;
• delete your account and personal data.

Depending on where you live, you also have the right to:

• Access — get a copy of the personal data we hold about you.
• Rectification — have inaccurate data corrected.
• Erasure — have your data deleted, subject to records we must keep by law.
• Restriction and objection — ask us to pause or stop certain processing, including anything based on legitimate interests.
• Portability — receive your data in a machine-readable format.
• Withdraw consent — for anything based on consent.
• Complain — to your data protection authority.

California residents: we do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not use it for cross-context behavioural advertising. You may exercise access and deletion rights using the contacts below, and we will not discriminate against you for doing so.

To exercise any right, email support@aomadinah.com from — or quoting — the phone number on your account. We may ask you to verify that number before acting, to stop someone else obtaining your data.

14. Delete my data

You can delete your account from inside the app (Settings → Delete account) or here. Enter the phone number on your AoMadinah account; we send an SMS code; once you verify it, deletion runs immediately and cannot be undone.

This form uses Google reCAPTCHA to stop automated abuse of the SMS step. Google processes that verification under its own privacy policy.

15. Children

AoMadinah accounts are for adults arranging travel. We do not knowingly allow anyone under 18 to create an account, and we do not knowingly collect personal data from a child for their own account.

A child's passport and traveller details may appear on a booking made by their parent or guardian — that is submitted by the adult, under their responsibility, solely to arrange the child's travel, and it is deleted along with the traveller record. If you believe a child has created an account, email us and we will delete it.

16. Cookies and local storage

The AoMadinah website uses no advertising or tracking cookies and runs no third-party analytics. The delete-my-data flow on this page sets strictly necessary storage for Firebase sign-in and reCAPTCHA while you use it. The app stores your preferences and cached images on your own device. Full detail: Cookies and local storage.

17. Automated decision-making

We do not make decisions producing legal or similarly significant effects about you by automated means alone. Quotes, document approvals, cancellations, and refunds are decided by our staff. Automated checks — such as file-type validation, malware scanning, App Check attestation, and rate limiting — may block a specific upload or request, and you can always reach a person at support@aomadinah.com to have it reviewed.

18. Third-party links and content

The app and website link to third-party sites — airline and hotel pages, maps, social media, and payment instructions from your bank. Once you follow a link, that site's own privacy policy applies. Blog posts may embed images served from our own storage.

19. Changes to this policy

We update this policy when the app changes or the law requires it. The “Last updated” date above always reflects the current version. For material changes we will give notice in the app or by notification before the change takes effect. Continuing to use AoMadinah after that means you accept the updated policy.

20. Contact and complaints

• Privacy and data requests: support@aomadinah.com
• Operated by: Peer Bukhari Travels (AoMadinah), Pakistan
• Response time: within 30 days of a verified request

If you are not satisfied with our response, you may complain to your local data protection authority — in the EU or UK, the supervisory authority where you live, work, or where the issue arose.

← All legal & privacy pages