What counts as a data breach on a dating site?
A personal data breach is a security incident that has affected the confidentiality, integrity or availability of personal data. That is the definition used by the Information Commissioner's Office (ICO), and it is wider than a hack.
The ICO's examples include unauthorised access, sending data to the wrong recipient, lost or stolen devices and unauthorised changes to data. On a dating site, that covers:
- an attacker copying the member database
- a bug that shows one member's messages or photos to another
- a support agent emailing an account export to the wrong person
- a staff login used by someone who should not have it
- a storage bucket of profile or ID photos left open to the internet
Dating breaches carry more risk than most. Profiles and messages can reveal sexual orientation, religion and health, and on a niche brand the fact of membership can be sensitive by itself. Our guide to GDPR for dating sites explains why.
This page is general information, not legal advice. Call a lawyer early in any real incident.
What should you do in the first 72 hours?
Contain the breach, keep the evidence, establish the facts and decide who must be told. The table combines the ICO's rules with the US Federal Trade Commission's (FTC) guide for businesses.
| When | What to do | Why |
|---|---|---|
| At once | Record the time you became aware, and name one person to lead | The UK reporting deadline runs from when you become aware |
| First hours | Stop further data loss. Take affected equipment offline, but do not switch machines off until forensic experts arrive | The FTC's instruction, so that evidence is kept |
| First hours | Change passwords, keys and access tokens | The FTC warns that stolen credentials leave you exposed even after an attacker's tools are removed |
| First day | Bring in legal, security and communications help, and tell your insurer | The FTC lists these roles for a response team |
| First day | Work out what data was taken, how many members are affected and whether you can contact them | You need this for every report and notice |
| By 72 hours | Report to the ICO if a risk to people is likely | UK GDPR deadline |
| Without undue delay | Tell affected members if the risk to them is high | UK GDPR duty |
| Afterwards | Fix the cause, record the breach and review your plan | The ICO requires a record of every breach |
Do not destroy forensic evidence while you clean up. The FTC also says to remove exposed data from your own website, ask search engines to stop archiving it, and look for copies posted elsewhere.
Check your cyber cover before you need it. See our guide to dating business insurance.
When must you report a breach to the regulator?
In the UK, you must report to the ICO not later than 72 hours after becoming aware of a breach, if a risk to people's rights and freedoms is likely. If you report late, you must explain the delay.
The ICO says the report must cover:
- the nature of the breach, including where possible the categories and approximate numbers of people and records affected
- the name of your data protection officer or other contact
- the likely consequences
- the measures you have taken or plan to take
Risk is judged case by case. The ICO's own example is that a stolen customer database would need reporting, while a lost staff telephone list normally would not. A dating member database sits firmly on the first side of that line.
Failing to notify a reportable breach can itself lead to a fine of up to £8.7 million or 2 per cent of global turnover, the ICO says. You must also keep a record of every breach, reported or not, with the facts, the effects and what you did.
The EU GDPR has an equivalent duty, with reports going to the data protection authority in the relevant country.
When must you tell members, and what should you say?
You must tell members without undue delay when a breach is likely to result in a high risk to their rights and freedoms. The ICO can order you to notify if it thinks the risk is high.
The ICO says the message must use clear, plain language and include:
- what happened
- a contact point for questions
- the likely consequences
- what you have done and what you plan to do
- where possible, specific advice, such as resetting a password or watching for phishing
Dating adds three points of its own.
- Be discreet. The notice itself can reveal that someone uses a dating service. Use a neutral subject line, and send it only to the address the member registered.
- Warn about blackmail and impersonation. Tell members that criminals may contact them claiming to hold their data, and that they should not pay.
- Say how you will contact them. The FTC advises telling people how you will and will not get in touch, so they can spot fake messages that follow a breach.
Do not play down what happened. The FTC says not to make misleading statements about a breach and not to withhold details that would help people protect themselves.
What are the breach notification rules in the US?
Every state has its own law, so the rules depend on where your members live. The FTC says all states, the District of Columbia, Puerto Rico and the Virgin Islands have enacted legislation requiring notification of security breaches involving personal information.
Deadlines, definitions of personal information and the duty to tell a state attorney general vary. Have a US lawyer map the states that apply to your membership before you need to.
The FTC's guide adds practical steps:
- Notify law enforcement immediately, and ask whether notice to members could impede the investigation.
- Tell businesses whose accounts or data are affected, such as your payment processor.
- Name one person to release information.
What mistakes make a dating breach worse?
Weak basics before the breach, and slow or misleading communication after it. Regulators look at both.
The best-known dating case involved an affairs site. In December 2016 its operators agreed to pay a total of $1.6 million to settle FTC and state charges after a 2015 breach that exposed the data of more than 36 million people. The FTC alleged that the company had no written information security policy, no reasonable access controls, inadequate security training for employees and no monitoring of how effective its security was. It also said intruders had entered the network several times without being detected. The order required a comprehensive data security programme with third-party assessments.
The lessons apply to any dating brand:
- Write a security policy and follow it.
- Limit who can see member data, and log access.
- Check your suppliers' security, not only your own.
- Monitor, so that you find a breach quickly.
- Delete data you no longer need. Data you do not hold cannot leak. See our guide to data retention.
How do you prepare before a breach happens?
Write a plan, name the people and practise it. The UK's National Cyber Security Centre (NCSC) says incidents can and will happen, and that good preparation is what helps you deal with one well.
The NCSC says a response plan should link to your disaster recovery, business continuity and crisis management plans. A workable plan for a dating business includes:
- an incident lead and deputies, with phone numbers that work out of hours
- contacts for your lawyer, forensic firm, insurer, hosting provider and payment processor
- a list of regulators for each country you operate in
- draft notices for members, written in advance
- a breach log
- a test at least once a year
Our guide to platform security standards covers the controls that reduce the chance of needing the plan.
Who reports a breach on a white label dating site?
The controller reports, and on a shared white label network that is usually the platform. The ICO says a processor must tell the controller without undue delay as soon as it becomes aware of a breach, and that the contract should set this out.
On Dating Partners, our sister company run by the same group as this site, the platform handles hosting, software and data protection, and partners handle brand, domain and marketing. You are still responsible for data you hold yourself, such as your own email list, enquiry forms or advertising accounts. A breach of those is yours to assess and report. See our compliance page for the wider split.
If you run an app on DatingAPI, also run by our group, you may remain the controller, so the contract should say how fast the platform must tell you about an incident. DatingAPI says it is preparing for ISO 27001 certification, with a target of June 2027.
Ask any provider:
- How quickly will you tell me about a breach that affects members of my brand?
- Who reports to the regulator, and who writes to members?
- Have you had a reportable breach, and what changed afterwards?
- Which security standards are you certified against, or working towards?
Questions
Do we have to report every breach to the ICO?
No. You report when a risk to people's rights and freedoms is likely. If you decide the risk is unlikely, you do not need to report, but the ICO says you should document the decision and be able to justify it.
What if we do not know the full facts within 72 hours?
Report anyway. The ICO allows you to provide information in phases, as long as you notify on time, prioritise the investigation and send further details as soon as possible.
Is a service outage a data breach?
It can be. The ICO's definition covers the availability of personal data, but it says unavailability counts as a breach only where it has a significant negative effect on individuals.
Should we offer credit monitoring after a breach?
The FTC suggests considering at least a year of free credit monitoring or similar support, especially when financial information or Social Security numbers were exposed. For a dating breach, support against blackmail and phishing may matter more.
Should we tell the police about a breach?
The FTC's guide for US businesses says to notify law enforcement immediately. In the UK, the National Cyber Security Centre runs a service for reporting cyber incidents. Take advice on timing so that a notice to members does not harm an investigation.
Sources
- ICO: Personal data breaches, a guide, checked 21 November 2026
- FTC: Data Breach Response, a guide for business, checked 21 November 2026
- FTC: Operators of AshleyMadison.com settle FTC, state charges resulting from 2015 data breach (14 December 2016), checked 21 November 2026
- National Cyber Security Centre: Incident management, checked 21 November 2026
- Dating Partners partner terms, checked 21 November 2026
- DatingAPI, checked 21 November 2026
What changed
- : First published. Replaces our older breach response guide.