Coordinated Vulnerability Disclosure Policy
Reporting a vulnerability? Email
[email protected]
with the subject line SECURITY. You will get a human acknowledgement
within 3 business days. Please do not open a public issue.
This policy covers software and services we operate:
The following are out of scope, because we do not control them:
If you make a good-faith effort to follow this policy, we will not pursue or support legal action against you for your research, and we will treat your report as authorised access. If a third party brings action against you for activity that complied with this policy, we will make that compliance clear. Good faith is judged on your conduct, not the severity of what you find.
This safe-harbour commitment does not extend to accessing other people's personal data beyond the minimum needed to demonstrate a finding, to extortion, or to destroying data.
| Stage | Our commitment |
|---|---|
| Acknowledgement | Within 3 business days |
| Initial assessment | Within 10 business days: validity and severity |
| Progress updates | At least every 14 days while the report is open |
| Fix for critical issues | Targeted within 30 days of confirmation |
| Credit | Named in our release notes if you want it; anonymous if you prefer |
We do not currently operate a paid bug bounty. We would rather say so plainly than imply a reward that does not exist. Every valid report gets a written response and, with your consent, public credit.
Where a vulnerability you report is being actively exploited, or an incident materially affects the security of EchoDrop, we notify the relevant authorities on the statutory timeline, including, for users in the European Union, reporting through the ENISA single reporting platform under the Cyber Resilience Act, and notifying affected users and supervisory authorities under the GDPR where a personal data breach is involved. Your report may form part of such a notification; we will not name you to a regulator without asking you first.
This policy is referenced from our
/.well-known/security.txt, published per
RFC 9116.