From High Intent Media, the group behind Smooch, Just Singles, Dating Partners and DatingAPI. We say where our products fit, and where they do not.Facts and sources
Talk to us
Guide · Rules and safety

Bug bounty and vulnerability disclosure for dating sites

Short answer

Every dating site should publish a vulnerability disclosure policy: a page and a security.txt file telling security researchers how to report a flaw and what to expect. A paid bug bounty is optional and suits teams that can fix reports quickly. On a white label platform, the platform owns the code, so reports must reach it.

By the White Label Dating teamLast checked 7 minute read

This site is run by High Intent Media, which also runs Dating Partners and DatingAPI. Both may be mentioned on this page. Editorial policy

What is the difference between a disclosure policy and a bug bounty?

A vulnerability disclosure policy tells outsiders how to report a security flaw, and a bug bounty pays them to go looking for one. HackerOne, which runs both kinds for its customers, puts it this way: a policy sets out how an organisation prefers to receive reports, and a bounty gives people an incentive to find flaws and report them directly.

Vulnerability disclosure policyBug bounty
PurposeA safe, clear route for anyone who notices a flawPaid encouragement to search for flaws
MoneyNo rewards. Thanks or public creditCash rewards, on a scale you set
Open toEveryone, published on your sitePublic, or private by invitation
Work to runA page, an inbox and someone to answerReward budget, scope, response targets, triage
SuitsEvery dating site and appTeams that can confirm and fix reports quickly

A dating service holds private messages, photos, location and often details of sexuality or faith. A flaw that exposes them hurts members directly. A reporting route means the person who finds a flaw can tell you before anyone else finds it. Our guide to GDPR for dating sites explains why this data needs extra care.

Does a dating site need a bug bounty?

No. A dating site needs a disclosure policy, and a paid bounty is a later step that only some teams should take.

A bounty brings a stream of reports, including duplicates and low-value ones, and each needs a reply. HackerOne's own documentation says bounties are more complex to run, with more to set up, such as a reward structure and response targets. If you cannot confirm and fix a serious report within days, paying people to send you more of them does not make members safer.

A sensible order for a growing dating brand:

  1. Publish a disclosure policy and a security.txt file.
  2. Commission penetration tests on a schedule. See our guide to platform security standards.
  3. Run a private bounty, by invitation, once fixes ship reliably.
  4. Open the bounty to the public only when the private one runs smoothly.

What should a vulnerability disclosure policy say?

It should say how to contact you, what to send, what you will do and what is in scope. Those points come from the Vulnerability Disclosure Toolkit published by the UK's National Cyber Security Centre (NCSC), which is the best free starting point.

The NCSC lists what a policy should contain:

  • How you want to be contacted, and a secure way to do it. It prefers a web form to an email address.
  • What information a report should include.
  • What the finder can expect to happen next.
  • What is in scope and what is not.

Its sample policy gives timings you can adopt: a response within 5 working days and triage within 10 working days. It asks finders not to chase for updates more than once every 14 days. It also asks them to delete any data they retrieved once the flaw is fixed, which matters a great deal when that data is members' profiles.

Add a promise not to pursue people who follow the policy. HackerOne lists this "safe harbor" statement as a standard part of a policy. The NCSC also advises against asking finders to sign documents such as non-disclosure agreements. Have a lawyer check the wording.

What is security.txt and where does it go?

It is a small text file that tells researchers where to send a report, and it sits at /.well-known/security.txt on your domain. The format is set out in RFC 9116, published in April 2022.

Two fields are required: Contact, which gives the reporting address or page, and Expires, which says when the file goes out of date. The RFC recommends an expiry date less than a year ahead, so put a renewal in the calendar. Optional fields include Policy (a link to your disclosure policy), Encryption, Acknowledgments and Preferred-Languages. The file must be served over HTTPS.

The NCSC toolkit says to place the file on each domain and subdomain. If you run several dating brands, each one needs its own copy.

How should you handle a report when one arrives?

Acknowledge it quickly, pass it to the person who can fix it, and keep the finder informed until it is closed. The NCSC's advice comes down to six steps:

  1. Do not ignore it. Reply promptly and thank the finder.
  2. Give the report a reference number and send it to whoever owns the affected system.
  3. Ask politely for more detail if you need it.
  4. Tell the finder when the issue is being worked on, and update them if the fix takes time.
  5. Tell them when it is fixed.
  6. Consider thanking them in public, if they agree.

