What are the parts of a dating app chat system?
A dating chat system has five parts: a live connection, a message store, push alerts, moderation and a permissions layer. The first three are common to any chat product. The last two are where dating differs.
| Part | What it does | Dating-specific point |
|---|---|---|
| Live connection | Carries messages, typing and read status while the app is open | Members open the app in short bursts, so reconnecting cleanly matters more than raw speed |
| Message store | Keeps every conversation so it loads on any device | Messages can reveal sexual orientation, health or location, so treat them as sensitive |
| Push alerts | Tell a member about a new message when the app is closed | Alert text shows on a lock screen. Do not put message content in it by default |
| Moderation and reporting | Screens messages, takes reports, lets members block | Scams and harassment happen in private chat, not on profiles |
| Permissions | Decides who can message whom | Matched only, paid only, blocked, suspended, under review |
Get the permissions layer right early. Every message should pass one check on the server: are these two members allowed to talk right now? That single check is what makes blocking, suspensions and paid messaging work.
Do I need WebSockets for dating chat?
Yes, for most apps a WebSocket connection is the standard way to make chat feel instant. MDN describes the WebSocket API as a way to open a two-way session between a browser and a server, so messages arrive without the app having to keep asking for them. MDN lists it as widely available, in browsers since July 2015.
Three practical points:
- The connection will drop. Phones change networks and put apps to sleep. Design for reconnecting and fetching anything missed, not for a connection that stays up.
- The server is the record. A message counts as sent when your server has stored it, not when the phone shows it.
- Plain requests still work. A simple site can load the inbox with ordinary page requests and refresh every few seconds. It feels slower, but it is cheaper to run and easier to debug.
Our guide to real-time messaging and WebSockets covers the connection layer in more depth.
What happens when a member is offline?
The message is stored on your server and a push alert tells the member it is waiting. Do not rely on the push alert to carry the message itself.
Google's Firebase Cloud Messaging documentation shows why. A message ID from the service means only that the message "was accepted for delivery", not that it reached the device. If the device is offline, the service holds the message until it reconnects, for up to 28 days, and then discards it. If the app has been uninstalled, the message is discarded straight away.
So treat push as a doorbell. When the member opens the app, the app asks your server for everything since the last message it has. That one rule also fixes duplicates, messages out of order and members who use two devices. Our guide to push notifications for dating apps covers what the alerts should say.
How long should a dating app keep messages?
Keep messages for as long as the conversation is useful to the members and you have a reason to hold it, then delete them. There is no fixed legal period: the Information Commissioner's Office (ICO) says the UK GDPR does not set specific time limits for different types of data, but you must be able to justify how long you keep it.
A workable set of rules:
- Keep a conversation while both accounts are active and neither has deleted it.
- When a member deletes their account, delete their messages, apart from any tied to an open safety report.
- Keep reported conversations for a set, written period so moderators and, where the law requires, the police can see the evidence.
- Write the periods into your privacy policy and review them.
The ICO also says members have a right to erasure when you no longer need the data. See our guide to data retention for dating sites. This page is general information, not legal advice.
How do you moderate private messages?
Combine automated screening, easy reporting and human review, because no single method catches enough. The big apps publish some useful evidence on what works.
- Prompt the sender. Tinder's "Are You Sure?" feature detects harmful language before a message is sent and asks the sender to pause. Match Group said that in early testing it reduced inappropriate language in sent messages by more than 10%.
- Prompt the receiver. Tinder's "Does This Bother You?" asks the receiver whether they want to report a message. Match Group said reports of inappropriate messages rose by 46% among members who saw it.
- Blur before showing. Bumble's Private Detector blurs a suspected nude image in chat and lets the member choose whether to view it, block it or report it. Bumble has published an open-source version.
- Report with context. A report should send the moderator the reported message and the messages around it, so they can judge it fairly.
These are company figures, not independent studies, but they point the same way: small prompts change behaviour.
Rules sit behind this too. Ofcom's illegal content codes ask every in-scope service, whatever its size, to have a way to review suspected illegal content and take it down swiftly, and a complaints system that is easy to find and use. Google Play says features that allow one-to-one interaction, such as private messages, must let people block others.
One design choice affects all of this. If you encrypt messages end to end, your servers cannot read them, so you cannot screen messages on the server and can review only what a member chooses to report. Decide that deliberately and write the decision into your risk assessment. Our guide to a content moderation workflow covers queues and response times.
Should I build chat, buy a chat API or use a platform?
Buy or use a platform unless chat is the thing that makes your product different. Building the connection layer is achievable. Running it reliably, with moderation, at all hours is the expensive part.
| Route | What you get | Published entry price (20 November 2026) | Watch for |
|---|---|---|---|
| Build your own | Full control of features and data | Your developers' time, then hosting | Reconnection, delivery order, moderation tools and on-call cover are all yours |
| Stream (chat API) | Hosted chat with client libraries and basic moderation included | Free up to 1,000 monthly active members. Start plan $499 a month ($399 billed annually) for 10,000 | AI moderation is listed as an add-on on the enterprise plan |
| Sendbird (chat API) | Hosted chat with client libraries | Free trial up to 1,000 monthly active members. Starter $399 a month ($349 billed annually) at the 5,000 tier | Prices for larger tiers are not shown on the page; ask them |
| Dating platform | Chat built in, with matching, payments and moderation | Depends on the platform | Less freedom to change how chat works |
Both chat APIs price by what they call "monthly active users" and cap the number of connections open at once, so check both limits against your busiest hour.
A chat API gives you chat, not a dating product. You still build the permissions layer, connect reports to your moderation team and keep the member's plan in step with what they can send.
DatingAPI, run by the same group as this site, includes messaging, safety and moderation as part of its platform for apps. It charges per active and paying member with a $10,000 monthly minimum, so it suits brands that already have an audience, not a first launch. For a dating website, Dating Partners, our sister company, includes messaging in its software. Our dating software page explains both routes, and our guide to build, buy or white label covers the wider decision.
What should I ask before choosing a chat provider?
Ask where messages are stored, who can read them, and what happens at your busiest hour. Then ask about leaving.
- In which country are messages stored, and can I set how long they are kept?
- Can my moderators see a reported conversation with its context?
- Is text and image screening included, or an extra charge?
- What are the limits on active members and open connections, and what happens if I pass them?
- Can I export every conversation if I move to another provider?
- How do blocked and suspended members get cut off, and how fast?
Questions
Should dating chat have read receipts and typing indicators?
They are optional. Both make chat feel live, and both can make members anxious, so let members switch them off. Neither is needed at launch.
Can members send photos in chat?
Only if you can screen them. Bumble, for example, blurs suspected nude images and lets the member choose whether to view, block or report. If you cannot review images, launch with text only.
Should free members be able to message?
That is a pricing decision, not a technical one. Your chat system needs a permissions layer that can check a member's plan before a message is sent or read, so you can change the rule later.
Is a chat API cheaper than building chat?
At small scale, usually yes, because the published entry plans cost a few hundred dollars a month. Costs rise with active members, so ask for a quote at ten times your launch size.
Do I have to delete messages when a member deletes their account?
The ICO says you must not keep personal data longer than you need it, and members have a right to erasure when you no longer need the data. Set a written rule, including any short period you keep messages for open safety reports.
Sources
- MDN Web Docs: The WebSocket API, checked 20 November 2026
- Firebase Cloud Messaging: Set the lifespan of a message, checked 20 November 2026
- Match Group: Tinder introduces Are You Sure?, checked 20 November 2026
- Bumble: Open-source version of Private Detector, checked 20 November 2026
- ICO: Principle (e), storage limitation, checked 20 November 2026
- Ofcom: Illegal harms statement, summary of our decisions, checked 20 November 2026
- Google Play: User Generated Content policy, checked 20 November 2026
- Stream: Chat pricing, checked 20 November 2026
- Sendbird: Chat pricing, checked 20 November 2026
- DatingAPI, checked 20 November 2026
What changed
- : First published. Replaces our older guide to dating app chat architecture.