Services · Mobile app development · Matrimonial apps

Matrimonial apps for the Kingdom, built on family consent and Saudi data law.

Codeeo offers matrimonial app development in Saudi Arabia for khatba agencies, family matchmaking services and charitable marriage associations that want to serve families across the Kingdom. We build guardian managed profiles, photo privacy that families control, matchmaker workspaces and the consent and data controls that the Personal Data Protection Law expects. The result is a service that families in any region can trust with something as personal as a marriage proposal, and that you can extend from one city to many.

A national service has to respect that customs differ between regions while the legal framework stays the same. We design one platform with regional settings, so matchmakers in each area can follow local etiquette while compliance, security and reporting are handled once. Families moving between regions keep one account.

Built for
Matrimonial services, khatba networks and marriage associations operating in several Saudi regions or planning to.
Typical timeline
Phases and regional launch order are agreed in discovery and fixed in a written plan before design begins.
What you own
Source code, store listings, admin and matchmaker tools, and all family records, held in your organisation's accounts.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the platform can include

The national building blocks of a Saudi matrimonial platform.

Running a matrimonial service across Saudi Arabia means dealing with national systems once and regional differences many times. Identity, payments, invoicing and data protection follow national rules set by bodies such as SDAIA, ZATCA and the National Cybersecurity Authority. Matchmaking etiquette, the role of the extended family and how quickly photos are shared vary from Najd to the Hijaz, the south and the Eastern Province. The capabilities below are the ones that matter most at national scale. Some belong in the first release for every operator; others, such as association case management or multi region reporting, depend on your model. We set the order with you in discovery and plan the platform so that adding a region never means rebuilding it.

Explain your project
  • Nafath identity verification

    Identity confirmed through Nafath, via an approved provider route, so every guardian and candidate is a real adult resident. The platform keeps only the result of the check and the date, which limits the personal data you hold and makes the verified badge meaningful. Families abroad can be checked by a matchmaker instead.

    Fake and underage profiles are stopped before they reach a family.

  • PDPL consent and sensitive data controls

    Separate, recorded consent for each purpose, optional fields for anything the PDPL treats as sensitive, such as religious belief or health, and a self service area where families can see, correct or delete their data. Retention periods are set with your adviser.

    Your data handling can be explained to SDAIA and to any family who asks.

  • Guardian and wali roles

    Distinct account roles for the guardian, the candidate and other relatives, with the guardian approving contact and the candidate confirming their own listing. The rights of each role can be adjusted per region or per service without changing the code. A candidate can request a direct login once the guardian agrees.

    The family hierarchy is built into the platform rather than left to chance.

  • Regional matchmaker network

    Matchmakers assigned by region and city, each seeing only her own families and proposals. National administrators see totals and quality measures without opening family files. Families choose whether to be visible in their own region only or nationally. Workload per matchmaker is visible so no region is overloaded.

    You can open a new region by appointing a matchmaker, not by redeveloping the app.

  • Photo consent ledger

    Every photo release is a recorded event: who asked, who approved, when it expires and when it was withdrawn. The ledger supports disputes and complaints, and the same structure works whether a region shares photos early or only after a family visit.

    Any question about a shared photo can be answered from the record.

  • Contract stage handoff

    When families agree to proceed, the app explains that the marriage contract is registered through the Ministry of Justice's official channels, including Najiz and a licensed marriage registrar, and links there. The app does not draft or store contracts itself.

    Families leave the app for the official process at the right moment, with no confusion.

  • Premarital screening guidance

    A short explanation at the engagement stage that Saudi law requires premarital screening through the Ministry of Health, with a link to official information. No results or health details are requested or stored, keeping sensitive health data out of your systems.

    A required national step is flagged without creating a health data liability.

  • Saudi payment methods and Fatoora

    mada, Apple Pay, STC Bank and SADAD for packages and registrations, connected through a licensed payment provider, with electronic invoices produced in line with ZATCA's Fatoora requirements and exported to your accounting system. Failed payments retry politely without blocking a family's profile.

    Payments and tax invoices work the way Saudi families and auditors expect.

  • Hijri and Gregorian dates

    Dates of birth, visits and package periods shown in both calendars, with the family's preference remembered. Prayer times by city are used to avoid suggesting visit slots that clash, which matters when guardians in several regions share one schedule.

    Scheduling feels natural to every family in every region.

  • National reporting and audit logs

    Dashboards showing registrations, proposals and outcomes by region, and audit logs of every staff access to a family file. Security controls follow the National Cybersecurity Authority guidance your adviser considers relevant to your service. Logs are retained for the period your adviser sets.

    Leadership sees how each region performs and every sensitive access is traceable.

