Security disclosure policy

Ronski is a dating app for gay, bi and queer men. Our members trust us with sensitive information, so we want to hear about security problems and we promise to treat people who report them in good faith fairly.

How to report

What we promise (response times)

StepTarget
We confirm we received your reportwithin 3 working days
First assessment and severitywithin 7 days
Status updateat least every 14 days until it is resolved
Fix for a critical or high issueas fast as we can, aiming for 30 days
Crediton request, once the issue is fixed (see below)

Ronski is run by a very small team, so these are targets, not guarantees. If we are slow, please nudge us.

Safe harbour

If you act in good faith and follow this policy we will not start or support legal action against you, and we will not ask a hosting provider or the police to act against you, for the research you describe in your report. In particular, we consider the following authorised:

This safe harbour covers Ronski's own systems. It cannot bind third parties (for example our hosting and infrastructure providers) and it does not let you break the law in ways unrelated to the research. If a third party starts action against you for research that followed this policy, we will say publicly that you acted with our permission.

Rules for researchers

Please do not:

Scope

In scope: the Ronski API and admin console on our own domains, the Ronski mobile app, and the public site ronski.app.

Out of scope: findings that only exist in third-party services (Cloudflare, Oracle Cloud, Microsoft Azure, Expo, Zoho) which should be reported to those providers; missing best-practice headers without a demonstrated impact; reports from automated scanners with no proof of impact; and vulnerabilities in outdated apps or devices.

Rewards and credit

We cannot pay bounties. We can thank you by name on a hall-of-fame list if you wish, and we will tell you when the fix is out.

Our side

We keep reports confidential, use your details only to handle the report, and tell you the outcome. If the problem put member data at risk we follow our breach procedure and notify the Data Protection Ombudsman and members as the law requires.

This page is machine-readable via security.txt (RFC 9116). The policy link in that file points here (SECURITY_POLICY_URL).