# What it takes to run a dating app: the backend checklist

Published 2026-10-16. Updated 2026-10-16. https://www.datingapi.io/insights/dating-app-tech-stack

**In short:** A dating app needs ten backend systems working together: accounts, profiles and photos, discovery and matching, messaging, moderation, ID and age checks, payments, notifications, analytics and compliance. The app screens are the visible part. Most launch delays, store rejections and safety failures trace back to one of these systems being missing or thin.

Running a dating app takes ten backend systems working together: accounts, profiles and photos, discovery and matching, messaging, moderation, ID and age checks, payments, notifications, analytics and compliance. The app screens members see sit on top of these. Apple and Google will reject a dating app that lacks filtering, reporting and blocking [1][2], regulators in the UK and EU expect working safety processes [4][6], and members leave when matching or messaging is unreliable.

This checklist sets out what each system does, what goes wrong without it, and the questions to ask whoever builds or runs it.

## The checklist at a glance

| System | What it does | What goes wrong without it |
| --- | --- | --- |
| Accounts | Sign-up, login, sessions, deletion | Store rejection, account takeovers, duplicate and banned members returning |
| Profiles and photos | Stores profiles, resizes and serves images | Slow loading, unmoderated photos going live |
| Discovery and matching | Decides who sees whom | Empty feeds, the same faces repeated, members leaving |
| Messaging | Real-time chat between matches | Lost messages, no evidence when a report comes in |
| Moderation | Scans and reviews photos, bios, messages and reports | Scams, abuse and store removal |
| ID and age checks | Confirms members are real and adult | Under-18s on the app, fake profiles, regulatory action |
| Payments | Subscriptions, one-off purchases, refunds | Lost revenue, members charged wrongly, chargebacks |
| Notifications | Push, email and in-app alerts | Matches and messages go unseen |
| Analytics | Measures funnels, matching health and revenue | Decisions made blind |
| Compliance | Privacy, deletion, data export, regulatory records | Fines, store rejection, failed due diligence |

Source: our checklist, with store and regulatory requirements from Apple [1], Google Play [2][3], Ofcom [4] and the EU Digital Services Act [6][7].

## Accounts, profiles and photos

**Accounts** handle sign-up, login and sessions. Phone verification is the usual first barrier against fake accounts. Twilio Verify, a common choice, charges $0.05 per successful verification plus $0.0083 per SMS in the US [10]. If you offer social login such as Google or Facebook as the main sign-in, Apple requires an equivalent privacy-focused option that limits data to name and email [1]. Both stores require account deletion: Apple inside the app [1], Google inside the app and through a web link [3]. Without good account controls, banned members simply sign up again.

**Profiles and photos** store member details and images, generate resized versions and serve them quickly. Photos are the product in a dating app. Without a proper pipeline, images load slowly on mobile networks and, worse, go live before moderation has seen them. Profile fields also carry legal weight: data about a person's sex life or sexual orientation is special category data under UK GDPR and needs an extra legal condition to process [5].

## Discovery, matching and messaging

**Discovery and matching** decides which profiles each member sees. At its simplest it filters by distance, age and preference. Larger operators invest heavily here: Match Group lists recommendation algorithms among the shared capabilities its smaller brands draw on [11]. Without a working ranking system, members in thin areas see empty feeds, members in busy areas see the same few profiles, and the most attractive profiles get flooded. All three drive churn. See our guide to [liquidity](/glossary/liquidity) for why this matters more than features.

**Messaging** delivers chat in real time, stores history, and handles read receipts, photos and sometimes voice or video. It is also your evidence store. When a member reports abuse, moderators need the conversation. Without reliable messaging, matches go cold and reports cannot be investigated.

## Moderation and ID checks

**Moderation** is the system most often underbuilt. Apple's guideline 1.2 requires apps with member content to filter objectionable material, offer a way to report it with timely responses, let members block abusive accounts, and publish contact details [1]. Google Play requires in-app reporting and blocking and moderation "as is reasonable and consistent with the type of UGC hosted by the app" [2]. Google also says incidental sexual content must be hidden by default behind filters that take at least two actions to remove [16].

A working moderation stack has three layers: automated scanning of every photo and message, a review queue where people act on reports, and an audit trail of decisions. Automated image scanning is inexpensive, at $0.001 per image for the first million each month on Amazon Rekognition [9]. The human layer is the cost. Match Group told CBS News in 2024 that it spends $125 million a year on [trust and safety](/glossary/trust-and-safety) [13].

**ID and age checks** confirm members are real people and adults. In the UK, Ofcom's protection of children codes came into force on 25 July 2025 [4], which pushes dating apps towards [age assurance](/glossary/age-assurance) that actually keeps under-18s out. Published prices give a sense of scale: Veriff's self-serve plans cost $0.80 to $1.89 per verification [8], and Amazon's face liveness check costs $0.015 per check for the first 500,000 in US East [9]. Without these checks, fake profiles and scammers move in, and you have no defence when a regulator asks how you keep children off the service. More in our guide to [age verification](/insights/age-verification-dating-apps).

## Payments, notifications and analytics

**Payments** cover subscriptions, one-off purchases such as boosts, renewals, refunds and entitlements across iOS, Android and web. Apple requires in-app purchase to unlock features in the app [1], and keeps 30% of a subscription in the first year and 15% after a year of paid service [15]. Web billing has its own costs: Stripe charges £20 for each dispute received in the UK [14]. The backend must reconcile all three channels so a member who pays on the web is premium on their phone. When this breaks, members are charged without getting features, and support and [chargebacks](/glossary/chargeback) follow.

