Privacy policy
Last updated: 27 September 2026
This policy explains how GP ACCIPE LTD (“we”, “us”) uses personal data when you use Mithaq, including the mobile apps, the web app, and the waitlist website. English is the governing language of this policy. The Arabic text is a translation.
1. Who we are
Mithaq is a project of GP ACCIPE LTD, a private limited company registered in England and Wales (company number 16653943). Registered office: 19 Mansard Close, Hornchurch, England, RM12 4HS.
We are the controller of personal data processed for Mithaq under the UK GDPR and the Data Protection Act 2018.
GP ACCIPE LTD is registered with the Information Commissioner’s Office (ICO) as a data controller. Registration reference: ZC256019. Public register entry: https://ico.org.uk/ESDWebPages/Entry/ZC256019.
Contact: hello@mithaq.org.uk
2. What this policy covers
This policy covers:
- The Mithaq app on iOS, Android, and web
- The waitlist website that collects the same account before the app is published
- Matching, chat, photos, wali (guardian) links, optional Support payments, and the face check described below
It does not cover other websites or apps that you open from Mithaq (for example Apple, Google, or a payment page). Those services have their own policies.
3. Age
Mithaq is for people 18 or older. We use the date of birth you give us to check that. We do not knowingly keep accounts for children. If you believe someone under 18 has an account, email hello@mithaq.org.uk.
4. Data we collect
Account
Depending on how you sign in, we store an email address, a phone number, and/or an identifier from Google or Apple. We also store the role you choose (man, woman, or wali). Role is part of how matching works and is not casually switched later.
Profile (man and woman)
We store the profile fields you complete so other matchable users can see a card and a full profile. That includes identity details (display name, residence country and city, nationality, ethnicity, height, occupation group, education, languages, marital status, children, willingness to relocate), religious practice (including prayers, madhab, faith background, hijab for women, beard for men), free-text about and looking-for, and partner preferences.
Age shown to others is derived from your date of birth. Other users do not see the raw date.
An illustrated avatar is not a photograph. Wali accounts do not have a matchable profile.
Religious practice and related fields are special-category data under UK GDPR. We use them because you supply them so matching can work. You can leave optional fields blank.
Residence cities come from the SimpleMaps Basic World Cities list (CC BY 4.0). That list is not personal data about you.
Waitlist website
The waitlist uses the same account as the app. Until the app shows you, waitlist profiles stay hidden from Home and Search. The site does not collect photos.
We may store first-party campaign parameters (UTM) so we know which advert or group sent you. Join uses Google reCAPTCHA to stop bots; Google may receive device and interaction data for that check only. The site does not load Meta Pixel, Google Ads tags, or other advertising trackers.
The site stores a language cookie (`mithaq_locale`) and an authentication session from our database provider.
Photos
Profile photographs live in a private storage bucket. Clients load them with short-lived signed URLs. Photos stay locked until you have an active match and both of you accept a photo exchange. After that, you, your match, and (for a woman) an active linked wali may view them.
When a photo is opened, we overlay a watermark in the form “Viewed by {name} · {time}”. The watermark is a deterrent. It is not a guarantee that someone cannot copy the image.
Face check (Didit)
Matchable users (man and woman) complete a one-time photo check during onboarding: you upload one reference photo, then a live selfie is checked for liveness and matched to that photo by Didit. We do not ask for an identity document.
Mithaq stores only a status (`none`, `pending`, `approved`, `declined`, or `in_review`), the latest Didit session id, and the time of approval. We do not store the live selfie, a match score, or Didit image URLs.
Until the check is approved, a matchable account stays off Home and Search. You can refuse the check and delete the account instead. Adding more photos later does not repeat the check.
Didit processes the selfie and the reference photo as our processor. Didit may keep session data under its own retention rules. See Didit’s privacy information as well as this policy.
Wali accounts do not go through this check.
Matching, chat, and wali
We store interests, rejection reasons you choose to give, connections, and text chat messages. Chat is text only. We do not put message bodies in analytics.
A woman may link a wali. The wali sees what that role allows (view-only or co-manage send). A wali is a role, not a paid plan.
You may report another user or a message. We store the report so staff can review it.
You may take a break. That hides you from new discovery. It does not delete your account.
Notifications and devices
If you allow notifications, we store a device token so we can send alerts (for example a new message or a screenshot notice). You can change notification types in Settings. We send generic title and body copy, not chat text or photo URLs.
Analytics and crash reports
Firebase Analytics and Crashlytics may receive your account id, role, and event names (for example that an interest was sent). They do not receive your email, phone, display name, date of birth, message text, or photo URLs.
Optional Support
The app is free. Optional Support is a tip through the App Store, Google Play, or Stripe via RevenueCat. It does not unlock Search, interest, ranking, or any other feature.
We may keep a snapshot of display name, email, and phone on the donation record so we can send a thank-you and meet accounting needs. Apple, Google, and Stripe keep their own payment records.
5. Why we use the data
- To create and run your account
- To show profiles, interests, matches, and chat
- To run the face check and keep photos private until a mutual exchange
- To send the alerts you allow
- To keep the service safe (reports, bans, technical logs)
- To count waitlist sign-ups and remember which campaign sent you
- To accept optional Support and record the donation
- To understand product use without reading your messages
6. Who we share data with
We do not sell your data. We do not share profiles with advertisers or data brokers.
We use processors who handle data for us:
- Supabase — accounts, database, private photo storage, and realtime chat (hosted in `eu-west-1`, Ireland)
- Google — Firebase Analytics, Crashlytics, and FCM; optional Google sign-in; Play billing; reCAPTCHA on the waitlist
- Apple — optional Apple sign-in and App Store billing
- Didit — liveness and face match
- RevenueCat and Stripe — optional Support
A matched user sees the profile you chose to share, and photos only after a mutual exchange. A linked wali sees what you granted. Staff may review reports and related chat to keep people safe.
Sign-in with Google or Apple sends those providers only what they require to authenticate you.
7. Screenshots, cameras, and sharing other people’s content
Photos of other people are shown for matching, not for copying.
- On iOS, if the system reports a screenshot while shared photos are open, we may notify the other person. That is a notice. It does not block screenshots.
- On Android, the photo-view screen uses a secure flag so the system screenshot and screen recorder cannot capture that window. Another camera can still photograph the display.
- On web, we cannot stop capture.
Watermarks and notices are deterrents. They are not a guarantee. You must not download, screenshot for sharing, photograph the screen, or pass on another person’s photos, chats, or profile. The terms of use forbid that. We may suspend accounts that ignore it.
8. Where data is stored and transfers
Our primary database is in the European Union (`eu-west-1`). Some processors (including Google, Apple, Didit, RevenueCat, and Stripe) may process data outside the United Kingdom. Where they do, they provide appropriate safeguards (for example standard contractual clauses) as required by UK data protection law.
9. How long we keep data
We keep account, profile, photo, interest, and chat data while the account exists.
If you delete the account, we remove the login, profile, photos we store, chats, interests, device tokens, and related rows we hold. See section 11.
We may keep a Support donation snapshot (name, email, phone, amount, store) after the account is gone, for accounting and thank-you records. Payment providers keep their own receipts.
Didit may retain its own session records for a limited period.
Staff reviewing reports may look at recent chat in a limited window (about 15–30 days). That is a review window, not a promise that messages are deleted after that time while the account still exists.
Short-lived backups may hold deleted data until those backups expire.
10. Your rights
Under UK GDPR you can ask to:
- Access a copy of your data
- Correct inaccurate data
- Erase your data (including by deleting the account)
- Restrict or object to certain processing
- Receive data you provided in a portable form
- Withdraw consent where we rely on consent (for example notification permission, or refusing the face check and deleting the account)
You can edit most profile fields in the app. To use these rights, email hello@mithaq.org.uk. You can also complain to the Information Commissioner’s Office at https://ico.org.uk/make-a-complaint/. GP ACCIPE LTD is registered with the Information Commissioner’s Office as a data controller. Registration reference: ZC256019. Public register entry: https://ico.org.uk/ESDWebPages/Entry/ZC256019.
11. How to delete your data
While you can sign in:
- In the app: Settings → Delete my account. Confirm by typing DELETE. You can take a break instead if you only want to hide for a while.
- On the website: open Delete my data, sign in with the same method you used to join, and confirm.
Both paths call the same deletion process. That process deletes your Auth user, the profile and related database rows, and the photo files in our private bucket for your account.
If you cannot sign in, email hello@mithaq.org.uk from a contact we can match to the account.
Deletion cannot be undone. After deletion, a Support snapshot may remain as described above, and Apple, Google, Stripe, Didit, and backup systems may still hold what they already processed, for a limited time or as the law requires.
12. Security
Traffic uses TLS. The database provider encrypts disks at rest. The app and the public site use a publishable key plus row-level security, not a secret admin key. Photos are not in a public bucket.
No method is perfect. Email us if you think there has been a breach of your account.
13. Changes
We will update the “Last updated” date when this policy changes. Material changes will be posted in the app and on the website. Continued use after an update means you have read the new policy.
14. Contact
GP ACCIPE LTD
19 Mansard Close, Hornchurch, England, RM12 4HS
hello@mithaq.org.uk