Who this is for

Four organisations building matrimonial services at national scale.

National scale changes the brief. A single matchmaker can rely on memory and trust; a platform covering several regions needs rules, roles and records that work without her. The operators we build for in Saudi Arabia usually fall into one of the four groups below. For each we start with discovery, held in person at our Riyadh office or by video call for teams elsewhere in the Kingdom. Whatever the group, the first question is the same: what must be true for a guardian in any region to trust your service with a daughter's or son's details?

01

A network of khatba agencies under one brand

You are bringing several established matchmakers in different cities together on one platform. Each keeps her own families and her own way of working, while you provide verification, payments and support centrally. We build regional workspaces, national administration and clear rules for when a family can be suggested outside its own region. Financial settlement between the brand and each matchmaker can also be tracked in the admin view.

Each matchmaker keeps her relationships; the brand provides the infrastructure.

02

A marriage association with branches

Charitable associations that help young people marry often combine matchmaking with premarital courses and family counselling. We separate support records from matchmaking data, add volunteer roles with narrow access and produce reports for your board and for the National Center for Non-Profit Sector's requirements as your adviser defines them. Branches can share a national pool of families or keep separate lists, depending on your policy.

Confirm with your adviser what your licence covers.

03

A digital matrimonial company scaling nationally

You launched in one city and families elsewhere are asking to join. We review the existing app for privacy gaps, then plan regional settings, matchmaker recruitment tools and stronger moderation, so expansion does not weaken the trust you built at home. Where the current code cannot carry the load, we say so plainly. Where it can, we keep what works and avoid a costly rewrite.

04

An investor backed new entrant

You want to enter the Saudi market with a serious, family centred service from day one. We help you choose a launch region, design the consent and guardian model, and build a first release that can pass app store review, satisfy your legal adviser and grow to new regions on a planned schedule. We also prepare the documentation investors and auditors usually ask to see about data handling and security.

How we take a matrimonial platform across the Kingdom.

  1. 01National and regional discoveryWe map the legal framework with your adviser, then talk to matchmakers in each launch region about local etiquette, photo norms and family roles. Findings are written into a short brief.
  2. 02Platform rulesConsent purposes, guardian rights, visibility levels, retention periods and moderation policy are written as one rulebook, with regional variations listed clearly. Your adviser signs it off.
  3. 03Arabic first design systemOne set of components in formal Arabic with English support, tested with parents and matchmakers from different regions so the tone suits all of them. Contrast and text size suit older readers.
  4. 04Build and national integrationsApps, matchmaker workspace and admin built with Nafath, payments, Fatoora invoicing and hosting arranged to meet your data obligations. Every role is tested separately.
  5. 05Launch in the first regionOne region goes live with a small group of matchmakers. We measure where families hesitate, fix it and confirm the rulebook works in practice. Matchmakers are trained in person or by video.
  6. 06Regional expansionFurther regions open on a planned schedule, each with its own matchmakers and settings, while security, compliance and releases continue centrally. Each region gets its own launch checklist.

Technology

What we build this with.

Native or cross platform apps for iOS and Android, web workspaces for matchmakers and administrators, and a backend with encryption, role based access and audit logging. Hosting is chosen to meet your data residency and transfer obligations under Saudi law.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

What national operators ask about matrimonial apps.

Several national frameworks, confirmed for your model by a Saudi lawyer.

The Personal Data Protection Law, supervised by SDAIA, governs consent, sensitive data and transfers abroad. ZATCA rules cover electronic invoicing, the e-commerce law applies to paid online services, and NCA guidance shapes security expectations. Charities have their own registration rules. We are developers, not legal advisers, so we build to the requirements your lawyer confirms and keep the controls easy to update. Store policies from Apple and Google on age ratings and user generated content apply on top of Saudi law, and we prepare the review notes they ask for.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews