Privacy Policy
Last updated 30 October 2026
Humsafar (“we”, “us”, “the app”) is a marriage-intent application for iOS and Android. This policy explains what personal data we collect, why, on what legal basis, who else processes it, how long we keep it, and what you can do about it. It applies to the apps, the Humsafar backend, and this website.
1. Who is responsible for your data
The data controller is Saga Verify AS (organisation number 917 284 512), Postboks 1054 Forneburingen, 1307 Fornebu, Norway. For anything about your personal data, write to [email protected].
2. The short version
- Your email address or phone number is used to sign you in and to contact you about your account or a security incident. It is never shown to other members.
- Location is a country and a city. We do not store your coordinates.
- Your profile, photos and messages are visible only inside the app, to the people the app shows them to.
- Usage analytics are off until you agree to them, are never linked to your account, and can be switched off at any time.
- Nothing from your conversations reaches an AI provider unless you agree first.
- We do not sell your data, we do not share it for advertising, and we do not track you across other companies' apps or websites.
- You can delete your account, and everything associated with it, from the Account tab.
3. Before you sign in
You can open Humsafar and look around without an account. While you are not signed in, the app does not know who you are, and only two things can leave your device:
- Crash reports (Firebase Crashlytics) — when the app crashes, a technical report with the device model, OS version, app version and the state of the code at the moment of the crash. These are not linked to you or to an account. We need them to keep the app working, so they are always on.
- App usage analytics (Firebase Analytics) — only if you agree. On first launch the app asks you, under “Help us improve”. You can accept, or choose Customize and leave App usage analytics switched off. See section 6.
4. What we collect when you have an account
| Data | Why we have it | How it is stored |
|---|---|---|
| Email address or phone number | To create your account, send you a one-time verification code, and contact you about your account or a security incident | On our servers. Never shown to other members. Codes themselves are stored only as a hash |
| Name, date of birth, gender | Shown on your profile; date of birth also enforces the 18+ minimum | On our servers |
| Country and city | So people can find matches near them | Country and city name only — never coordinates |
| Profile details you choose to add | Your story, intentions, family plans, sect, employment status, lifestyle answers | On our servers. All optional |
| Photos | Your profile pictures and any images you send in a chat | On BunnyCDN storage in the EU, served through short-lived signed links |
| Messages | To deliver your conversations | On our servers. The latest message event is also passed through Firebase Realtime Database so the other person's app updates |
| Likes, saves, blocks, reports, profile views | To power matching, your Insights, and safety tools | On our servers |
| Device push token and device identifier | To send you notifications about matches and new messages | Per device, removed when you log out |
| App language | So verification emails and notifications reach you in your language | On our servers |
| Terms acceptance | To record which version of the Terms and this policy you accepted, and when | On our servers |
| AI settings and allowance | The goal and context you write for reply suggestions, and how much of your monthly allowance you have used | Settings on your device; allowance usage on our servers |
| Subscription status | To unlock paid features you have bought | With RevenueCat, under a random account identifier. We never see your card details |
| Sign-in sessions | To keep you signed in securely on each device | On our servers; refresh tokens only as a hash |
Religious information
Your sect, and some lifestyle answers, can reveal your religious beliefs, which data protection law treats as a special category of data. Adding them is entirely optional. If you add them, you are explicitly agreeing to us showing them on your profile and using them in matching. You can change or remove them at any time from the Account tab, which withdraws that agreement.
How location works
To set your city you drop a pin on a map. Your device asks Apple's (or Google's, on Android) map service which city that pin falls in, and only the resulting country and city name are sent to us. On Android you can also let the app centre the map on your approximate position; that needs your permission, and the position stays on your phone. The pin's coordinates are never sent to us or stored.
What we deliberately do not collect
- Your precise location.
- Your contacts, calendar, or other apps' data.
- Advertising identifiers. Advertising features in our analytics are switched off.
- Any payment card details — purchases are handled entirely by Apple or Google.
5. Why we use it, and our legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Running your account: sign-in, profile, matching, chats, notifications, purchases | Performance of our contract with you — art. 6(1)(b) |
| Showing and matching on religious information you choose to add | Your explicit consent — art. 9(2)(a) |
| App usage analytics | Your consent — art. 6(1)(a) |
| Sending conversation context to a third-party AI provider | Your consent — art. 6(1)(a) |
| Crash reports, abuse prevention, reports and blocks, request signing and other security measures | Our legitimate interest in keeping the app working and its members safe — art. 6(1)(f) |
| Telling you about a security incident that affects you; keeping records the law requires | Legal obligation — art. 6(1)(c) |
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
6. Analytics and crash reports
App usage analytics (Firebase Analytics) help us see which features are used and how long people spend in the app — for example which tab was opened, or that a profile card was shown. They are off until you agree, use a random, resettable app instance identifier, and are never linked to your account, your name, or your email address or phone number. Advertising storage, ad personalisation and ad user data are always denied. You can change your choice at any time under Account → App settings; your choice is stored in your device's secure storage.
Crash reports (Firebase Crashlytics) are sent whenever the app crashes, whether or not you are signed in. They contain technical information about the crash only, and are not linked to your account.
We also use Firebase Remote Config to switch features on and off and to tell you when an update is required. It sees the app version and a random installation identifier, not who you are.
7. How we use your contact details
We store the email address or phone number you sign up with. It identifies your account, and we use it to send you one-time verification codes when you sign in. Verification emails are sent through Brevo.
We also keep it so we can reach you when it matters: if there is a security incident that affects your account or data, or about a safety or account issue that needs your attention. We do not use it for marketing, and it is never shown on your profile or to other members.
8. Notifications
Notifications are delivered through Google Firebase Cloud Messaging and, on iPhone, Apple's push notification service. A new-message notification contains the sender's name and the message text, or a short-lived link to the image they sent, so it can be shown on your lock screen. You can turn notifications off in your phone's settings.
9. Artificial intelligence features
The app can suggest a reply for you. On iPhones that support Apple Intelligence, this can run entirely on your phone with Apple's on-device model, and nothing leaves the device. On Android, and on iPhones without it, suggestions come from a server-side provider as described below.
If you choose a server-side provider instead — OpenAI, Anthropic, Google Gemini or DeepSeek — the goal and context you wrote in AI Settings, and where needed parts of that conversation, are sent through our servers to that provider so it can generate a suggestion. The app asks for your explicit agreement before this happens for the first time, and you can decline and continue to use every other part of Humsafar. We do not send your name, contact details or photos to AI providers, and we do not keep the suggestions they return. Suggestions are drafts: nothing is sent to the other person until you send it.
Photos and message text are also screened for explicit content. This screening runs on your own device — the images and text are not uploaded for that purpose.
10. Who else processes your data
We use a small number of service providers (processors), each bound by a data processing agreement and used only for the purpose named:
| Provider | What for | Where |
|---|---|---|
| Google Firebase | Real-time chat updates (Realtime Database), push notifications (Cloud Messaging), crash reports (Crashlytics), usage analytics with your consent (Analytics), feature flags (Remote Config) | EU and USA |
| BunnyCDN (BunnyWay d.o.o.) | Storage and delivery of profile and chat images | Storage in Germany; delivery from EU edge locations |
| Cloudflare | Network security and protection against denial-of-service attacks for our servers | Global network |
| Brevo | Sending verification-code emails | EU |
| RevenueCat | Managing subscriptions bought through Apple or Google | USA |
| OpenAI, Anthropic, Google (Gemini), DeepSeek | Reply suggestions — only the provider you pick, and only after you agree | USA (OpenAI, Anthropic, Google); China (DeepSeek) |
Our own servers, which hold your account, profile and messages, are in Frankfurt, Germany. Apple and Google also process data as independent controllers when you download the app, buy a subscription, or receive a notification, under their own privacy policies.
We do not sell personal data, and we do not share it with advertisers.
Transfers outside Europe
Some of these providers process data outside the European Economic Area. Where they do, the transfer is covered by the European Commission's Standard Contractual Clauses or, for US companies certified under it, the EU–US Data Privacy Framework. China has no adequacy decision: DeepSeek receives data only if you pick it as your suggestion provider and agree to the prompt in the app. You can ask us for a copy of the safeguards that apply.
11. How long we keep it
- Your account, profile, photos and messages: until you delete your account, or until a message is deleted by a participant. When an image is deleted it is removed from storage immediately; copies cached by the delivery network expire within 24 hours.
- Likes, saves, views, blocks and reports you made or received: deleted together with your account.
- Sessions: a sign-in session lasts up to 30 days and is extended while you keep using the app. Logging out revokes it immediately.
- Verification codes: valid for five minutes, and stored only as a hash.
- Verification email logs (Brevo): one month.
- Push tokens: until you log out of that device or delete your account.
- Real-time chat events (Firebase): only the latest event per conversation is kept, and it is overwritten by the next one.
- Usage analytics: event data tied to the random app identifier is deleted by Firebase after 2 months; only aggregated reports that identify no one are kept after that.
- Crash reports: 90 days.
- Subscription records (RevenueCat): deleted when you delete your account. Apple and Google keep their own purchase records under their policies.
12. Your rights
You can, at any time:
- See and correct everything on your profile from the Account tab.
- Delete your account from Account → Management → Delete account. This cannot be undone.
- Withdraw consent to analytics under Account → App settings, or remove optional profile details. Withdrawing does not affect processing that happened before.
- Turn on Incognito mode so others are not shown your activity on their profile.
- Block or report anyone, and review those lists later.
Under the GDPR you also have the right to access your data and receive a copy of it in a portable format, to have it erased, to restrict or object to how we use it, and to object to processing based on our legitimate interests. To use any of these rights, write to [email protected]. Please write from the email address you signed up with, or tell us the phone number, so we can locate the account. We answer within one month.
If you are unhappy with how we handle your data, you can complain to the Norwegian Data Protection Authority (Datatilsynet) or to the data protection authority where you live. We would appreciate the chance to put it right first.
13. Children
Humsafar is for adults. You must be 18 or older to create an account, and the app enforces this at sign-up. If you believe a minor has an account, tell us at [email protected] and we will remove it.
14. Security
Traffic between the app and our servers is encrypted in transit. Sign-in tokens are short-lived and every request is checked against a session that you can revoke by logging out. Refresh tokens and verification codes are stored only as a hash. Images are served through signed links that expire. On your device, credentials and your analytics choice are held in the platform's secure storage — the iOS Keychain and Android's encrypted preferences. So that you stay signed in after reinstalling the app, the iOS Keychain and, on Android, Google Play services' Block Store keep your sign-in token, your analytics choice and a random device identifier on the device; they are not uploaded to a cloud backup.
No system is perfect. If a breach puts your rights at risk, we will tell you and the relevant authority as required by law.
15. This website
hum-safar.com sets no cookies, runs no analytics, and loads nothing from third parties. If you use the contact form, we receive your name, email address and message by email and use them only to reply. To stop abuse, the form remembers your IP address for one hour. Like any web server, ours keeps standard access logs.
16. Changes to this policy
If we change this policy materially we will update the date at the top and, where the change affects how we use your data, notify you in the app.
17. Contact
Saga Verify AS, organisation number 917 284 512, Postboks 1054 Forneburingen, 1307 Fornebu, Norway. Write to [email protected] or use the contact form.