<ahref=#scope>services available</a>)</p><h2id=rules>Rules:<ahref=#rulesclass=anchoraria-hidden=true>#</a></h2><h3id=before-you-start>Before you start<ahref=#before-you-startclass=anchoraria-hidden=true>#</a></h3><ul><li><p>Check the list of domains that are in scope for security research
and the list of targets for useful information for getting started.</p></li><li><p>Check the list of bugs that have been classified as ineligible.</p></li><li><p>Check our changelog(in our GitHub repositories) for recently launched
features.</p></li><li><p>Never attempt non-technical attacks such as social engineering,
phishing, or physical attacks against our employees, users, or
infrastructure.</p></li></ul><p>When in doubt, contact
me(<ahref=/contributors/aravinth-manivannan/>@realaravinth</a>) at
<ahref=mailto:realaravinth@batsense.net>realaravinth@batense.net</a>.</p><h3id=performing-your-research>Performing your research<ahref=#performing-your-researchclass=anchoraria-hidden=true>#</a></h3><ul><li><p>Do not impact other users with your testing, this includes testing
vulnerabilities with CAPTCHA credentials and account credentials
automated tools which produce excessive amounts of traffic.</p><p>Note: We do allow the use of automated tools so long as they do
not produce excessive amounts of traffic. For example, running
one nmap scan against one host is allowed, but sending 65,000
requests in two minutes using Burp Suite Intruder is excessive.</p></li></ul></li><li><p>Researching denial-of-service attacks is allowed only if you follow
these rules:</p><ul><li><p>There are no limits for researching denial of service
<ahref=https://mcaptcha.org>https://mcaptcha.org</a> or <ahref=https://mcaptcha.io>https://mcaptcha.io</a>):</p><ul><li>Research must be performed using credentials you own.</li><li>Stop immediately if you believe you have affected the
availability of our services. Don’t worry about demonstrating
the full impact of your vulnerability, our team
will be able to determine the impact.</li></ul></li></ul></li></ul><h3id=handling-personally-identifiable-information-pii>Handling personally identifiable information (PII)<ahref=#handling-personally-identifiable-information-piiclass=anchoraria-hidden=true>#</a></h3><ul><li><p>Personally identifying information (PII) includes:</p><ul><li>legal and/or full names</li><li>names or usernames combined with other identifiers like phone numbers or email addresses</li><li>health or financial information (including insurance information, social security numbers, etc.)</li><li>information about political or religious affiliations</li><li>information about race, ethnicity, sexual orientation, gender, or other identifying information that could be used for discriminatory purposes</li></ul></li><li><p>Do not intentionally access others’ PII. If you suspect a service
provides access to PII, limit queries to your own personal
information.</p></li><li><p>Report the vulnerability immediately and do not attempt to access any
other data. We will assess the scope and impact of the PII exposure.</p></li><li><p>Limit the amount of data returned from services. For SQL injection,
for example, limit the number of rows returned</p></li><li><p>You must delete all your local, stored, or cached copies of data
containing PII as soon as possible. We may ask you to sign a
certificate of deletion and confidentiality agreement regarding the
exact information you accessed. We may ask you for the usernames and
IP addresses used during your testing to assess the impact of the
vulnerability.</p></li></ul><h3id=reporting-your-vulnerability>Reporting your vulnerability<ahref=#reporting-your-vulnerabilityclass=anchoraria-hidden=true>#</a></h3><ul><li><p>Reports must include written instructions for reproducing the
vulnerability.</p></li><li><p>When reporting vulnerabilities you must keep all information on
restricted to email correspondence with us. Do not post information to
video-sharing or pastebin sites.</p></li><li><p>For vulnerabilities involving personally identifiable information,
been publicly made available.</p></li></ul><h3id=legal-safe-harbor>Legal safe harbor:<ahref=#legal-safe-harborclass=anchoraria-hidden=true>#</a></h3><p>We currently don’t have any legal policies in place but rest assured
that as long as your research adheres to the above rules, your security
research and vulnerability disclosure activities are considered as
“authorized”.</p><p>A detailed policy based on this sentiment is in the works.</p><h2id=scope>Scope:<ahref=#scopeclass=anchoraria-hidden=true>#</a></h2><p>mCaptcha runs a number of services. Only domains listed below are are