**Notifications** tell members about new matches, messages and likes through push, email and in-app alerts. Dating is time-sensitive. A message seen a day late often gets no reply. Without a notification system with sensible limits, matches go unseen, or members get so many alerts they turn them off.

**Analytics** measures sign-up funnels, matching health (likes, matches, replies), retention, [payer conversion](/glossary/payer-conversion) and moderation volumes. Without it, you cannot tell whether a drop in revenue comes from fewer sign-ups, worse matching or a pricing change.

## Releases and compliance

**Compliance** covers privacy notices, consent, account deletion, data export, retention rules and regulatory records. In the UK, Ofcom required illegal content risk assessments by 16 March 2025 and children's risk assessments by 24 July 2025 [4]. In the EU, the Digital Services Act has applied to all online platforms since 17 February 2024 [6], with duties including notice and action for illegal content and statements of reasons when content is removed [7]. Without records, you fail regulator requests, store reviews and buyer due diligence.

**Releases** sit across everything. Bumble says it often releases updates once a week to its mobile app and twice a day to its server backend [12]. Each app update goes through Apple and Google review, and both stores change rules every year. An app nobody is actively releasing slowly falls out of compliance. See our [launch checklist](/insights/dating-app-launch-checklist) for the store submission steps.

## What it means for dating app operators

- **Audit the ten systems, not the screens.** When you assess a build quote, a script or a platform, ask which of the ten it covers fully, which partly, and which you must add yourself.
- **Moderation and ID checks are not optional extras.** They are store requirements and regulatory expectations [1][2][4]. Budget for them as running costs. Our [cost guide](/insights/dating-app-development-cost) works through the numbers.
- **Keep an audit trail from day one.** Reports, decisions, deletions and age checks all need records that you can show a regulator, a store reviewer or a buyer.
- **Decide who runs releases.** Someone has to ship and resubmit both apps every time Apple or Google changes the rules. If that is not your team, it needs to be in a contract. Our comparison of [build, buy or join a platform](/insights/build-vs-buy-dating-app) covers who does what under each route, and [the platform page](/platform) shows how one managed platform splits it.

## Questions

**What features does a dating app backend need?**

At minimum: accounts, profiles and photo storage, discovery and matching, messaging, moderation, ID and age checks, payments, notifications, analytics, and compliance tooling such as account deletion and data export. Apple and Google both require filtering, reporting and blocking in apps with member content [1][2].

**Do dating apps have to let members delete their account?**

Yes. Apple requires apps that support account creation to offer account deletion inside the app [1]. Google Play requires an in-app deletion path and a web link where members can request deletion of their account and data [3].

**How often do dating apps release updates?**

Bumble says it often releases updates once a week to its mobile app and twice a day to its server backend [12]. Smaller operators release less often, but still need a team that can ship and resubmit to both stores.

**What does it cost to verify a dating app member's ID?**

Veriff's published self-serve prices run from $0.80 to $1.89 per verification [8]. Amazon Rekognition's face liveness check starts at $0.015 per check [9]. Phone verification through Twilio costs $0.05 per successful verification plus SMS fees [10].

## Sources

1. App Review Guidelines, Apple Developer, 2026-10-16. https://developer.apple.com/app-store/review/guidelines/
2. User Generated Content policy, Google Play Console Help, 2026-10-16. https://support.google.com/googleplay/android-developer/answer/9876937?hl=en-GB
3. Understanding Google Play's app account deletion requirements, Google Play Console Help, 2026-10-16. https://support.google.com/googleplay/android-developer/answer/13327111?hl=en-GB
4. Important dates for Online Safety Act compliance, Ofcom, 2026-08-24. https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/important-dates-for-online-safety-compliance
5. What is special category data?, Information Commissioner's Office, 2026-10-16. https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/special-category-data/what-is-special-category-data
6. DSA applies to all online platforms in the EU, Lewis Silkin, 2024-02-17. https://www.lewissilkin.com/insights/2024/02/17/dsa-applies-to-all-online-platforms-in-the-eu-102j0fj
7. Regulation (EU) 2022/2065 (Digital Services Act), EUR-Lex, 2022-10-27. https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng
8. Pricing and plans, Veriff, 2026-10-16. https://www.veriff.com/pricing
9. Amazon Rekognition pricing, Amazon Web Services, 2026-10-16. https://aws.amazon.com/rekognition/pricing/
10. Verify pricing, Twilio, 2026-10-16. https://twilio.com/verify/pricing
11. Match Group Q2 2026 shareholder letter, Match Group (SEC filing), 2026-08-04. https://www.sec.gov/Archives/edgar/data/0000891103/000089110326000128/mtch8-k20260804ex992.htm
12. Bumble Inc. annual report on Form 10-K for 2025, Bumble Inc (SEC filing), 2026-03-16. https://www.sec.gov/Archives/edgar/data/1830043/000183004326000027/bmbl-20251231.htm
13. Is the online dating industry investing enough in trust and safety?, Global Dating Insights, 2024-04-24. https://www.globaldatinginsights.com/news/is-the-online-dating-industry-investing-enough-in-trust-safety/
14. Stripe pricing (United Kingdom), Stripe, 2026-10-16. https://stripe.com/gb/pricing
15. Auto-renewable subscriptions, Apple Developer, 2026-10-16. https://www.developer.apple.com/app-store/subscriptions/
16. Understanding moderation requirements and incidental sexual content in UGC apps, Google Play Console Help, 2026-10-16. https://support.google.com/googleplay/android-developer/answer/12923286?hl=en-EN