Check early whether personal data was exposed. If it was, the report may also be a personal data breach. The Information Commissioner's Office says a notifiable breach must be reported within 72 hours of discovering it, and that every breach must be recorded whether or not it is reported. Our guide to dating breach response covers that process.

How do the large dating apps do it?

The largest apps run bounties through a specialist platform and say little in public about the terms. This is what their own pages state.

AppWhat its page saysNot published there
TinderReports go through a bug bounty on HackerOne. Researchers are asked not to share details until Tinder has reviewed and addressed the issue.Scope and reward amounts
HingeReports go through a bug bounty on HackerOne. Denial of service testing and automated scanning tools are prohibited.Reward amounts
GrindrLaunched a bounty with HackerOne in October 2020, to complement its third-party penetration tests.Scope and reward amounts in the announcement

A bounty does not cover every risk. In January 2026 Bitdefender reported a security incident at Match Group in which attackers were said to have compromised a single sign-on account, not exploited a software flaw. Staff access controls and monitoring matter as much as code.

It depends on the country and on what they do, which is why your policy should spell out what you allow. This section is general information, not legal advice.

In the US, the Department of Justice changed its charging policy on 19 May 2022. Morrison Foerster's summary says the department will not charge good-faith security research under the Computer Fraud and Abuse Act. That means accessing a computer only to test, investigate or fix a flaw, in a way designed to avoid harm. Using a discovered flaw for extortion is not good faith and can still be charged.

That policy guides federal prosecutors. It does not write your terms for you. A clear scope, a ban on reading or keeping member data beyond what proves the flaw, and a safe harbour promise give honest researchers the confidence to report.

Who handles vulnerability reports on a white label platform?

The platform does, because it owns the code and the servers. Your job as the brand owner is to make sure a report that lands in your inbox reaches the platform the same day.

Dating Partners, our sister company run by the same group as this site, runs hosting, software and data protection for its partners' websites, so fixes are made once for every brand. DatingAPI, also run by our group, does the same for apps and is preparing for ISO 27001 certification, with a target of June 2027. Neither publishes a paid bounty that we can cite here, so ask us the questions below, as you would ask any provider. Our compliance page sets out what the platform covers.

  • Do you publish a disclosure policy and a security.txt file?
  • Where should I forward a report that reaches my brand?
  • How quickly do you acknowledge and triage reports?
  • How often do you commission penetration tests, and can I see a summary?
  • Will you tell me if a report affects my members' data?

For the wider picture of audits and certificates, see our guide to dating auditing and certification.

Questions

How much should a bug bounty pay?

There is no standard rate, and the large dating apps do not print their reward tables on their own security pages. Look at the public listings on the bounty platforms for services of your size before you set a budget.

Is a bug bounty the same as a penetration test?

No. A penetration test is a paid, time-limited review by a firm you choose. A bounty is open-ended and pays outside researchers for what they find. Grindr describes its bounty as a complement to its penetration tests.

Do I have to answer every report?

Yes, at least to acknowledge it. The UK's National Cyber Security Centre tells organisations not to ignore reports, to thank the finder and to keep them updated.

What if a researcher asks for money and I have no bounty?

Point to your policy. The National Cyber Security Centre's sample policy states that no monetary rewards are offered, and a thank-you page is a common alternative. A demand backed by a threat is extortion, so take legal advice.

Should the policy cover member reports about other members?

No. Keep security reports separate from safety reports. Tinder's security page sends profile problems and member reports to its support team, not to the bounty.

Sources

  1. NCSC: Vulnerability Disclosure Toolkit, version 2, checked 20 November 2026
  2. RFC 9116: A File Format to Aid in Security Vulnerability Disclosure, checked 20 November 2026
  3. HackerOne documentation: VDP vs BBP, checked 20 November 2026
  4. Tinder: Security at Tinder, checked 20 November 2026
  5. Hinge: Security, checked 20 November 2026
  6. Grindr: Grindr Launches Bug Bounty Program in Partnership With HackerOne, checked 20 November 2026
  7. Bitdefender: Breach at Tinder, Hinge and OkCupid parent Match Group exposes user data, checked 20 November 2026
  8. Morrison Foerster: Justice Department revises cyber crime charging policy to shield good-faith security research, checked 20 November 2026
  9. ICO: Personal data breaches, a guide, checked 20 November 2026
  10. DatingAPI, checked 20 November 2026

What changed

  • : First published. Replaces our older guide on dating bug bounties and vulnerability disclosure.

Tell us what you want to launch

A named person replies within one working day. No account, no newsletter.

Talk to us