Responsible Disclosure Policy
We take the security of our systems seriously, and we value the security community. But no matter how much effort we put into system security, there can still be vulnerabilities present.
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. Please follow the following guidelines when investigating and reporting vulnerabilities:
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
- If you are using an automated tool to uncover vulnerabilities, please limit your requests to 2 per second.
- Use the identified communication channels to report vulnerability information to us; and
- Keep information about any vulnerabilities you’ve discovered confidential between yourself and BoardGameGeek until we’ve had 90 days to resolve the issue.
If you follow these guidelines when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research;
- Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);
- At our discretion, we may offer you a cash or voucher reward if you are the first to report the issue and we make a code or configuration change based on the issue.
boardgamegeek.com, rpggeek.com, videogamegeek.com, geekdo.com, bgg.cc, and any subdomains of geekdo.com (but not subdomains other than "www" of the other domains).
Out of Scope
3rd party providers and services are excluded from scope.
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Denial of Service (DoS/DDoS) vulnerabilities
- In addition, issues that are bugs but not actual security vulnerabilities are generally not eligible for bounties.
Things we do not want to receive:
- Personally identifiable information (PII).
Reporting a vulnerability
If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing email@example.com. Please include the following details with your report:
- Description of the location and potential impact of the vulnerability;
- A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us);
We prefer that you contact us initially by unencrypted email, but if you feel that the information must be encrypted, please use our PGP Key
. Its fingerprint is:
F89B B1FA 6F11 66FC 63F9 2AB8 86B9 8A3F 626C 75FA