Document 1 of 7
Privacy Policy
- Effective
- To be set on publication after legal review
- Last updated
- 19 November 2026
- Version
- 0.9
- Status
- Draft for legal review
GoMusāfir is an app for group journeys such as Hajj, Umrah and other Islamic group travel. It helps a travel organisation and its Journey team guide a group, and helps pilgrims stay together, talk, find their way and keep their memories. This policy explains what personal data we handle, why, who sees it and what rights you have.
In short: pilgrims decide who sees their name, photo, phone number and voice. Privacy rules are enforced on our server, so the app never receives what it may not show. Your Journey team sees your location only between the trip dates. Family at home see only what a pilgrim releases in Memories, never a live location or anything about safety. We do not sell personal data and we show no advertising.
1. Who we are
GoMusāfir (“GoMusāfir”, “we”, “us”) provides the GoMusāfir apps for iPhone and Android, the web pages that belong to them and the website gomusafir.app. Address: Tauber 52, Den Haag, the Netherlands. Chamber of Commerce number: 93396368.
Privacy questions and requests: privacy@gomusafir.app. Help: help@gomusafir.app. General questions: hello@gomusafir.app. Security vulnerabilities: security@gomusafir.app.
2. What this policy covers
This policy covers the GoMusāfir apps, the GoMusāfir web pages (for invitations, trip links, sign-in, account creation and family Memories), our e-mails, our support and the website gomusafir.app. The Cookie Policy describes the website’s browser storage in detail.
It does not cover what an organisation does with data outside GoMusāfir, for example in its own booking systems, or the services of Apple, Google, Stripe or the official Nusuk app, which have their own policies. GoMusāfir is not connected to Nusuk and never books permits.
3. The people whose data we handle
- Organisations: travel organisers and other groups that create a business account, buy boarding passes and run journeys.
- Journey team: the people an organisation adds to run a journey, with the roles Admin, Co-host and Manager.
- Pilgrims: the people who travel on a journey. A pilgrim can be asked to lead a split group as a coordinator.
- Family followers: people who create an account to follow a pilgrim’s journey in Memories, if the pilgrim lets them in.
- People a user tells us about: emergency contacts and travel companions.
- Website visitors and people who contact our support.
4. Who is responsible: controller and processor
A controller decides why and how personal data is used. A processor handles it on a controller’s behalf and only on its instructions.
The organisation is the controller for the pilgrim data it collects and manages for its journey: who travels, bookings and Passport details, the programme, and what its Journey team sees and does on the trip. For that data GoMusāfir is the organisation’s processor under a data processing agreement. You can ask the organisation or us; we pass requests on where needed.
GoMusāfir is the controller for its own processing: accounts and sign-in, organisation accounts and billing, payments, security and fraud prevention, abuse reports that reach us, anonymous crowd and gate information across trips, Memories and follower accounts, our e-mails, support and this website.
| Activity | Controller | Our role |
|---|
| Account, sign-in and app settings | GoMusāfir | Controller |
|---|
| Organisation account, seats, wallet and invoices | GoMusāfir | Controller |
|---|
| Journey participation, bookings and Passports, programme | The organisation | Processor |
|---|
| Location, alerts and SOS within a journey | The organisation | Processor |
|---|
| Voice chat, transcripts and trip chats | The organisation | Processor |
|---|
| Journey Assurance reports and trip feedback | The organisation | Processor |
|---|
| Anonymous crowd levels and gate reports across trips | GoMusāfir | Controller |
|---|
| Memories and family followers | GoMusāfir | Controller |
|---|
| Payments, security, abuse prevention, support, website | GoMusāfir | Controller |
|---|
5. The data we handle
| Category | Examples | Source |
|---|
| Account data | Name, e-mail, phone number, profile photo, app language, woman or man, display name | You, or the organisation that invites you |
|---|
| Sign-in data | Hashed sign-in links, codes, hashed password, sign-in history | You and your device |
|---|
| Organisation data | Company name, logo, country, phone, address, VAT and Chamber of Commerce number, billing e-mail | The organisation |
|---|
| Journey data | Trips, role, approval status, Musafir number, split group, room and bookings | You, the organisation, our systems |
|---|
| Bookings and Passports | Name as in the passport, date of birth, nationality, last 4 passport digits and expiry, visa status and copy, allergies, health and mobility notes | You and the organisation |
|---|
| Contacts you add | Emergency contacts (name, relation, phone), travel companions | You |
|---|
| Location data | Position during the trip dates, route points, distance to the group, battery level | Your device |
|---|
| Communication data | Messages, photos, voice notes, files, polls, reports, voice chat audio, captions and transcripts | You and other users |
|---|
| Memories | Photos, videos, words, place and time, route, followers, hearts and messages | You and your followers |
|---|
| Payment data | Purchases, amounts, invoices, transaction references; no card or bank details | Apple, Stripe, you |
|---|
| Technical data | Device type, operating system, app version, push token, crash reports, IP address, logs | Your device |
|---|
6. Account registration and sign-in
Pilgrims join a journey with a trip link or QR code from their organisation, or through an invitation e-mail. We ask for your name, e-mail address, phone number, an optional photo and whether you are a woman or a man. We use the last point only for privacy choices that depend on it, such as who may see your details and who hears your voice.
Invitations contain a one-time sign-in link, valid for 7 days, usable once and stored only in hashed form. We never send a password by e-mail. Without the app, the link opens a web page where you choose your own password. Face ID or fingerprint sign-in is handled by your phone; we never receive biometric data. We use short e-mail codes for some steps and pause sign-in after repeated failed attempts.
6.1 Organisation and Journey team accounts
An organisation creates a business account with its company name and a business e-mail address; the person who creates it becomes its Admin. Company details and the billing e-mail are used for invoices and to show pilgrims who organises their trip. Journey team members join through an e-mail invitation valid for 7 days and only for the invited address. Journey team accounts also hold the role on each journey and what the Journey team member shows pilgrims.
7. Pilgrim profiles and journey participation
When you join with a trip link, you wait for approval and see nothing of the trip until the Journey team approves you. A waiting person never uses a boarding pass. The Journey team can approve, decline or block a join request for that trip. Once you are on a journey, the organisation sees your profile, approval status, Passport and group. Your account stays yours after the trip: you can still sign in, open Memories and join a new journey.
7.1 Musafir numbers
For each journey you get a new Musafir number, such as “Musafir 12”. If you hide your name, other pilgrims see this number instead, and Deen’s orb instead of your photo. It is a pseudonymous identifier: it does not reveal who you are to other pilgrims, but your Journey team and our systems can link it to you, so it is still protected as personal data. You can also choose a display name, such as a kunya; your Journey team always sees your real name.
8. Visibility and privacy preferences
Every detail starts closed: only your Journey team sees it until you share it. For first name, last name, photo, phone number and e-mail you choose separately: everyone on my trip, only women, only men, only people I choose, or Journey team only. You can show only the first letter of a name, and “Check as” shows what a given person sees of you. The Journey team can lock some settings for a trip; you then see a lock with the reason.
These rules are enforced on our server: another user’s app never receives a detail it may not show, and hidden details cannot be found through search.
Your Journey team always sees what it needs to keep you safe: real name, photo, phone number, e-mail, emergency contacts, Passport and, during the trip, location. Every Journey team role sees the same. Every look by a Journey team member at a detail you hid is logged, and sensitive details require Face ID, fingerprint, phone code or password. Journey team members choose which pilgrims see their own location and phone number.
9. Location
Location lets the Journey team find people, call the group back, count heads at the bus and help in an SOS, and lets Deen show you the way back. The app asks for location permission “Always”, so it works when the app is closed or the screen is locked (background location). You can choose “While using” or turn location off in your phone settings; some safety features then work less well or not at all.
Live location is shared only from the first day of the trip at 00:00 to the last day at 23:59: never before or after, not on the map, in a chat or in the voice chat. If your organisation allows it, you can pause sharing; Deen explains the effect and tells the Journey team. An SOS always shares your location.
Who sees it: your Journey team during the trip; travel companions you confirmed, if “Always share my location with them” is on; other pilgrims only if you accept their request or share live in a chat, until you stop; a split group coordinator only during a live session of that group. Location is never shared through “Show to everyone”, and family never see your live location.
Location also powers features you use: counting Tawaf rounds and Sa’i laps, the nearest gate or Journey team member, and check-in at a meeting point. Your battery level is used for reminders: you at 10%, your Journey team at 15%.
9.1 Crowd levels, gate reports and map search
We combine positions from GoMusāfir users on all trips into anonymous crowd levels. An area is shown only when at least 10 pilgrims from at least 3 trips are in it, counts are rounded, and the raw positions are kept for at most one hour. Gate reports are anonymous; passers-by are counted, never named. Gate photos added by a Journey team member are checked by a person at GoMusāfir before other trips see them. When you search for a place, the map provider receives the search text and a rough position, never your name or trip.
10. SOS and emergencies
When you press SOS, your location, real name, photo and the details that help reach you are shared with the whole Journey team until the SOS is handled, even if location sharing is off. The SOS reaches the Journey team at once, also through Do Not Disturb where the phone allows it. A team member can take it (“I’ll go”), assign a colleague or mark it handled. A travel companion or emergency contact on the same trip is also told and sees your location until the SOS ends. GoMusāfir contacts nobody at home: no SMS, push or e-mail. Your Journey team can call your emergency contacts itself.
SOS events and alerts about drifting, lost pilgrims and low battery are kept in an alert history for the Journey team and counted in the Journey Assurance report.
GoMusāfir is not an emergency service. SOS and alerts depend on your phone, battery, network, permissions and available Journey team members. In an emergency, always contact local emergency services (911 in Saudi Arabia, 112 in the European Union).
11. Voice communication
The voice chat lets the Journey team guide the group with Hold to Talk, up to four open microphones, Mute all and requests to talk. Your voice is streamed live to the people allowed to hear it. You choose who hears your voice; for women, “Hide my voice from men” is on by default. Quiet reading and the prayer quiet window mute the voice chat; urgent messages and SOS still come through.
Live captions and translation in 15 languages turn speech into text for each listener. What is said is written down as a transcript for the Journey team and kept until 30 days after the trip. You are told this once per trip when you join. We do not use your voice to identify you.
11.1 Listen back (temporary audio buffer)
Listen back lets you replay up to the last 10 minutes of the voice chat, for example after a reconnect. For this, voice chat audio is held temporarily and deleted 10 minutes after the voice chat ends. Apart from this buffer and the transcript, no audio is recorded.
12. Chats, chat requests and discovery
Messages holds the trip group chat, your Journey team chat, split group chats, private chats and groups. You can send text, photos, videos, voice notes, documents, polls, places and a live location. Phone numbers are not shared through Messages, and only the Journey team sees who answered what in a poll.
A pilgrim can send another pilgrim one message as a request, which you can accept, decline silently, or block and report. The Journey team sees reports with the reason and the message. You can accept requests from people on this trip or from nobody; your Journey team can always message you. Request notifications never show the message text. Other pilgrims can find you only by your visible name, display name or Musafir number.
All chats of a trip, with their photos, voice notes, files, locations, polls and reports, are deleted for everyone 30 days after the trip ends; Deen reminds you to save photos first. Translations are not stored.
13. Notifications and e-mail
Push notifications tell you about calls back, meeting points, safety alerts and messages. Your phone gives us a push token, which we use through Apple’s or Google’s push service. The lock screen never shows phone numbers, e-mail addresses, coordinates or emergency contacts. Most notification types can be turned off; safety notifications cannot during the trip dates.
Transactional e-mails (invitations, codes, receipts, account notices) never contain passwords, passport numbers, health data or live location. The two digests (the Journey team daily summary and the Memories digest) and any marketing e-mail are sent only if you opt in, and you can opt out at any time. We have no newsletter.
14. Photos, videos and uploads
You can upload a profile photo, share media and documents in chats and add Memories. Journey team members can upload a cover, programme documents, booking lists, gate photos and group album photos. Uploaded documents are checked by content, scanned for viruses, cleaned of macros and scripts and kept in private storage; nobody sees an upload before these checks pass. Photos can contain place and time, which Memories uses to place them on your route; you can change it or show only the city.
15. Bookings and Passports
Your organisation can ask you to fill in a form through a personal link protected with an e-mail code. The standard questions are your name as in your passport, gender, date of birth, nationality, phone, e-mail, emergency contact, who you travel with, the last 4 passport digits and expiry date, visa status and, if asked, a visa copy, allergies, optional health and mobility notes, and a room wish. The organisation can add its own questions. We never ask for your full passport number or a passport scan.
Only you and your Journey team see your answers. The organisation uses them to arrange your journey and is their controller. A visa copy can be kept on your phone, encrypted, until the trip ends, so it works offline.
16. Sensitive data: religion and health
Taking part in a pilgrimage, and content such as duas, may reveal your religious beliefs. Allergies, health and mobility notes and vaccination certificates are health data. The GDPR, the UK GDPR and the Saudi PDPL give this data extra protection.
We process it only to provide the journey you asked for. Health questions are optional unless your organisation needs them for your travel. Where required, this data is processed with your explicit consent, which you can withdraw at any time, or, in an emergency where you cannot consent, to protect your vital interests. We never use it for advertising or profiling.
17. Memories and family access
Memories is your own journey album: photos, videos, words, places, times and your route. It is saved in your GoMusāfir account, not in your phone’s photos, and stays as long as your account exists. For each memory you choose “Family can see this” or “Only me”.
Family can follow your journey only if you share your personal link and let them in. Followers create an account with name, e-mail and password and pay through Stripe. A follower sees a place only after you have left it (500 metres away or 20 minutes after you left), and never your live location, hotel, group, other pilgrims’ names, bookings, Passport, messages, SOS or safety information. The route starts at the airport, never at home. In the group album, other pilgrims’ faces are blurred. When you remove a follower or delete a memory, it disappears for them at once.
Followers can send you a heart and a short message only you see, and receive push notifications and, if they opt in, an e-mail digest. GoMusāfir never contacts your family about your safety.
18. Deen and artificial intelligence
Deen is the face and voice of GoMusāfir Intelligence. Most of what Deen says is fixed text filled with facts from your trip. Everything that decides, counts, measures, routes or filters, such as who sees what, who is drifting or whether an SOS is handled, is plain code with fixed rules.
We use AI services to help Deen answer questions about a trip from its own data, to translate what people write and say, to read a programme or booking list the Journey team uploads (the team checks the result), to summarise anonymous feedback, to read Deen’s fixed lines aloud and to answer help questions about the app. We send only the text or audio needed, without your name, location or trip attached. Deen never gives religious rulings, never writes duas and never reads your private chats, reports or location history. Messages and reminders Deen prepares wait for the organiser’s OK.
19. Journey Assurance and feedback
After a trip, the organisation receives a Journey Assurance report on how it went, such as on-time departures, check-ins, message reach and SOS response times. The anonymous version has no names, Musafir numbers or exact places, and never breaks down groups smaller than 5. The full version, with names, is only for the Journey team, protected, logged and deleted with the trip data. Feedback Deen asks for after the trip is always anonymous.
20. Payments
Pilgrims use GoMusāfir for free. Organisations buy boarding passes with Apple in-app purchase on iPhone, with Stripe on Android, or by company invoice through Stripe. Family followers pay for Memories through Stripe. Apple and Stripe process card and bank details under their own policies; we never see them. We receive what was bought, the amount, the date, a transaction reference and, for invoices, company and billing details.
21. Device information, diagnostics and analytics
To run the app securely and fix problems, we process device type, operating system, app version, language, push token, IP address, sign-in and security logs, and crash reports. We do not use advertising identifiers or third-party advertising or marketing trackers in the apps. We may use aggregated, anonymous statistics on feature use to improve GoMusāfir.
22. The website
The website gomusafir.app is hosted on Google Firebase Hosting. It sets no cookies unless you accept Google Analytics in the cookie banner; then Google Analytics counts visits and clicks for us, without advertising features and without storing IP addresses. It stores your light or dark choice and your Ask Deen conversation in your browser. Ask Deen on the website runs entirely in your browser from the website’s help texts; questions are not sent to a server. Firebase Hosting (Google) receives technical data such as your IP address, as every web host does. See the Cookie Policy.
23. Purposes and legal bases
We do not rely on consent for everything. The table shows each purpose, its data and its legal basis under Article 6 GDPR and the UK GDPR. Where we are processor, the organisation decides the basis; the table shows the one we expect it to use. Under the Saudi PDPL the matching grounds are consent, an agreement with you, a legal obligation, your actual interest when you cannot be reached, and legitimate interests (not for sensitive data).
| Purpose | Data | Legal basis |
|---|
| Create and run your account and sign-in | Account and sign-in data | Contract |
|---|
| Journey team accounts of an organisation | Account data, role | Legitimate interests of the organisation and GoMusāfir in running the team |
|---|
| Organisation account, seats, invoices | Organisation and payment data | Contract; legal obligation for tax records |
|---|
| Journey participation, Passport, programme | Journey and booking data | Organisation: contract with the pilgrim; legal obligation where travel or visa rules apply |
|---|
| Location sharing with the Journey team during the trip | Location, battery | Contract; legitimate interests in group safety |
|---|
| Location sharing with companions, other pilgrims, live share | Location | Consent (your choice, can be stopped at any time) |
|---|
| Drifting, lost and battery alerts | Location, battery | Legitimate interests in group safety; contract |
|---|
| SOS and emergency help | Location, name, photo, contacts, relevant health notes | Contract; legitimate interests; vital interests when you cannot act yourself |
|---|
| Voice chat, captions, translation | Audio stream, speech text | Contract |
|---|
| Voice transcript and Listen back | Transcript, temporary audio | Organisation: legitimate interests in guiding the group, with notice once per trip |
|---|
| Chats, requests, reports | Messages and media | Contract; legitimate interests in safety and abuse handling |
|---|
| Health and religion data | Health notes, journey participation | Explicit consent; vital interests in an emergency |
|---|
| Memories and followers | Memories, follower accounts | Contract; sharing with followers by your choice |
|---|
| Transactional e-mail and push | E-mail address, push token | Contract |
|---|
| Digests and marketing e-mail | E-mail address | Consent |
|---|
| Crowd levels and gate reports | Positions kept at most one hour | Legitimate interests in crowd safety for all users |
|---|
| Journey Assurance and feedback | Trip measures, anonymous feedback | Organisation: legitimate interests in quality and accountability |
|---|
| Security, fraud and access logs | Logs, device data | Legitimate interests; legal obligation to secure data |
|---|
| Diagnostics and improvement | Device data, aggregated statistics | Legitimate interests |
|---|
| Website statistics (Google Analytics on gomusafir.app) | Analytics cookies, pages viewed, clicks, device and approximate location (country or city) | Consent (cookie banner; can be withdrawn at any time) |
|---|
| Payment records | Invoices and receipts | Legal obligation |
|---|
| Support and legal claims | Correspondence, relevant records | Contract; legitimate interests; legal obligation |
|---|
24. Who we share data with
- Your organisation and its Journey team, as described here and limited by your privacy choices.
- Other users, only what you or your settings allow: pilgrims, travel companions, coordinators and Memories followers.
- Service providers who process data for us under contract, listed below by category.
- Apple, Google and Stripe for payments and app store functions, under their own policies.
- Authorities or courts where the law requires it, or where needed to protect someone’s life or safety.
- A successor if GoMusāfir is reorganised or sold, under the same protections.
24.1 Categories of service providers
- Cloud hosting, database and file storage.
- Push notification services of Apple and Google.
- Maps and place search.
- Voice transport, speech-to-text and translation.
- AI services for the uses in section 18.
- E-mail delivery.
- Payments (Apple, Stripe).
- Crash reporting.
- Website hosting and, with your consent, website statistics (Google Firebase Hosting, Google Analytics).
- A mobile data (eSIM) partner, once the eSIM is available.
25. International transfers
GoMusāfir is based in the Netherlands. Pilgrims use the app in Saudi Arabia, and organisations and family may be in the United Kingdom or elsewhere, so data travels between these countries.
When data goes outside the European Economic Area, we use a legal safeguard: an adequacy decision of the European Commission (for example for the United Kingdom, or for US companies certified under the EU-US Data Privacy Framework), or the Commission’s standard contractual clauses with extra measures where needed. Saudi Arabia has no EU adequacy decision; data goes there mainly because you use the app there, to provide the service you asked for. For transfers from Saudi Arabia we follow the PDPL and its transfer regulations; from the United Kingdom, the UK adequacy regulations or the UK International Data Transfer Addendum. You can ask us for a copy of the safeguards.
26. How long we keep data
We keep personal data only as long as needed for its purpose, unless the law requires longer. Periods marked “as designed” come from the app design. All periods are proposed and still to be confirmed.
| Data | Period | Note |
|---|
| Account and profile | Until you delete your account | See Account and Data Deletion |
|---|
| Trip chats, media, polls, reports in chats | 30 days after the trip ends | As designed |
|---|
| Recently deleted chats and trips | Up to 30 days | As designed |
|---|
| Voice chat transcripts | 30 days after the trip ends | As designed |
|---|
| Listen back audio | Deleted 10 minutes after the voice chat ends | As designed |
|---|
| Location history (route points) | 30 days after the trip ends | Proposal; not decided |
|---|
| Raw positions for crowd levels | At most one hour | As designed |
|---|
| Personal pins | 30 days after the trip ends | As designed |
|---|
| SOS records and alert history | 30 days after the trip ends; anonymous counts kept | Proposal |
|---|
| Full Journey Assurance report | Deleted with the trip data | As designed; anonymous report kept |
|---|
| Bookings and Passports | Organisation access ends 30 days after the trip; the pilgrim’s own copy stays with the account | Proposal |
|---|
| Logs of Journey team views of hidden details and exports | 12 months | Proposal |
|---|
| Security and sign-in logs | 6 months | Proposal |
|---|
| Crash reports | 90 days | Proposal |
|---|
| Memories | Until the pilgrim deletes them or the account | As designed |
|---|
| E-mail delivery logs | 30 to 90 days | Proposal |
|---|
| Support correspondence | 2 years after the request is closed | Proposal |
|---|
| Invoices and payment records | 7 years | Dutch fiscal retention obligation |
|---|
27. Deleting your account
Pilgrims can delete their account in the app. If you are on a trip, or it starts within 14 days, deletion is planned for the day after the trip, so your Journey team can still find you in an SOS; you can ask us to delete sooner. Journey team members, organisations and followers can write to privacy@gomusafir.app. We then delete or anonymise the data, except what the law requires us to keep, such as invoices. The Account and Data Deletion page explains each step.
28. Your rights
Under the GDPR and the UK GDPR you can access, correct and delete your data, restrict its use, receive it in a portable format and object to processing based on legitimate interests. You can withdraw consent at any time, without affecting earlier processing. Under the Saudi PDPL you can be informed, access and get a copy of your data, have it corrected or completed, have it destroyed when no longer needed, and withdraw consent.
Many choices are in the app under My profile › Privacy. For other requests, write to privacy@gomusafir.app. We may ask you to confirm your identity. We answer within one month, extendable by two months for complex requests, with the reason. For data your organisation controls, we pass your request on and help it answer.
29. Children
Children often travel with their families. GoMusāfir is not designed for children to use on their own, and a child under 16 may not create their own account. Where a child travels, a parent or guardian decides which of the child’s details are given to the organisation and to GoMusāfir, and gives consent on the child’s behalf where needed. An organisation that adds a child’s details as part of a family booking must have the parent’s or guardian’s agreement. Like every pilgrim’s details, a child’s details start as visible only to the Journey team.
If we learn that a child under 16 created an account without a parent or guardian, we will delete it or ask a parent or guardian to take it over. Parents and guardians can exercise a child’s rights through privacy@gomusafir.app.
30. Security
We protect personal data with technical and organisational measures that fit the risk, including server-side privacy rules, role-based access for the Journey team, logging of Journey team access to hidden details and exports, extra confirmation before sensitive details are shown, hashed sign-in links and passwords, limits on sign-in attempts, checks and virus scans on uploads, short-lived media links and encrypted connections. No system is free of risk. If a breach is likely to put you at risk, we will tell you and the supervisory authority as the law requires. Report security problems to security@gomusafir.app.
31. Automated decisions
GoMusāfir uses fixed rules to send alerts, for example when a pilgrim is more than 25 metres from the nearest Journey team member with the group (drifting) or more than 150 metres away (lost) during a programme item, or when a battery is low. In free time and rest nobody is marked lost. These alerts only inform you and the Journey team, who decide what to do; they have no legal or similarly significant effect. Deen and the AI features make no decisions about you, and Journey Assurance is not used to judge or rank individual pilgrims. We make no decisions based solely on automated processing within the meaning of Article 22 GDPR.
32. Changes to this policy
We may update this policy when GoMusāfir changes or the law requires it. The date of the latest version is shown at the top. We will tell you about important changes in the app or by e-mail before they take effect.
Back to top
Document 2 of 7
Terms of Service
- Effective
- To be set on publication after legal review
- Last updated
- 22 October 2026
- Version
- 0.9
- Status
- Draft for legal review
These terms are the agreement between you and GoMusāfir when you use the GoMusāfir app on iPhone or Android, the GoMusāfir web pages or Memories. They apply to pilgrims, to Journey team members when they use GoMusāfir as a person, and to family and friends who follow a journey in Memories.
In short: your travel organiser decides who joins a journey and runs the trip; GoMusāfir provides the tool. The app is free for pilgrims. SOS and the other safety features help your Journey team reach you, but they are not an emergency service and can fail: in an emergency, always contact the local emergency services. Deen can make mistakes and never gives religious rulings. Your rights as a consumer under the law of the country where you live always stay in place.
Organisations that buy seats and run journeys also agree to our Business Terms and Conditions. Our Privacy Policy explains how we handle personal data.
1. About these terms and acceptance
GoMusāfir is provided by GoMusāfir, Tauber 52, Den Haag, the Netherlands (“GoMusāfir”, “we”, “us”). Chamber of Commerce number: 93396368.
These Terms of Service apply to every use of the GoMusāfir apps, the web pages on gomusafir.app and its subdomains (such as join.gomusafir.app and memories.gomusafir.app) and Memories (together, the “Service”).
You accept these terms when you create an account, when you confirm that you agree to them, or when you first use the Service after we have shown them to you. If you do not agree, please do not use the Service. You can read, save and print these terms at any time.
2. Words we use
- “Organiser”: the travel organisation, group or person that creates a journey in GoMusāfir and buys the seats for it.
- “Journey”: a trip created in GoMusāfir, such as an Umrah or Hajj group trip, with its own dates, group and programme.
- “Journey team”: the people the organiser has added to run a journey. Inside the organisation they have roles (admin, co-host or manager); pilgrims see all of them simply as the Journey team.
- “Pilgrim”: a person who takes part in a journey.
- “Follower”: a family member or friend who follows a pilgrim’s journey in Memories.
- “Deen” and “GoMusāfir Intelligence”: the assistant in the Service and the features behind it, some of which use artificial intelligence.
3. Who can use GoMusāfir
You may create your own account if you are at least 16 years old, or older where the law of your country sets a higher age for using an online service like this one without a parent’s consent.
Children often travel with their family. A child below that age may only use the Service with the consent and under the supervision of a parent or legal guardian, who is responsible for the child’s use and accepts these terms on the child’s behalf. The parent or guardian should travel on the same journey or be known to the Journey team.
To pay for anything in the Service, such as following a journey in Memories or buying seats for your own family journey, you must be an adult under the law of your country or have a parent’s or guardian’s permission.
4. Your account and keeping it safe
You need an account to take part in a journey or to follow one. Give correct details and keep them up to date. You can choose in your privacy settings who sees your name, photo and phone number.
If your organiser invites you by e-mail, you receive a one-time sign-in link. It works once, is valid for 7 days and only for the address it was sent to. Without the app, it opens a web page where you set your own password. We never send a password by e-mail.
Keep your password, your phone and any sign-in codes to yourself, and use the screen lock of your phone. You are responsible for what happens with your account, unless it was used without your permission and you were not careless. Tell us straight away at help@gomusafir.app if you think someone else has used it. You may not share, sell or hand over your account or your place in a journey.
5. Journeys run by an organisation
Most journeys are created and run by a travel organiser. The organiser decides who may join, approves or declines join requests, chooses the Journey team, sets the dates and programme, and decides which privacy rules apply to the trip within the limits the Service allows. GoMusāfir provides the tool.
GoMusāfir is not your travel organiser. We do not sell, arrange or perform flights, hotels, transport, visas, permits or guidance, and we are not a party to your travel contract. Questions about your booking, your programme, your payment for the trip or your rights under package travel law go to your organiser.
Your organiser uses GoMusāfir to collect and manage trip information, such as bookings, passport and visa status and your emergency contact. For that information the organiser decides what is collected and why, and GoMusāfir processes it on the organiser’s behalf, as our Privacy Policy explains.
The Journey team sees what it needs to keep the group safe. Every look by a Journey team member at a detail you have hidden is logged. After the trip your organiser can receive a Journey Assurance report on how the journey went; the version for sharing contains no names.
6. Creating your own family journey
You can also create a journey yourself, for example for your family. You are then its organiser and Journey team and decide who joins. The person who creates a journey takes part free of charge; every other person uses one seat, bought in advance as shown on our pricing page.
If you do this as a private person, you are a consumer. Sections 15 and 25 then also apply to the seats you buy, and the seat rules in our Business Terms and Conditions (such as their 24-month validity) apply to you only as far as they do not reduce your rights as a consumer. You must use the information your group shares with you only for the trip.
7. Joining and taking part in a journey
You join with the trip link, the QR code or the invitation your organiser gives you. Until a Journey team member approves you, you can only message the Journey team and see nothing of the trip, the group or the people in it.
Once approved, you get a Musafir number for the trip, which is shown instead of your name to people you hide your name from. Your organiser can remove or block you from a journey, for example when you were added by mistake. You can leave a journey at any time.
Some features only work during the trip dates: location sharing with the Journey team starts at 00:00 on the first day and stops at 23:59 on the last day. In a split group, the organiser may make a pilgrim coordinator of their group; a coordinator does not see phone numbers, e-mail addresses or emergency contacts.
8. Your responsibilities
When you use GoMusāfir you agree to:
- follow the instructions of your Journey team, the authorities and the staff at the holy sites, even when the app says something different;
- keep your phone charged, carry a power bank where you can, and keep the app, your phone and the permissions you chose up to date;
- give correct information in your profile and in your organiser’s forms;
- respect other people’s privacy and not share their details, photos or voice without their permission;
- not rely on the Service as your only way to stay with your group or get help, and agree with your group on a meeting point in case phones do not work.
9. Voice, messages and translation
The features below are described as designed. Your organiser decides which ones a journey uses.
9.1 Voice chat
You hold a button to talk (Hold to Talk). A few people can talk at once; others wait in line or ask to talk, and the Journey team can mute everyone. You choose who hears your voice. SOS, call back and safety messages are never filtered.
What is said is turned into live captions, which can be translated, and the Journey team of the trip keeps a written record. If you miss part of the voice chat, you can listen back to a short period of recent sound. With Quiet reading on, Deen mutes the voice chat for you; urgent messages and SOS still come through. Our Privacy Policy says how long sound and transcripts are kept.
9.2 Messages
Messages include the trip group, a private thread with your Journey team, private chats, groups, pins, polls, gatherings and documents. Your phone number is not shown to other pilgrims. Another pilgrim can only start a private chat with you by request, which you can accept, decline or block and report. A private chat can be read only by the people in it; if you report it, your Journey team can read it too. Chats of a journey are deleted for everyone some time after the trip, as the Privacy Policy explains, so save what you want to keep.
9.3 Translation and captions
Automatic translation and captions can contain errors, miss words in a noisy place or change the meaning, especially of names, numbers, times and religious terms. Check anything important with your Journey team.
10. Live Location
When you allow it on your phone, GoMusāfir shares your location with the Journey team of your journey, only between the trip dates. It helps them keep the group together, count the group at the bus, call everyone back and show you the way.
Other pilgrims see your location only if you accept their request, choose to share it with the people you travel with, or share it in a chat. Family at home never see your live location.
The app can warn you and the Journey team when you seem to drift away or seem lost. In free time nobody is marked lost, and a phone without a recent position turns grey. Phone location is often wrong, late or missing in crowds, between tall buildings, indoors and with battery saving on. Never assume that someone is safe, or in danger, only because of the map.
Your organiser may decide that location sharing cannot be paused during the trip. If you switch it off on your phone, the Journey team is told and cannot find you on the map. An SOS still shares where you are, if your phone can find its position.
11. SOS and safety features
GoMusāfir is not an emergency service and is never a guaranteed way to get help. It does not contact the police, an ambulance, the authorities at the holy sites or anyone at home. In an emergency, always contact the local emergency services first, for example 911 in Saudi Arabia or 112 in the European Union, and ask people nearby for help.
SOS sends an alert with your location to the whole Journey team of your journey at once. As designed, you hold the SOS button briefly and then have a few seconds to cancel. A Journey team member can take the SOS and come to you. Until the SOS is handled, the Journey team sees what it needs to reach you, such as your real name, photo and location. The person you travel with on the trip may be told too. Nobody at home is contacted.
Whether an SOS or alert arrives, and how fast, depends on:
- your phone, its settings and permissions, including notifications, Do Not Disturb, battery saving and location access;
- your battery: a phone that is off or empty cannot send an SOS;
- mobile data or Wi-Fi, which is often slow or unavailable in large crowds in Makkah, Madinah, Mina and Arafat;
- whether a Journey team member is available, reachable and able to respond;
- the services of Apple, Google, mobile networks and our own servers, which can fail or be delayed.
11.1 Reminders and alerts
The app can remind you when your battery is low and tell the Journey team when it is very low. Battery reminders, drift alerts, headcounts and call backs are aids for the Journey team. They do not replace the Journey team’s attention or your own care for the people around you.
11.2 Using SOS properly
Use SOS only when you need help, never as a test or a joke during the trip. Misuse can delay help to someone else and may lead to suspension of your account. If you pressed it by mistake, cancel it or tell the Journey team that you are okay.
12. Internet, crowds and offline use
Most of GoMusāfir needs internet, including voice chat, Live Location, SOS, Messages and Deen. In Makkah and Madinah, and during the days of Hajj, networks are often overloaded, so calls, messages, alerts and positions can arrive late or not at all.
Where the app supports it, some information is saved on your phone so that you can see it offline, such as parts of your trip details, prayer times and your Passport. Not every feature works offline, and what you see offline may be out of date.
If your organiser has included an eSIM with your seat, the eSIM provider supplies the mobile data under its own terms. An eSIM needs a compatible phone and correct installation, and does not guarantee a connection in a crowd.
13. Availability and changes to the Service
We work to keep GoMusāfir available and reliable, especially during journeys, but we cannot promise that it will always be available or free of errors. Where we can, we plan maintenance outside busy trip moments and announce it in advance.
We may add, change or remove features. If a change takes away a main feature you rely on or makes the Service clearly worse for you, we tell you in advance and you can stop using it; if you paid for something we stop providing, section 25 applies. Features marked beta, test or coming soon may change, work less reliably or be withdrawn. We never present planned features as available.
14. Your content, photos and videos
Your content is everything you add: messages, voice, photos, videos, documents, pins, duas, polls, form answers and memories. You keep all rights to it.
You give GoMusāfir a non-exclusive, worldwide, royalty-free licence to store, copy, process, translate, transcribe, show and send your content, only as far as needed to run and secure the Service for you and the people you share it with, according to your settings. The licence ends when your content is deleted, except for copies we must keep by law or that others already received from you. We do not use your photos or videos for advertising and we do not sell your content.
Only add content you have the right to share. Ask people before you photograph or film them, and respect the rules on photography at the holy sites. As designed, faces of other pilgrims are blurred before followers see a memory; this can fail and does not make sharing other people’s images without permission acceptable.
15. Memories
Memories is a private family page with the photos and moments of a pilgrim’s journey. The pilgrim decides what is released and who may follow. Followers see a place only after the pilgrim has moved on, and never see the live location, the hotel, the group, SOS or safety messages. GoMusāfir never contacts a pilgrim’s family.
Memories is free for pilgrims and organisers. A follower pays €2.99 per follower per journey, including VAT, on the web through Stripe. Following a new journey of the same person is a new payment.
After you pay, the pilgrim decides whether to accept you and can remove you later. By paying you ask us to start the service immediately. Where the law allows, you then lose your right of withdrawal once we have given you access. If the pilgrim declines your request within two weeks, we refund the €2.99. If the pilgrim removes you later, it is not refunded. This does not affect your legal rights if Memories does not work as promised. A technical error, such as a double charge, is always put right.
If Memories is ever sold inside the iPhone app, Apple is the seller of that purchase and Apple’s terms and refund rules apply.
16. Deen and GoMusāfir Intelligence
Deen is the assistant in GoMusāfir. Some of what Deen says is fixed text from the Service; some uses artificial intelligence (GoMusāfir Intelligence), for example to answer questions about your trip and the app, to translate, and to help the Journey team prepare messages from the programme. When an answer comes from artificial intelligence, you are interacting with an AI system, not a person.
Deen answers from your trip’s information and our help texts, but artificial intelligence can be incomplete, out of date or wrong, even when it sounds certain. Check important times, places and meeting points with your Journey team. Messages Deen prepares from the programme wait for the Journey team’s approval before they are sent.
Deen can count the rounds of Tawaf and the laps of Sa'i from your phone’s position and shows prayer times and reminders. Counts and times can be wrong: keep your own count, and follow the adhan and iqamah where you are.
Deen never gives religious rulings; religious questions go to your Journey team. Deen does not read private chats between pilgrims, and artificial intelligence never decides who sees your location or details.
17. Religious guidance
GoMusāfir is a tool for travelling together, not a religious authority. Guides, duas, Umrah and Hajj steps, prayer times, reminders and counts are offered for convenience, may contain errors and may not follow the school of thought or scholars you follow.
For questions about the validity of your worship, the rites of Umrah or Hajj, ihram or anything else of religious importance, follow your Journey team and the scholars you trust. You remain responsible for your own worship. Nothing in the Service is a fatwa or a religious ruling.
18. Third-party services
GoMusāfir works with services of other companies. Their own terms and privacy policies apply, and we are not responsible for how they work.
- Apple and Google: you download the app from the App Store or Google Play under their terms. Purchases through Apple in the iPhone app are sold by Apple, which handles payment, receipts and refunds for them.
- Stripe: payments on Android and on the web are processed by Stripe. GoMusāfir never sees or stores your full card or bank details.
- Nusuk: GoMusāfir is not connected to Nusuk or any Saudi government service and never books permits, visas or appointments. The app can remind you to book in the official Nusuk app; you book and manage permits yourself.
- Maps, notifications, voice and eSIM data come from other providers, listed in our Privacy Policy.
18.1 If you use the iPhone app
These terms are between you and GoMusāfir, not Apple. GoMusāfir, not Apple, is responsible for the app, its maintenance and support, and for handling claims about it, including product liability, legal compliance, consumer protection, privacy and intellectual property claims. You may use the app on Apple devices you own or control as the App Store terms allow. If the app does not conform to a warranty, you may notify Apple, which may refund the app’s purchase price, if any; as far as the law allows, Apple has no other warranty obligation. You confirm that you are not in a country under a United States embargo and not on a United States list of restricted parties. Apple and its subsidiaries are third-party beneficiaries of these terms for the iPhone app and may enforce them.
19. Intellectual property
The Service, including the software, design, Deen and its animation, texts, guides, logos and the name GoMusāfir, belongs to GoMusāfir or our licensors.
We give you a personal, non-exclusive, non-transferable and revocable licence to use the Service for your own journeys under these terms. You may not copy, change, sell, rent or distribute the Service or try to obtain its source code, except where the law allows it and this cannot be excluded. We may use your feedback without paying you, but will not name you without permission.
20. Prohibited activities
You may not use GoMusāfir to:
- break the law, including the laws of Saudi Arabia while you are there, or the rules at the holy sites;
- harass, threaten, insult or discriminate against anyone, or send sexual or hateful content;
- pretend to be someone else, including a Journey team member, an organiser, Deen or GoMusāfir;
- collect or share other people’s details, location, photos or voice without permission, or get around their privacy settings;
- follow or track someone who has not agreed to it;
- press SOS or send reports without a real reason;
- send spam, advertising or fundraising requests the organiser has not allowed;
- upload harmful files, or try to break into, overload or reverse engineer the Service, except good-faith security research reported to us;
- use automated tools to copy the Service, or join a journey you were not invited to, or use someone else’s seat or account.
21. Harassment, abuse and reporting
Nobody should feel unsafe on a journey. You can decline a message request without the other person being told, and block and report someone. A report needs a reason, and your Journey team sees it with the message so that they can act. You cannot block the Journey team, but you can report a Journey team member to the organisation or to us.
You can report content or behaviour that you believe is illegal or breaks these terms to help@gomusafir.app. Say what it is, where it is and why. We handle every report carefully and without undue delay and tell you what we decided. If we restrict your content or account, we tell you what we did and why, unless the law forbids it, and you can ask us to review it. If someone’s life or safety is at risk, we may inform the competent authorities.
If you are in danger, contact the local emergency services and your Journey team straight away. Reports are not an emergency service.
22. Suspension and ending the agreement
You can stop using GoMusāfir at any time and delete your account as described in section 23.
We may suspend or limit your account, remove content or close your account if you seriously or repeatedly break these terms, put the safety or privacy of others at risk, or if the law requires it. Where reasonable, we warn you first and give you the chance to put things right, and we take into account whether you are on a running journey. Your organiser can remove you from their journey; that does not end your GoMusāfir account.
If we stop offering the Service altogether, we tell you at least two months in advance where we can and give you a way to save your own content. Sections 19, 24, 26 and 28 continue after the end.
23. Deleting your account
You can delete your account in the app. What is deleted, what we must keep by law and for how long is explained in the Account and Data Deletion section of the GoMusāfir Legal Centre.
If you ask to delete your account during a journey or shortly before it, the deletion may be planned for the day after the journey ends, so that your Journey team can still find you in an SOS. You can cancel it until then. Deleting your account does not refund a payment, unless the law gives you that right.
24. Our liability
We provide GoMusāfir with reasonable care and skill and are responsible for damage we cause by not meeting these terms or the law. We are not liable for:
- loss that was not foreseeable when you started using the Service or made the payment;
- loss caused by your organiser, the Journey team, other pilgrims, followers or travel providers, who are responsible for their own acts;
- loss caused by events outside our reasonable control, such as overloaded or failing networks, power failures, failures of Apple, Google or other services we do not control, or decisions of authorities;
- loss caused by using the Service against these terms or against the instructions of the Journey team or the authorities;
- loss of business or profit, if you use the Service for a business purpose (the Business Terms and Conditions then apply).
24.1 What we never exclude
Nothing in these terms limits or excludes our liability for death or personal injury caused by our negligence, for damage caused by our intent or gross negligence, for fraud, or for any liability that cannot be limited by law. Nothing in these terms reduces your rights under the mandatory consumer law of the country where you live, including your rights if the Service is not as described or not fit for purpose.
24.2 Safety features
Because SOS, Live Location, alerts, translation and Deen depend on things outside our control (sections 10, 11, 12 and 16), we cannot promise that they always work. This does not reduce our duty to build and run them with reasonable care and skill.
25. Your rights as a consumer
If you use GoMusāfir as a consumer, you have legal rights these terms cannot take away, in the EU (including the Netherlands) and in the United Kingdom. In particular:
- the Service and anything you pay for must be as described and fit for purpose, even when you use the app for free and provide personal data; if not, you can ask us to fix it and, where the law allows, for a price reduction or refund;
- we provide the updates, including security updates, needed to keep the Service in conformity while we supply it;
- for purchases at a distance you normally have 14 days to withdraw without giving a reason; for digital content and services you lose this right only once we have started with your express request and your acknowledgement, which we ask before you pay;
- prices shown to you as a consumer include VAT.
25.1 Withdrawal and complaints
Where you have a right of withdrawal, send a clear statement to help@gomusafir.app within the period, saying what you bought, when, and the name and e-mail address of the account. We refund you within 14 days using the same payment method. Purchases made through Apple are withdrawn and refunded through Apple.
Send complaints to help@gomusafir.app with a description and, for a payment, the date and receipt. We confirm receipt and aim to answer within 14 days, or tell you why we need longer. Complaints about your trip go to your organiser. If we cannot solve a complaint together, you can go to the competent court (section 26) or to an out-of-court dispute body where one is available to you.
26. Governing law and courts
Dutch law applies to these terms. If you are a consumer living in another country, you keep the protection of the mandatory consumer law of that country.
Disputes may be brought before the competent court in the Netherlands. As a consumer you can also always bring a claim in the courts of the country where you live, and we can only bring a claim against you there. If you live in the United Kingdom, you can use the courts of England and Wales, Scotland or Northern Ireland, depending on where you live.
27. Changes to these terms
We may change these terms, for example for new features, changes in the law or more clarity. We tell you about important changes in the app or by e-mail at least 30 days before they take effect. If you do not agree, you can stop using the Service and delete your account before then. Changes required by law or that only benefit you can apply sooner. The version and date at the top show which terms apply.
28. General
If part of these terms is invalid, the rest stays in force and the invalid part is replaced by a valid rule as close as possible to what was meant. Not enforcing a right straight away does not mean we give it up.
We may transfer this agreement to a company that takes over the Service if your rights are not reduced, and we will tell you. You may not transfer your account or this agreement. These terms are written in English; if a translation differs, the version most favourable to you as a consumer applies.
Back to top
Document 3 of 7
Business Terms and Conditions
- Effective
- To be set on publication after legal review
- Last updated
- 22 October 2026
- Version
- 0.9
- Status
- Draft for legal review
These terms apply when a travel organisation, mosque, community or other business uses GoMusāfir to run journeys for its pilgrims. They cover the business account, the Journey team, seats (boarding passes) and payments, and the organisation’s responsibilities, including for the personal data of its pilgrims.
In short: you buy seats in advance, there is no subscription and no recurring billing. Only approved pilgrims use a seat; every Journey team member who joins a trip uses one Light seat, and the organiser who creates the trip is free. Seats stay valid for 24 months, unused seats return to your wallet after a trip, and seats are not refunded in money. You decide who joins and run the trip; GoMusāfir provides the tool and processes pilgrim data on your behalf under our Data Processing Agreement.
1. Scope and acceptance
These Business Terms and Conditions (“Business Terms”) form the agreement between GoMusāfir, Tauber 52, Den Haag, the Netherlands, Chamber of Commerce number 93396368 (“GoMusāfir”, “we”), and the organisation that creates a business account (“Organisation”, “you”).
They apply to the business account, journeys created by the Organisation, seats and all related services. The Data Processing Agreement and the Terms of Service also apply: the Terms of Service govern each person’s individual use of the apps, and the Data Processing Agreement governs our processing of personal data for you. If they conflict, the Data Processing Agreement prevails on data protection, then these Business Terms, then the Terms of Service.
The person who accepts these Business Terms confirms that they are authorised to bind the Organisation. These Business Terms are made for business customers. A private person who creates a journey for their own family is a consumer; the Terms of Service apply to them, and nothing in these Business Terms reduces their consumer rights. General terms of the Organisation do not apply.
2. Definitions
- “Business account”: the account of the Organisation in GoMusāfir, with its company details, Journey team, journeys and wallet.
- “Journey”: a trip created in GoMusāfir, with its own dates, package, pilgrims, Journey team and programme.
- “Journey team”: the people who run journeys for the Organisation, with the role of admin, co-host or manager. Pilgrims see all of them as the Journey team.
- “Pilgrim”: a person who takes part in a journey.
- “Seat” or “boarding pass”: the right for one person to take part in one journey, bought in advance in a package (Light, Plus or Pro).
- “Wallet”: the overview of the seats the Organisation has bought, reserved, used, returned and that have expired.
- “Pilgrim data”: personal data of pilgrims and other people that is processed in GoMusāfir for the Organisation’s journeys.
3. Business account registration
To open a business account, you give the name of the Organisation, its country and your own details, and confirm your e-mail address with a code we send you. The person who creates the business account becomes its first admin.
You keep the company details complete and correct, including the registered name, address, VAT number where you have one, Chamber of Commerce or equivalent registration number and the billing e-mail address. These details appear on invoices and receipts, and you are responsible for their accuracy. Admins and co-hosts can change them.
A business account is for the Organisation only. You may not resell seats or give access to the Service to another organisation without our written consent.
4. Organisation verification
We verify the e-mail address used to create the business account. We may also ask for information to confirm that the Organisation exists and that the person acting for it is authorised, such as a registration number, a VAT number or proof of authority, for example before accepting a company invoice, when there are signs of misuse, or where the law requires it.
We may refuse or suspend a business account if verification is not completed, if the information is false or if we reasonably suspect fraud. Verification by GoMusāfir does not mean that we approve or vouch for the Organisation or its travel services. GoMusāfir does not check travel licences, accreditations or authorisations for Hajj or Umrah; obtaining and keeping them is your responsibility.
5. Authorised administrators
Admins act for the Organisation in GoMusāfir. Everything an admin or co-host does in the business account, such as buying seats, inviting Journey team members, changing company details or deleting a journey, is binding on the Organisation.
You decide who receives the role of admin or co-host, keep the number of admins and co-hosts to what you need, and remove a person’s access as soon as they leave the Organisation or no longer need it. You make sure that every business account has at least one active admin who can be reached. Only an admin can delete the Organisation’s business account.
We may rely on instructions from an admin as instructions from the Organisation. If there is a dispute inside the Organisation about who controls the business account, we may ask for proof of authority and limit changes to the account until it is resolved.
6. Journey team roles and responsibilities
Roles in the Journey team are permissions inside the Organisation. Pilgrims never see the role; they see one Journey team badge. The role of a person can differ per journey. As designed, the roles are:
| Permission | Admin | Co-host | Manager |
|---|
| Run the trip: voice, map, pins, SOS, messages | Yes | Yes | Yes |
|---|
| Invite pilgrims and approve join requests | Yes | Yes | Yes |
|---|
| Change dates, privacy rules, form fields and cover | Yes | Yes | Yes |
|---|
| Buy seats and add places | Yes | Yes | Asks an admin or co-host |
|---|
| Invite Journey team members | Yes | Yes | Asks an admin or co-host |
|---|
| Delete a trip | Yes | Yes | No |
|---|
| Delete the Organisation | Yes | No | No |
|---|
6.1 Coordinators
In a split group, the Journey team can make a pilgrim the coordinator of a group. A coordinator helps their own group, is not a member of the Journey team and does not see phone numbers, e-mail addresses or emergency contacts.
6.2 Your responsibility for the Journey team
You are responsible for the acts and omissions of the people you add to the Journey team and for coordinators you appoint, as for your own. You make sure that they are trained in the use of GoMusāfir, keep their accounts secure, use pilgrim data only for the journey and treat pilgrims with respect. Every time a Journey team member opens a detail a pilgrim has hidden, this is logged.
7. Journey management
You create journeys, choose their package, dates and programme, decide who joins and run them with your Journey team. You decide which features and privacy rules a journey uses within the options the Service offers, for example whether pilgrims may pause location sharing.
You remain the provider of the travel services to your pilgrims and solely responsible for them, including any obligations under package travel law, travel licensing and the rules of the Saudi authorities. GoMusāfir is not a party to your contracts with pilgrims, does not perform travel services and is not connected to Nusuk. GoMusāfir never books permits, visas or appointments.
You check everything that Deen or GoMusāfir Intelligence prepares before it is used. Messages and reminders that Deen prepares from an uploaded programme wait for the approval of the Journey team and are sent only after that approval; you are responsible for their content once approved. AI suggestions, translations and readings of documents can contain errors.
Safety features, such as SOS, drift alerts, headcounts, battery alerts and call backs, support your Journey team but do not replace your own safety plan, staffing, supervision and emergency procedures. You make sure that each journey has enough Journey team members available to respond to SOS alerts, and that pilgrims are told to contact the local emergency services in an emergency.
After a journey, you may receive a Journey Assurance report. The anonymous version is meant for sharing; the full version contains personal data and must be kept confidential and used only under section 16.
8. Pilgrim invitations and approval
You can invite pilgrims with a trip link, a QR code or an invitation by e-mail. An e-mail invitation contains a one-time sign-in link that works once, is valid for 7 days and only for the address it was sent to. GoMusāfir never sends a password by e-mail.
A person who uses a trip link or QR code asks to join. Until a member of the Journey team approves them, they see nothing of the trip, the group or anyone in it, and a waiting person never uses a seat. You may decline or block a request, for the journey or for the whole Organisation.
You invite and approve only people who are travelling with the group, or who have another legitimate reason to be in the journey, and who have been informed under section 16. You are responsible for checking who you approve; a forwarded link can reach people you do not know.
9. Seats: purchase, allocation and consumption
GoMusāfir is paid for with seats bought in advance. There is no subscription and no recurring billing: you only pay when you buy seats.
9.1 Packages and prices
Every package includes every app feature. Prices are per seat, excluding VAT, as shown on gomusafir.app/pricing when you buy. A seat covers one journey of up to 30 days. A journey of 31 to 60 days costs 2 times the package price, and a journey of 61 days or more 3 times.
| Package | Up to 30 days | 31 to 60 days | 61 days or more | Mobile data (eSIM) |
|---|
| Light | €9.97 | €19.94 | €29.91 | Optional: 3 GB for €7.95 per seat, chosen at purchase |
|---|
| Plus | €19.97 | €39.94 | €59.91 | 5 GB included |
|---|
| Pro | €29.97 | €59.94 | €89.91 | 10 GB included |
|---|
9.2 Allocation and consumption
- A journey reserves seats of its package from your wallet. The oldest seats are used first.
- Only approved pilgrims use a seat. A person waiting for approval, or declined, never uses a seat.
- Every Journey team member who joins a journey uses one Light seat. The organiser who creates the journey is free.
- A seat is used when the pilgrim or Journey team member is approved for or joins the journey. Removing an approved pilgrim, or a Journey team member leaving a journey, does not return the seat.
- When a journey ends, every seat it reserved but did not use returns to your wallet with its original expiry date.
9.3 Validity and expiry
Seats are valid for 24 months from the date of purchase or, for a company invoice, from the date the invoice is paid and the seats are credited. As designed, we remind you 60 and 30 days before seats expire. Seats that are not used or reserved by a journey before their expiry date lapse without refund or credit.
9.4 Additional seats
You can buy additional seats at any time, even during a journey, for example to add a place for a pilgrim on the waiting list. When a journey needs more seats than your wallet holds, you only pay for the difference. A manager can ask an admin or co-host to buy seats; the purchase is made by the admin or co-host.
10. eSIM mobile data
Plus and Pro seats include an eSIM with mobile data for the pilgrim; Light seats can include it as an option chosen at purchase. The eSIM data is supplied by a third-party provider under its own terms. It needs a compatible, unlocked phone and correct installation, and coverage and speed depend on the local networks, which are often overloaded in Makkah, Madinah and during Hajj. GoMusāfir does not guarantee coverage or speed.
An eSIM that has been issued or installed cannot be returned. Unused eSIM data is not refunded or carried over to another journey.
11. Payment processing
Seats are paid in advance in one of these ways:
- In the iPhone app, through Apple in-app purchase. Apple is the merchant of record for these purchases: Apple charges the payment, sets the price shown including VAT in your App Store country, issues the receipt and handles refunds under the App Store terms. Company invoices are not available in the iPhone app.
- In the Android app and on the web, by card or another method offered on the Stripe checkout page. Stripe processes the payment. GoMusāfir never sees or stores your full card or bank details.
- By company invoice through Stripe. GoMusāfir sets the amount and any minimum; even one seat is possible. Stripe sends the invoice to your billing e-mail address, and you can pay it with the methods shown on the invoice. Seats are credited to your wallet only after the invoice has been paid.
12. Taxes and invoicing
Prices are in euros and exclude VAT and other taxes, unless stated otherwise. VAT is added on receipts and invoices at the applicable rate. For Apple purchases, Apple calculates and charges the taxes.
Where you are a business established in another EU member state and give us a valid VAT identification number, our invoices may apply the reverse charge mechanism, in which case you account for the VAT. You confirm that the VAT number you give is valid and belongs to the Organisation, and you are responsible for VAT due because it is not.
Company invoices must be paid within the payment term stated on the invoice. Receipts and invoices are available in the business account and are kept as the law requires.
13. Refunds
Seats are never refunded in money. Instead, unused seats return to your wallet after a journey and stay valid for 24 months from purchase. This applies to seats a journey reserved but did not use, including the reserved seats of a journey that is cancelled or deleted. A seat that was used by an approved pilgrim or a Journey team member is not returned, even when that person is removed later or does not travel.
This does not affect technical errors: if you are charged twice, charged the wrong amount or receive fewer seats than you paid for, we correct it, by crediting seats or refunding the amount charged in error. It also does not affect your rights if GoMusāfir fails to provide the Service in breach of these Business Terms, or rights that cannot be excluded by law.
Refunds for purchases through Apple are handled only by Apple, under Apple’s rules.
14. Payment failures
Seats are credited only after we have received payment. If a card payment fails or is reversed, or an invoice is not paid on time, the seats concerned are not credited, or we may remove them from your wallet if they have not been used.
If seats were already used before a payment failed or was reversed, the amount stays due. We may then suspend the purchase of new seats and the creation of new journeys until the amount is paid. We will not interrupt a running journey because of a payment failure without first contacting you and giving you a reasonable chance to pay, so that pilgrims on the journey are not put at risk.
If you dispute a charge with your bank or card issuer without first contacting us, we may treat it as a payment failure until it is resolved.
15. Upgrades
Upgrading seats to a higher package, by paying the difference in price, is coming soon and is not available yet. Until it is available, a journey uses seats of the package chosen for it, and seats cannot be exchanged between packages. When upgrades become available, we will publish how they work and the price difference that applies.
16. Organisation responsibilities for pilgrim data
For pilgrim data, the Organisation is the controller and GoMusāfir is the processor. The Data Processing Agreement applies and forms part of these Business Terms. You are responsible for:
- having a lawful basis under the GDPR, the UK GDPR or other applicable law for collecting and using pilgrim data in GoMusāfir, including a valid condition for special categories of data. Taking part in Hajj or Umrah can reveal a person’s religion, and form fields can contain health information, such as allergies or medical needs;
- informing pilgrims, before they join, that you use GoMusāfir, what you collect through it, why, who in your Journey team sees it and how long you keep it, with a link to your own privacy notice and to ours;
- collecting only what you need for the journey, and the accuracy of the information you or your Journey team enter;
- obtaining the consent of a parent or guardian where you add children to a journey, and making sure a parent or guardian travels with them or is known to you;
- handling requests from pilgrims to exercise their rights about pilgrim data, with our help as set out in the Data Processing Agreement;
- keeping exports, reports and downloads of pilgrim data secure, sharing them only with people who need them, and deleting them when they are no longer needed. Every export is logged.
17. Privacy and data protection
GoMusāfir processes pilgrim data only on your documented instructions, as set out in the Data Processing Agreement, and processes the personal data of the Journey team’s own accounts, of Memories and of payments as a controller under our Privacy Policy.
GoMusāfir enforces visibility rules on its servers, so the app never receives what a user may not see. The Journey team sees a pilgrim’s location only between the trip dates, and in an SOS what it needs until the SOS is handled. Pilgrims choose who sees their name, photo and phone number, and family at home never see live location, the hotel, the group, SOS or safety messages.
We use sub-processors for hosting, voice, maps, notifications, e-mail and payments. The current list and how we inform you of changes are set out in the Data Processing Agreement. Where pilgrim data is transferred outside the European Economic Area or the United Kingdom, we use the safeguards required by law.
18. Security obligations
GoMusāfir takes appropriate technical and organisational measures to protect the Service and pilgrim data, as described in the Data Processing Agreement, and informs you without undue delay after becoming aware of a personal data breach affecting pilgrim data.
You make sure that your Journey team:
- uses strong, unique passwords and the screen lock and biometric options of their phones, and never shares accounts or sign-in codes;
- keeps phones with access to GoMusāfir with them and under control during journeys, and reports a lost or stolen phone straight away;
- does not copy pilgrim data out of GoMusāfir into other tools, chats or spreadsheets unless needed, and then protects and deletes it;
- reports any suspected unauthorised access, misuse or vulnerability to security@gomusafir.app without delay.
19. Acceptable use
You and your Journey team use GoMusāfir only to organise and guide your journeys, in line with the law and the prohibited activities in the Terms of Service. In particular you may not:
- use pilgrim data for marketing, profiling or any purpose other than the journey, unless the pilgrim has separately agreed to it outside GoMusāfir as the law requires;
- track or contact pilgrims through GoMusāfir outside the purpose of the journey, or try to see location outside the trip dates or details a pilgrim has hidden without a real need;
- use GoMusāfir to send advertising or unsolicited messages, or upload content that is unlawful, misleading or harmful;
- share seats, accounts or access with another organisation, or resell the Service;
- misuse SOS, alerts or reports, or interfere with the security or operation of the Service.
20. Deen and GoMusāfir Intelligence for organisations
Deen helps the Journey team, for example by reading an uploaded programme, preparing messages and reminders, translating them into the pilgrims’ languages and summarising anonymous feedback. Artificial intelligence can make mistakes. You review and approve AI output before it is sent to pilgrims and remain responsible for what you approve.
Deen never gives religious rulings and passes religious questions to the Journey team. Any religious guidance you give to pilgrims through GoMusāfir, including duas and guidance you upload, is your own responsibility.
Uploaded files are checked before use and must not contain more personal data than needed. Do not upload passport scans or full passport numbers.
21. Third-party services
GoMusāfir relies on third-party services, including Apple and Google app stores, Stripe for payments, map, notification, voice and e-mail providers, and the eSIM provider. Their own terms apply to your use of them. We are not responsible for their availability or for changes they make, but we choose them with care and remain responsible for our sub-processors under the Data Processing Agreement.
GoMusāfir is not connected to Nusuk or any government system and never books permits, visas or appointments.
22. Intellectual property
GoMusāfir and its licensors keep all rights in the Service, including the software, Deen, the design, texts, guides and reports format. During the agreement you receive a non-exclusive, non-transferable right to use the Service for your journeys under these Business Terms.
You keep all rights in your content, such as your logo, cover images, programmes, duas and messages. You give GoMusāfir a non-exclusive licence to use that content only to provide the Service to you and your pilgrims. You confirm that you have the rights needed for content you upload. We will not use your name or logo in our marketing without your permission.
23. Confidentiality
Each party keeps confidential the non-public information of the other party that it receives under these Business Terms, such as prices agreed outside the published prices, full Journey Assurance reports and security information, and uses it only for the agreement. This does not apply to information that is public, already known, independently developed, or that must be disclosed by law.
24. Availability and support
We work to keep GoMusāfir available and reliable, especially during running journeys, and plan maintenance outside busy trip moments where we can. Unless agreed in writing, we do not offer a service level agreement, guaranteed uptime or guaranteed response times.
Support is available at help@gomusafir.app and through Ask Deen in the app. We answer as soon as we can and give priority to problems that affect a running journey or safety features.
We may change the Service. If a change removes a main feature you rely on or makes the Service materially worse for you, we inform you in advance.
25. Suspension and termination
The agreement continues as long as the Organisation has a business account. You can end it at any time by deleting the business account; this is not possible while journeys with pilgrims are running or coming up, because their pilgrims rely on them.
We may suspend or limit a business account, or end the agreement with immediate effect, if you materially breach these Business Terms or the Data Processing Agreement and do not remedy the breach within a reasonable period after our notice, if you misuse pilgrim data or put pilgrims at risk, if the law requires it, or if you become insolvent. Where possible, we avoid interrupting a running journey and contact you first.
We may end the agreement for convenience with at least three months’ notice. We then deal with unused, unexpired seats as set out in section 13.
When the agreement ends, the Data Processing Agreement sets out what happens to pilgrim data. Each pilgrim keeps their own GoMusāfir account, their personal Memories and their Passport. Before deleting the business account, admins can download the receipts, invoices and reports available in it. Receipts and invoices are kept as the law requires.
26. Liability
GoMusāfir is liable to the Organisation only for direct damage caused by an attributable failure to perform these Business Terms. GoMusāfir is not liable for indirect or consequential damage, including loss of profit, revenue, goodwill, business or data, or damage from claims of pilgrims about the travel services you provide.
The total liability of GoMusāfir under or in connection with the agreement, per event or series of connected events, is limited to the amounts the Organisation paid to GoMusāfir for seats in the 12 months before the event that caused the damage.
These limitations do not apply to damage caused by the intent or gross negligence of GoMusāfir’s management, to death or personal injury caused by negligence, or to liability that cannot be limited by law. Any claim must be notified in writing within 12 months after the Organisation became aware or could reasonably have become aware of the damage.
Given the nature of the safety features (see the Terms of Service, sections 10 to 12), GoMusāfir does not guarantee that SOS, location, alerts or notifications always arrive and is not liable for the consequences of their failure where that failure is caused by devices, batteries, connectivity, permissions or the availability of responders.
26.1 Indemnity
The Organisation indemnifies GoMusāfir against claims of third parties, including pilgrims and authorities, arising from the Organisation’s travel services, its breach of these Business Terms or the Data Processing Agreement, or its unlawful processing of pilgrim data, including reasonable legal costs.
26.2 Force majeure
Neither party is liable for a failure caused by circumstances beyond its reasonable control, such as overloaded or failing mobile networks, power or internet failures, failures of third-party platforms, government measures, war, epidemics or natural disasters. Payment obligations for seats already used are not suspended by force majeure.
27. Governing law and disputes
Dutch law applies to these Business Terms and the agreement. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
Disputes are submitted exclusively to the competent court in The Hague, the Netherlands, unless mandatory law requires otherwise. Before going to court, the parties try to resolve a dispute through discussion between authorised representatives.
28. Modifications
We may change these Business Terms. We inform admins by e-mail or in the app at least 30 days before an important change takes effect. If you do not accept the change, you can end the agreement before it takes effect; unused seats then follow section 13. Changes to published prices do not affect seats already bought. Changes required by law, or that only benefit you, can apply sooner. The version and date at the top show which terms apply.
29. General
If a provision is invalid, the rest stays in force and the parties replace it with a valid provision as close as possible to the original intent. Not enforcing a right does not waive it. You may not transfer the agreement without our written consent; we may transfer it to a company that takes over the Service, after informing you.
Notices to GoMusāfir are sent to legal@gomusafir.app, and to the Organisation to the e-mail address of its admins or its billing e-mail. These Business Terms are written in English; if a translation differs, the English version prevails.
Back to top
Document 4 of 7
Cookie Policy
- Effective
- To be set on publication after legal review
- Last updated
- 19 November 2026
- Version
- 0.9
- Status
- Draft for legal review
We keep the website gomusafir.app light and respectful of your privacy. It keeps a few small items in your browser so the site works as you expect, and everything it shows, including fonts, images and videos, comes from gomusafir.app itself. There is no advertising and there are no marketing pixels. We use Google Analytics only if you click Accept in the cookie banner; if you decline or make no choice, it stays off and no analytics cookies are set. This page lists everything, item by item.
1. About this policy
This Cookie Policy applies to the website gomusafir.app, provided by GoMusāfir, Tauber 52, Den Haag, the Netherlands. It explains which cookies and similar technologies the website uses, why, and what choices you have. It is based on a check of the website made on 22 October 2026.
The GoMusāfir apps for iPhone and Android, and the GoMusāfir web pages for invitations, sign-in and family Memories, are covered by our Privacy Policy.
2. Cookies and similar technologies
A cookie is a small text file that a website stores in your browser. Websites can also store information in the browser with local storage, which stays until you clear it, and session storage, which disappears when you close the tab. When a page loads a file such as a font, script or video from another service, that service receives technical data from your browser, such as your IP address. The law treats all of these in a similar way, so we describe them all here.
3. What our website stores in your browser
The website’s own code sets no cookies. It uses five browser storage items. They contain no name, e-mail address or other details about you, they are never sent to us, and they are not used to track you.
| Name | Type | Purpose | How long | Category |
|---|
| gm-theme | Local storage | Remembers whether you chose the light or dark look | Until you clear your browser data | Strictly necessary (a preference you set) |
|---|
| gm-deen-hi | Session storage | Remembers that Deen already said hello during this visit, so he does not greet you again | Until you close the tab | Strictly necessary |
|---|
| gm-deen | Session storage | Keeps your Ask Deen conversation in this tab while you browse | Until you close the tab | Strictly necessary |
|---|
| gm-cur | Local storage | Remembers the currency you picked for the prices (euro, pound, dollar or riyal) | Until you clear your browser data | Strictly necessary (a preference you set) |
|---|
| gm-consent | Local storage | Remembers whether you accepted or declined Google Analytics, and when | 12 months, then we ask again | Strictly necessary |
|---|
4. Ask Deen on the website
Ask Deen on the website runs entirely in your browser. It answers from the website’s own help texts. Your questions are not sent to a server, not to us and not to an AI service. The conversation is kept only in the session storage item gm-deen and disappears when you close the tab.
5. Hosting
Google Firebase Hosting serves gomusafir.app: your browser loads the pages, fonts, images and videos from there. Like every web host, it receives the technical data your browser always sends, such as your IP address, browser type and the page requested, and uses it to deliver and protect the website. The website does not load files from any other service.
| Service | Domains | What it does | Category |
|---|
| Google Firebase Hosting (Google) | gomusafir.app | Hosts the website and serves its pages, fonts, images and videos | Strictly necessary |
|---|
| Google Analytics 4 (Google), only after you click Accept | googletagmanager.com, google-analytics.com | Counts visits, page views, scrolling and clicks on buttons such as Start free and the app stores, so we can see which pages help | Analytics (needs your consent) |
|---|
5.1 Google Analytics, only with your consent
When you click Accept, the website loads Google Analytics 4. It sets the cookies _ga and _ga_S1L5E96487, which contain a random number to recognise your browser on later visits, and keeps them for 13 months. We use the statistics only to understand and improve the website. We do not use advertising features, Google signals or ad personalisation, we do not send names, e-mail addresses or what you type in Ask Deen, and we keep the data in Google Analytics for 14 months.
Google Analytics 4 does not store IP addresses. Google (Google Ireland Limited, with Google LLC as subprocessor) processes the data for us; where data goes to the United States, Google relies on the EU-U.S. Data Privacy Framework and standard contractual clauses.
If you click Decline, or make no choice, Google Analytics is never loaded. You can change your choice at any time with Cookie settings at the bottom of every page; when you withdraw consent we delete the Analytics cookies on gomusafir.app.
6. What we do not use
- No advertising cookies or advertising networks.
- No marketing pixels, such as those of social networks.
- No tracking across websites, and no Google Analytics unless you accept it.
- No embedded social media buttons that track you.
7. Strictly necessary and optional technologies
Strictly necessary technologies are needed to provide the website you ask for, or to remember a choice you make, such as light or dark. The law allows them without consent. Optional technologies, such as advertising, marketing pixels or analytics that affect your privacy, need your consent first.
Today the website uses strictly necessary technologies and, only when you accept it, Google Analytics. The legal basis for the related processing of technical data, such as your IP address, is our legitimate interest in running a secure, working website.
8. Consent
On your first visit the website asks whether we may use Google Analytics. Analytics stays off until you click Accept, Decline is just as easy, and nothing changes in how the website works if you decline. You can change your choice at any time with Cookie settings at the bottom of every page. We ask again after 12 months. We never use advertising or marketing pixels.
9. How you can control this
Use Cookie settings at the bottom of every page to accept or decline Google Analytics, or to withdraw your consent; we then delete the Analytics cookies. You can also delete local and session storage and block cookies in your browser settings. Session storage is deleted when you close the tab. If you delete gm-theme, the website shows its default look again; if you delete gm-consent, we ask for your choice again. If you block gomusafir.app itself, the website will not load.
10. Changes
We will update this policy whenever the website’s cookies, storage or services change, and show the date of the latest version at the top.
Back to top
Document 5 of 7
Data Processing Agreement
- Effective
- To be set on publication after legal review
- Last updated
- 22 October 2026
- Version
- 0.9
- Status
- Draft for legal review
This agreement explains how GoMusāfir processes personal data on behalf of a travel organisation that uses GoMusāfir for Hajj, Umrah and other Islamic group journeys. The organisation decides why and how the data of its pilgrims and Journey team is used. GoMusāfir provides the apps and servers and follows the organisation’s instructions.
It meets Article 28 of the GDPR and of the UK GDPR, includes a note on the Saudi Personal Data Protection Law (PDPL) and forms part of the GoMusāfir Business Terms. Annexes A to C describe the processing, the security measures and the subprocessors.
1. Parties and definitions
This agreement is between the organisation that creates a GoMusāfir organisation account to run journeys (the “Organisation”, controller) and GoMusāfir, Tauber 52, Den Haag, the Netherlands, Chamber of Commerce number: 93396368 (“GoMusāfir”, processor).
Terms such as controller, processor, data subject, personal data, processing, personal data breach and special categories of personal data have the meaning given in the GDPR, or the equivalent meaning under the UK GDPR or the PDPL where those apply. In addition:
- “Applicable Data Protection Law”: the GDPR, the Dutch GDPR Implementation Act, the UK GDPR with the UK Data Protection Act 2018, the PDPL with its implementing regulations, and any other data protection law that applies to the processing.
- “Business Terms”: the GoMusāfir Business Terms for organisations, including the purchase of boarding passes (seats).
- “Service”: the GoMusāfir apps for iPhone and Android, the related web pages for invitations, joining and sign in, and the backend.
- “Journey” or “trip”: a journey the Organisation creates in the Service, with its dates, programme, pilgrims and Journey team.
- “Journey team”: the people the Organisation authorises to run its journeys, in the roles Admin, Co-host and Manager.
- “Pilgrim”: a person who takes part in a journey. A “Coordinator” is a pilgrim who leads a split group and is treated as a pilgrim for privacy.
- “Organisation Data”: the personal data GoMusāfir processes on behalf of the Organisation, as described in Annex A.
- “SCCs”: the standard contractual clauses in Commission Implementing Decision (EU) 2021/914. “UK Transfer Mechanism”: the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the SCCs.
2. Roles of the parties
For Organisation Data, the Organisation is the controller and GoMusāfir is the processor. The Organisation decides which journeys it runs, whom it invites, which details it asks for and which role each Journey team member has.
Outside this agreement, GoMusāfir is an independent controller for: user accounts as such (sign-in details and the profile a person keeps across journeys), Memories and family followers, the billing relationship with the Organisation, the website gomusafir.app, security logs kept for its own protection, and anonymous or aggregated information such as crowd levels and gate reports combined from several trips. GoMusāfir’s Privacy Policy covers that processing.
When the Organisation deletes a trip and lets pilgrims keep their own Memories and GoMusāfir Passport, GoMusāfir holds that information from then on as controller, at the pilgrim’s request.
3. Scope, duration and relationship with the Business Terms
This agreement applies to all processing of Organisation Data in connection with the Service. It forms part of the Business Terms and becomes binding together with them when the Organisation creates its organisation account. A version both parties can sign is available on request at legal@gomusafir.app.
It stays in force as long as GoMusāfir processes Organisation Data, including the return and deletion period in section 16. On data protection, this agreement prevails over the Business Terms; the SCCs or a UK Transfer Mechanism, where they apply, prevail over this agreement.
4. Nature and purposes of the processing
GoMusāfir processes Organisation Data only to provide the Service, which means:
- running journeys: invitations, join requests, approval, seats, rooms, buses and split groups;
- the pilgrim form and Bookings and Passports, including fields only the Journey team sees;
- keeping the group together: live location between the trip dates, drifting and lost alerts, headcounts, Call everyone back, Show the way and battery reminders;
- safety: SOS alerts to the whole Journey team, assigning and handling, the alert history and the Journey Assurance report;
- communication: trip and private chats, pins, polls, gatherings, documents, voice chat with live captions and translation, and messages Deen prepares for the Journey team to approve;
- reading uploaded programmes so the Journey team can check them before publishing;
- support, security and integrity of the Service for these purposes, and deletion or return of the data.
4.1 Nature
The processing is automated: collection, storage, organisation, consultation, transmission to authorised users, translation, captioning, alerting, restriction and erasure, on servers used by GoMusāfir and on users’ devices. Captions, translation and programme reading may use artificial intelligence. No automated decision with legal or similarly significant effect is made about pilgrims. Deen never gives religious rulings and never decides who sees whose location, who is lost or whether an SOS is handled.
5. Data subjects and categories of personal data
5.1 Data subjects
- Pilgrims, including invited, waiting, approved, blocked and removed people, and children travelling with their family.
- Journey team members and coordinators.
- Emergency contacts and travel companions recorded by a pilgrim or the Journey team.
- Family followers, only where the Organisation is involved in their data (for example a follower recorded as an emergency contact). Memories itself is a GoMusāfir controller service.
- Other people named in messages or uploaded documents.
5.2 Categories of personal data
- Identity and contact: name (as in the passport where asked), photo, gender (woman or man, used for privacy choices), date of birth, nationality, Musafir number, e-mail, phone, language.
- Passport and visa: the last four digits and expiry date of the passport (never a full number or scan), visa status and, if asked, a visa copy.
- Bookings and form answers: flights, hotels, rooms, roommates, bus, meals, transfers, travel companions, answers to the Organisation’s questions and uploads.
- Location: live position during the trip dates, shared locations, SOS location, route during the trip, check-ins.
- Voice: live audio, captions, transcripts, requests to talk.
- Messages and media: chats, voice notes, photos, files, polls, pins.
- Safety: SOS events, drifting, lost and low battery alerts, assignments and handling times.
- Device and logs: device type, app version, push token, battery level, connectivity, crash reports, logs of looks at hidden details and of exports.
5.3 Special categories
Participation in Hajj or Umrah can reveal religious belief, a special category under Article 9 GDPR. The Organisation must treat Organisation Data as potentially revealing religious belief and have a valid condition for it.
The standard form includes allergies and an optional health and mobility field, and the Organisation can add questions such as wheelchair needs. These are health data. The Organisation asks only for what the journey needs and secures a valid Article 9 condition, such as explicit consent.
5.4 Children
The Organisation is responsible for processing children’s data lawfully, including consent from a parent or guardian where required, and for deciding whether a child has their own account.
6. Documented instructions
GoMusāfir processes Organisation Data only on the Organisation’s documented instructions, including for transfers to third countries, unless EU or Member State law requires otherwise; GoMusāfir then informs the Organisation first, unless that law forbids it.
The instructions are this agreement, the Business Terms and the settings and actions the Organisation and its Journey team choose in the Service, such as trip dates, privacy defaults, form fields, approving messages and deleting a trip. Other instructions must be in writing and fit the way the Service works; changes to the Service may be declined or offered at an agreed cost.
GoMusāfir informs the Organisation without delay if an instruction in its opinion infringes Applicable Data Protection Law, and may suspend it until confirmed or changed. GoMusāfir does not sell Organisation Data, does not use it for advertising and does not use it to train general AI models.
7. Obligations of the Organisation
- Have a lawful basis, including an Article 9 condition, and enter accurate data.
- Inform pilgrims and other data subjects about the processing and that GoMusāfir is its processor.
- Give Journey team members the lowest role that fits and remove them when access is no longer needed.
- Handle exports with care: a pilgrim list or full report downloaded from the Service leaves GoMusāfir’s control and is the Organisation’s responsibility.
- Not use the Service for full passport numbers, passport scans, payment card data or detailed medical records.
- Tell pilgrims that SOS and safety features depend on device, battery, connectivity, permissions and available responders, are not an emergency service, and that in an emergency they should contact local emergency services.
8. Confidentiality
GoMusāfir ensures that everyone it authorises to process Organisation Data is bound by confidentiality, and gives its personnel access only where needed for the purposes in section 4, such as a support request from the Organisation or a security investigation.
9. Security of processing
Taking into account the state of the art, the costs, the nature, scope, context and purposes of the processing and the risks for pilgrims, GoMusāfir implements appropriate technical and organisational measures under Article 32 GDPR, described in Annex B. The risk is higher than for an ordinary travel app because the Service processes location in crowded places, data that may reveal religious belief, health answers and passport details. GoMusāfir may update Annex B if the overall level of protection does not decrease.
10. Subprocessors
The Organisation gives GoMusāfir general written authorisation to engage subprocessors. Annex C lists the categories; GoMusāfir will publish a list with names and locations before the Service goes live.
GoMusāfir informs the Organisation at least 30 days before adding or replacing a subprocessor, by e-mail to its admins or in the Service. The Organisation may object on reasonable data protection grounds within that period. If the parties find no solution, the Organisation may end the Business Terms for the affected part of the Service without penalty.
GoMusāfir binds every subprocessor by written contract to obligations at least as protective as this agreement and remains fully liable for them. Apple, Google and Stripe, as app stores, platforms and payment providers acting as independent controllers, are not subprocessors for Organisation Data.
11. International transfers
GoMusāfir transfers Organisation Data outside the European Economic Area only in line with Chapter V GDPR: to a country with an adequacy decision (such as a provider certified under the EU-US Data Privacy Framework), or with the SCCs (module three, processor to processor) and supplementary measures where needed.
11.1 United Kingdom
For an Organisation subject to the UK GDPR, transfers to GoMusāfir rely on the UK adequacy regulations for the EEA. Onward transfers to third countries use a UK Transfer Mechanism where needed.
11.2 Organisations elsewhere
For an Organisation outside the EEA and the UK, for example in Saudi Arabia, the parties use the SCCs (module four, processor to controller) where required.
11.3 Saudi Arabia
Most location, voice, SOS and chat data is created while pilgrims are in Saudi Arabia and is sent from their devices to the servers used by GoMusāfir. The PDPL, supervised by the Saudi Data and Artificial Intelligence Authority (SDAIA), may apply, in particular when the Organisation is established in Saudi Arabia or the processing concerns persons in the Kingdom. Where it applies, the parties cooperate on its transfer rules, data subject rights and incident notification.
12. Assistance with data subject requests
Taking into account the nature of the processing, GoMusāfir assists the Organisation with appropriate measures in answering requests for access, rectification, erasure, restriction, portability and objection.
Many requests can be handled in the Service: pilgrims change their privacy choices and details and can delete their account. Deletion during a running journey takes effect the day after it ends, so the Journey team can still find the pilgrim in an SOS; the pilgrim sees the date and can cancel.
GoMusāfir forwards requests about Organisation Data to the Organisation without undue delay and only confirms receipt, unless instructed otherwise or required by law. Help beyond the tools in the Service may be charged at a reasonable fee agreed in advance.
13. Personal data breaches
GoMusāfir notifies the Organisation without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Organisation Data, by e-mail to its admins and where possible in the Service.
The notice describes, as far as known: the nature of the breach, the categories and approximate number of people and records, a contact point, the likely consequences and the measures taken or proposed. Missing information follows in phases without undue delay.
GoMusāfir contains and investigates the breach, documents it and assists the Organisation, which decides on notifying the supervisory authority and data subjects. A notice is not an admission of fault.
14. Data protection impact assessment
A DPIA under Article 35 GDPR is likely to be required: the Service monitors pilgrims’ location, may reveal religious belief, may hold health data, concerns vulnerable people such as elderly pilgrims and children, and uses new technology such as captions, translation and automated alerts. GoMusāfir assists the Organisation with its DPIA and any prior consultation under Article 36, and provides a description of the Service’s privacy design and security measures.
15. Audits and information
GoMusāfir makes available the information needed to demonstrate compliance with Article 28 GDPR, such as its security measures and subprocessor list, and allows for and contributes to audits by the Organisation or an independent auditor it mandates, on these terms:
- the Organisation first relies on the information provided and audits only if it is not sufficient;
- at least 30 days’ written notice with a proposed scope, and no more than once in 12 months unless a breach or a supervisory authority justifies more;
- during business hours, without access to other organisations’ data or trade secrets, by an auditor bound by confidentiality who is not a competitor;
- each party bears its own costs, unless the audit shows a material breach by GoMusāfir, which then bears the reasonable audit costs.
16. Return and deletion
As designed, a deleted trip can be restored by admins and co-hosts for 30 days and is then deleted for good. When deleting, the Organisation chooses whether pilgrims keep their own Memories and GoMusāfir Passport. Chats of a trip are deleted 30 days after the trip ends and personal trip data is deleted with the trip.
After the Business Terms end, the Organisation may export what it needs with the Service’s tools for 30 days. GoMusāfir then deletes the remaining Organisation Data unless EU or Member State law requires storage. Backup copies are deleted as the backups expire and are not restored except to recover from an incident. GoMusāfir confirms deletion in writing on request.
Data GoMusāfir holds as controller, such as a pilgrim’s own account and payment records the law requires, follows the Privacy Policy.
17. Term and termination
This agreement ends when GoMusāfir no longer processes Organisation Data and cannot be ended separately from the Business Terms. If GoMusāfir materially breaches it and does not cure the breach within a reasonable period after notice, the Organisation may end the Business Terms under their termination clause. Confidentiality, deletion, liability and applicable law survive.
18. Liability
Liability under this agreement is subject to the limitations in the Business Terms, to the extent Applicable Data Protection Law allows. Nothing limits liability towards data subjects under Article 82 GDPR or liability that cannot be limited by law.
19. Applicable law and jurisdiction
Dutch law applies. Disputes go to the competent court in The Hague, unless mandatory law provides otherwise. The SCCs and UK Transfer Mechanisms keep their own law and jurisdiction clauses.
20. Changes and notices
GoMusāfir may update this agreement when the law, regulatory guidance or the Service changes, with at least 30 days’ notice of material changes. Changes that reduce protection need the Organisation’s agreement. Notices go to legal@gomusafir.app, or security@gomusafir.app for incidents, and to the Organisation’s admins by e-mail.
Annex A. Processing description
“As designed” means taken from the product design and still to be checked in the built product.
| Item | Description and retention |
|---|
| Subject matter and duration | Provision of the Service under the Business Terms, for their term plus the return and deletion period of section 16. |
|---|
| Purposes | As in section 4. |
|---|
| Data subjects | As in section 5.1. |
|---|
| Identity and contact | Retention: with the trip; account fields as long as the account exists. |
|---|
| Passport and visa | Last four digits, expiry, visa status, visa copy if asked. Retention: with the trip unless the pilgrim keeps the Passport. |
|---|
| Bookings and form answers | Retention: with the trip. |
|---|
| Health data (special category) | Allergies, health and mobility, custom health questions. Retention: with the trip. |
|---|
| Location | Live only between the trip dates; SOS location until handled. Location history retention. |
|---|
| Voice | Transcripts. A server replay buffer of about 10 minutes is described in the design; otherwise audio is not kept. |
|---|
| Messages and media | Deleted 30 days after the trip ends (as designed). |
|---|
| Safety data | Names deleted with the trip data; Journey Assurance keeps counts only (as designed). |
|---|
| Special categories | Religious belief can be inferred; health data possible. |
|---|
| Subprocessors and transfers | Annex C and section 11; locations. |
|---|
Annex B. Technical and organisational measures
B.1 Measures in the design of the Service
- Visibility enforced on the server: a device does not receive details it may not show; Journey-team-only content is filtered on the server.
- Role-based permissions within one organisation; buying seats, inviting team members and deleting trips or the organisation are limited to higher roles; coordinators never see phone numbers, e-mail or emergency contacts.
- Organisation and journey separation: team members see only their own organisation’s journeys and pilgrims.
- Sensitive pilgrim details (passport, phone, medical, emergency contact) are masked until the team member confirms with Face ID, fingerprint or password, for 5 minutes on that device.
- Every look at a detail a pilgrim hides is logged (viewer, pilgrim, field, context), as are exports and full report downloads.
- One-time sign-in links are stored hashed, work once and expire after 7 days; passwords are never sent by e-mail and are stored hashed.
- Sign-in pauses for 15 minutes after 5 wrong passwords; e-mail codes have 6 digits, last 10 minutes and allow 5 tries; a password change signs out other devices.
- Location only between the trip dates; other pilgrims only by accepted, time-limited request or share; never to family; crowd data only for 10 pilgrims from 3 trips, raw crowd positions an hour at most.
- Only the last four passport digits and expiry are asked; no scans.
- No passwords, passport numbers, health data or live location in e-mail or on the lock screen; reports are links behind sign-in.
- Uploads limited in type and size, scanned for viruses and hidden code; macro files refused.
- During screen recording, names and photos are hidden and voice audio is excluded where the system allows.
- Translations are not stored; no names, locations or trips are sent to an AI service for translation.
- Card and bank details are handled by Apple or Stripe, never by GoMusāfir.
B.2 Proposed measures
- TLS encryption in transit for all connections.
- Encryption at rest where provided by the infrastructure provider.
- Separate production and test environments, without production personal data in tests.
- Least-privilege staff access with multi-factor authentication and logging.
- Managed secrets, rotated on staff changes or incidents.
- Regular, tested backups with a defined retention period.
- Security monitoring with alerts, a written incident response plan and a breach register.
- Dependency updates, review of access rule changes and a penetration test before launch.
- A disclosure channel at security@gomusafir.app, staff confidentiality and privacy training, and subprocessor due diligence.
Annex C. Subprocessors
No provider is final. Before publication each row needs the provider, its role, the location of processing and the transfer mechanism.
| Category | Purpose | Provider | Location |
|---|
| Cloud hosting, database and backups | Running the Service and storing Organisation Data | To confirm | To confirm |
|---|
| File and media storage | Photos, voice notes, documents, programmes | To confirm | To confirm |
|---|
| Real-time voice | Live audio in the voice chat | To confirm | To confirm |
|---|
| Speech-to-text | Live captions and transcripts | To confirm | To confirm |
|---|
| Translation and AI language services | Translation in 15 languages, programme reading, Deen’s answers from the trip | To confirm | To confirm |
|---|
| Maps and places | Maps and place search outside GoMusāfir’s own holy places layer | To confirm (prototypes use Google Maps) | To confirm |
|---|
| Push notifications | Alerts, SOS and messages to devices | To confirm (Apple and Google platform services) | To confirm |
|---|
| Transactional e-mail | Invitations, sign-in links, codes, service e-mail | To confirm (candidates: Postmark, Amazon SES or Resend) | To confirm |
|---|
| Upload scanning | Virus and hidden code checks | To confirm | To confirm |
|---|
| Crash reporting | Finding app errors | To confirm | To confirm |
|---|
| eSIM | eSIM data in Plus and Pro, if pilgrim data is shared | To confirm | To confirm |
|---|
| Support tools | Support requests from the Organisation | To confirm | To confirm |
|---|
Back to top
Document 6 of 7
Account and Data Deletion
- Effective
- To be set on publication after legal review
- Last updated
- 22 October 2026
- Version
- 0.9
- Status
- Draft for legal review
This page explains how to delete your GoMusāfir account and your data, for the GoMusāfir apps on iPhone and Android, the GoMusāfir web pages and Memories. It applies to pilgrims, Journey team members, organisations and family followers.
You can always ask us to delete your data. When we delete an account, we delete or anonymise its personal data, and keep only what the law requires us to keep, for as long as it requires.
1. How to request deletion
App: GoMusāfir, by GoMusāfir, on the App Store and Google Play. You do not need the app installed to request deletion.
- Pilgrims: open GoMusāfir, go to My profile, then Delete my account, type DELETE and confirm. You can also use the e-mail route below.
- Journey team members, organisations and family followers, or anyone who cannot use the app: send an e-mail to privacy@gomusafir.app with the subject “Delete my account”.
- Send the e-mail from the address linked to your account. Tell us your name, whether you are a pilgrim, Journey team member, organisation or family follower, and, if you know it, the journey you were on.
- We confirm receipt, check that the request is really yours (section 2) and tell you when deletion is complete.
- If you only want some data deleted, such as a memory, a message or a photo, tell us what; many items can also be deleted directly in the app.
2. Checking that it is you
Deleting an account cannot be undone, so we make sure the request comes from the account holder. In the app, you are already signed in and confirm by typing DELETE. For a request by e-mail, we send a 6-digit code or a confirmation link to the e-mail address of the account, and we delete only after you confirm. If you no longer have access to that address, we may ask for other information that only the account holder knows, such as the journey and the phone number on the account.
We never ask for a copy of your passport or another identity document to delete an account. A parent, guardian or other representative can make a request for someone else if they show they may act for that person.
3. Leaving, pausing and deleting
Not every goodbye has to be a deletion. Signing out or removing the app from your phone does not delete your account or your data. A pilgrim can leave a journey or be removed from it by the Journey team; the account then stays, with Memories and other journeys. A Journey team member can choose to step away from a trip for a while and come back later.
Permanent deletion removes your account and personal data as described on this page. After deletion, you cannot sign in, and the data cannot be restored.
3.1 Pilgrims on a running trip
If you ask to delete your account while you are on a trip, or within 14 days before it starts, deletion is planned for the day after the trip ends, so your Journey team can still find you in an SOS. You can cancel with “Keep my account” until then. If you do not want to wait, tell us at privacy@gomusafir.app and we will delete your account sooner; we will first tell your Journey team that you are no longer reachable in the app.
3.2 Recovery periods
A deleted trip can be restored by its Admin or Co-host within 30 days. Any recovery period exists only to protect you against mistakes. It never limits your right to erasure: if you ask us to delete without waiting, we will do so, unless the law requires us to keep the data.
4. Pilgrims
When a pilgrim deletes their account, we delete their profile, Passport details and form answers, messages, duas, locations, Memories, followers’ access and app settings. The pilgrim disappears from the full Journey Assurance report; only anonymous counts remain. Data that the organisation keeps in its own systems outside GoMusāfir is the organisation’s responsibility (section 9).
5. Journey team members
A Journey team member can ask for deletion by e-mail to privacy@gomusafir.app. An Admin or Co-host can also remove a member from the Journey team; this ends their access to the organisation’s journeys but does not delete their account.
Because the organisation needs a record of how its trips were run, we delete the Journey team member’s account and profile, and in the organisation’s trip records we replace their name with a neutral label, such as “Former Journey team member”, for actions like handling an SOS or sending a message. The organisation is told when a member of its team deletes their account.
6. Organisations
An organisation’s Admin can ask to delete the organisation by e-mail to privacy@gomusafir.app, from the Admin’s account address. Before deleting, we tell the Admin what will happen, and the Journey team is informed.
Deleting an organisation deletes its business account, company details, logo and cover, its journeys and the trip data we process for it, its Journey team memberships and its wallet. Unused seats in the wallet are lost and are not refunded in money. The personal accounts of pilgrims and Journey team members stay; each pilgrim keeps their own Memories. Invoices and payment records are kept as described in section 8.
Before deletion, the organisation can ask us for an export of the data it controls, so it can meet its own obligations.
7. Family followers in Memories
A family follower can ask to delete their account by e-mail to privacy@gomusafir.app. We delete the account, the journeys they follow and their hearts and messages. A follower can also stop following one journey, and a pilgrim can remove a follower at any time; access then ends at once on every device. Payments for following are not refunded when a follower is removed or deletes their account. We keep payment records as described in section 8.
8. What we keep and why
Some data must or may be kept after deletion, but only for the reason and the time stated, and only with the access needed for that reason.
| Data | Why we keep it | How long |
|---|
| Invoices, receipts and payment records | Dutch fiscal retention obligation | 7 years |
|---|
| Security and sign-in logs | Protecting accounts and investigating misuse | Proposed: 6 months (to confirm) |
|---|
| Logs of Journey team access to hidden details | Accountability towards pilgrims | Proposed: 12 months (to confirm) |
|---|
| Records needed for a legal claim or a request from an authority | Establishing or defending legal claims; legal obligations | Until the matter is closed |
|---|
| Backups | Restoring the service after a failure | Proposed: overwritten within 35 days (to confirm) |
|---|
| Anonymous statistics | Crowd levels, Journey Assurance counts, service improvement | No limit; they are no longer personal data |
|---|
9. Anonymisation
Where we keep information after deletion for statistics, we anonymise it: we remove names, Musafir numbers, contact details, exact places and anything else that could identify you, and we combine it with data from others. For example, Journey Assurance keeps only counts such as “16 of 17 departures on time”, and crowd levels never contain names or trips. Anonymous data can no longer be linked to you and is not personal data.
10. Chats, photos and uploads
When you delete your account, we delete the messages, photos, videos, voice notes and files you sent. In group chats, your messages are removed or shown as deleted. Copies that other people saved to their own phones are outside our control. Independently of any deletion, all chats of a trip are deleted for everyone 30 days after the trip ends, and you can delete a single message for everyone at any time.
Your Memories, your photos in Memories and the group album photos you added to your own Memories are deleted with your account. Photos that a Journey team member posted in a group album belong to that trip and are deleted with the trip data.
11. Journey records and alert history
Journey records include your participation in a trip, check-ins, gathering answers, alerts about drifting, being lost or low battery, SOS events and the alert history the Journey team sees. When you delete your account, these records are deleted or anonymised. If deletion is planned for the day after a trip (section 3.1), the records remain available to the Journey team until then, to keep the group safe. Voice chat transcripts are kept until 30 days after the trip and then deleted; the Listen back audio is deleted 10 minutes after each voice chat ends.
12. Data managed by your organisation
For the pilgrim data an organisation collects and manages for its journey, such as bookings and Passport details, the organisation is the controller and GoMusāfir is its processor. If you ask us to delete that data, we delete what is linked to your GoMusāfir account and may forward your request to the organisation, which decides on the rest. The organisation may have its own legal reasons to keep some details, for example under travel or tax law, and it must tell you so. You can also contact your organisation directly.
13. Apple, Google, Stripe and other services
- Apple and Google: purchases and app downloads are kept by Apple or Google under their own policies. Deleting your GoMusāfir account does not delete your Apple or Google account or purchase history. You can manage that with Apple or Google.
- Stripe: Stripe keeps payment data it needs under its own legal obligations. We ask Stripe to delete what it no longer needs where the law allows.
- Our service providers, such as hosting, e-mail and maps: we instruct them to delete your data together with ours, within their own backup cycles.
14. How long it takes
We act on a request without undue delay and at the latest within one month after we have confirmed it is yours. If a request is complex, we may extend this by two months and tell you why. For people protected by the Saudi PDPL we follow its time limits. Deletion from backups follows the backup cycle in section 8. We tell you when deletion is complete.
Back to top
Document 7 of 7
Security and Privacy
- Effective
- To be set on publication after legal review
- Last updated
- 22 October 2026
- Version
- 0.9
- Status
- Draft for legal review
This page explains how GoMusāfir protects pilgrims, Journey teams and travel organisations: how you sign in, who can see what, how we limit what we collect and what to do if you find a security problem.
No online service can promise perfect security. We describe what we do. How we use personal data is explained in our Privacy Policy; how we process data for travel organisations is set out in our Data Processing Agreement.
1. Our approach: privacy by design
GoMusāfir starts every personal detail closed and lets each pilgrim decide who sees it. The rules are part of how the app is built, not a setting someone has to remember. A few principles guide every feature:
- Collect less: we ask only for what a journey needs, such as the last four digits of a passport instead of a scan.
- Show less: the server sends each phone only what that person may see.
- Keep less, for shorter: trip data is deleted with the trip, and chats are deleted 30 days after the trip ends.
- Make access visible: every time a Journey team member looks at a detail a pilgrim has hidden, it is logged.
- No advertising, ever, and no selling of personal data.
2. Signing in
Pilgrims and Journey team members who are invited by e-mail receive a one-time sign-in link. The link works once, stays valid for 7 days and is stored by us only in hashed form, so it cannot be read back from our database. We never send a password by e-mail. If you open the link without the app, a web page lets you choose your own password and then shows you where to get the app.
You can also sign in with your e-mail address and your own password. On iPhone you can open GoMusāfir with Face ID, and on Android with your fingerprint, once you have turned this on. Your face or fingerprint is checked by your phone's operating system; GoMusāfir never receives it.
To slow down anyone who tries to guess a password, sign-in is paused for 15 minutes after 5 wrong attempts. Codes we send by e-mail have 6 digits, are valid for 10 minutes and allow 5 tries. When you change your password, you stay signed in on that device and are signed out everywhere else.
3. Roles and permissions
Each travel organisation decides who belongs to its Journey team. Team members have one of three roles: Admin, Co-host or Manager. Roles are permissions only; pilgrims never see them and simply see one Journey team badge.
Every role can run a trip. Buying seats and inviting new Journey team members is for admins and co-hosts; a manager asks them instead. Deleting a trip is for admins and co-hosts, and deleting the organisation is for admins only, with extra confirmation.
A pilgrim who leads a split group as coordinator is still treated as a pilgrim for privacy. A coordinator sees the group's name, photo and location during a session of that group, and never sees phone numbers, e-mail addresses or emergency contacts.
4. Separation between organisations and journeys
Every journey belongs to one travel organisation. Journey team members only see the journeys and pilgrims of their own organisation, and pilgrims only see the people of the trips they have joined.
Some information helps every group near the Haram, such as gate closures and crowd levels. It is shared without names, photos, trip names or anyone's location. A crowded area is only shown when at least 10 pilgrims from at least 3 trips are in it, and the raw positions used for this are kept for an hour at most.
5. Who sees what, enforced on the server
Privacy choices are checked on our server for iPhone and Android. The app never receives a detail it may not show, so hiding something is more than hiding it on the screen.
- Pilgrims choose who sees their name, photo and phone number: everyone on the trip, only women, only men, or only the Journey team. A hidden name becomes a Musafir number for that trip.
- Pilgrims choose who hears their voice. Hiding the voice from men is on by default for women. If the Journey team includes a woman, a pilgrim can also hide her voice from its men; the women of the Journey team always hear her.
- Other pilgrims never see your location unless you accept their request or share it. Requests last a set time, from 15 minutes to the whole trip.
- The Journey team sees location only between the trip dates. In an SOS, the team sees what helps reach you until the SOS is handled.
- Family at home see only what a pilgrim releases in Memories, after the pilgrim has moved on. Never live location, the hotel or the group, and never SOS or safety messages.
- Journey team members also have privacy: each chooses which pilgrims see their photo, phone and location.
6. Sensitive details and logged access
Passport, phone, medical and emergency contact details of pilgrims are protected for the Journey team. They stay masked until the team member confirms it is them with Face ID, fingerprint or their password. The details are then visible for 5 minutes on that device.
Every look by a Journey team member at a detail a pilgrim has hidden is logged with who looked, at what and in which situation. Exports of pilgrim lists and downloads of full trip reports are logged too. An export leaves GoMusāfir, so we remind the Journey team to share it only within the team, keep it off shared computers and delete it after the trip.
7. Encryption
Connections between the GoMusāfir apps, our web pages and our servers are encrypted in transit with TLS.
Where our infrastructure provider offers it, stored data is encrypted at rest.
On the phone, a visa copy that a pilgrim opens in the app stays on the phone, encrypted, until the trip ends.
8. Infrastructure and service providers
GoMusāfir runs on servers and services from established providers for hosting, storage, voice, captions and translation, maps, push notifications and e-mail. We choose providers that offer appropriate security and data protection terms, and we sign data processing agreements with them. Where data leaves the European Economic Area, we use safeguards such as standard contractual clauses.
We will publish the list of service providers that process personal data, with their role and location.
9. Data minimisation
- Passports: we ask the last four digits and the expiry date, never the full number or a scan.
- Location: never before day 1 or after the last day of the trip, and never live to family.
- Phone numbers: by default only the Journey team sees them. Pilgrims can chat without exchanging numbers.
- E-mail: our e-mails never contain passwords, passport numbers, health data or live location. Reports and invoices are links behind sign-in, not attachments.
- Lock screen: notifications never show phone numbers, e-mail addresses, coordinates or emergency contacts.
- Screen recording: names and photos are hidden in the app while the screen is recorded, and voice audio is kept out of the recording where the phone allows it.
- Translation: translations are made for display and not stored, and no names, locations or trips are sent to an AI service for translation.
- Memories: hotels are removed from routes and faces of other pilgrims are blurred.
10. Files and uploads
Files that the Journey team uploads, such as a programme or travel information, are limited in type and size. Before anyone sees or reads them, they are checked to be the type they claim, scanned for viruses and hidden code, and cleaned of scripts and macros. Files with macros are refused.
11. Monitoring and logging
We keep technical logs to run the service, detect misuse and investigate problems, and crash reports to fix errors in the apps. Logs are kept for a limited time and access to them is restricted.
12. Access by GoMusāfir staff
Only a small number of GoMusāfir staff can access the systems that hold personal data, and only when needed for support, security or maintenance. They are bound by confidentiality. We do not look at a travel organisation's trip data unless the organisation asks for support or we must investigate a security incident.
13. Incident handling
If we discover a security incident, we act to contain it, find the cause and prevent it from happening again. If personal data is affected, we inform the travel organisations concerned without undue delay, and we notify the supervisory authority and the people affected where the law requires it. Our Data Processing Agreement sets out what we tell organisations and when.
14. Backups and recovery
We make backups so that the service can recover from a technical failure. Backups are protected in the same way as live data and are deleted in a regular cycle. A deleted trip can be restored by its admins and co-hosts for 30 days, after which it is gone for good.
15. Deletion
Chats of a trip are deleted 30 days after the trip ends, and personal trip data is deleted with the trip. You can delete your account in the app. If you are on a running trip, deletion takes effect the day after the trip ends, so your Journey team can still find you in an SOS. Records that the law requires us to keep, such as payment records, are kept for the period the law sets.
16. Safety features and their limits
SOS reaches the whole Journey team at once, also through Do Not Disturb, and alerts warn when someone drifts from the group. These features help, but they are not an emergency service. They depend on the phone, its battery, connectivity, permissions and the Journey team being available. In an emergency, always contact local emergency services (911 in Saudi Arabia).
17. Apple, Google and Stripe
Card and bank details are handled by Apple, for in-app purchases on iPhone, or by Stripe, on Android and for company invoices. GoMusāfir never sees them.
Apple and Google run the app stores and the operating systems of your phone, including Face ID, fingerprint sign-in and push notifications. Their own security and privacy terms apply to what they do.
18. Keeping your account safe
- Choose a password you do not use anywhere else, and keep it to yourself.
- Turn on Face ID or fingerprint sign-in on your own phone only, and keep your phone locked with a code.
- Open sign-in links only from e-mails you expect. GoMusāfir never asks for your password by e-mail, phone or chat.
- Keep the app and your phone's operating system up to date.
- If you lose your phone or think someone else used your account, change your password and contact help@gomusafir.app.
- Journey team: lock your phone, do not share exports, and remove colleagues who leave.
19. Reporting a vulnerability
If you believe you have found a security vulnerability in GoMusāfir, please tell us at security@gomusafir.app. Include what you found, how to reproduce it and the possible impact. We will confirm receipt, keep you informed and tell you when it is fixed.
Please give us reasonable time to fix the problem before you share it with anyone else, only use test accounts or your own account, do not access, change or delete other people's data beyond what is needed to show the problem, and do not disrupt the service, for example through denial of service, spam or social engineering of pilgrims or staff.
If you act in good faith and follow these rules, we will not take legal action against you for your research and will not ask law enforcement to do so. We do not currently offer a bug bounty.
Back to top