If you believe you have found a security vulnerability in Legal Robot, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly fix the problem. As long as your research stays within the bounds of this policy, we welcome the dialog, promise not to take legal action for covered activities, and hope that we can compensate you for your efforts to make our products more secure.
All of the data in our non-production environment (legalrobot-uat.com) is non-sensitive, so have at it… just DO NOT do anything illegal, launch a DDoS attack, or anything else that could disrupt or get us blacklisted with our service providers. Because legalrobot-uat.com is not a full production environment, DMARC, SPF, and similar email issues will not be eligible there. Issues that we cannot reproduce in production (legalrobot.com) will not be accepted.
In the interest of transparency, it is our policy to at least ask for disclosure on all reports, but it is not necessary for Informative/Not Applicable/Duplicate, only Resolved reports - even then, we’re happy to do Limited Disclosure or delay for a good reason. In order to hold ourselves to a high standard, we’ll also do Full Disclosure if there is a possibility that we’ve been unfair to a researcher (marked as Spam, Locked Report, etc).
We want to show that we respect your work, so we will only close a report as a Duplicate with a link to the original report or to a previous public disclosure.
To encourage responsible disclosures, we will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy by legitimate security researchers. We consider security research and vulnerability disclosure activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA), the Digital Millennium Copyright Act (DMCA) and applicable anti-hacking laws such as Cal. Penal Code 502(c). We waive any DMCA claim against legitimate security researchers for circumventing the technological measures we have used to protect the applications in scope.
In case of any conflict between the terms of this policy and our Terms of Service, this policy will prevail.
If legal action is initiated by a third party against you and you are a legitimate security researcher that has complied with this policy, we will make it known that your actions were conducted in compliance with this policy. Contact us at firstname.lastname@example.org for assistance.
Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party may determine whether to pursue legal action. We cannot and do not authorize security research in the name of other entities.
You are expected, as always, to comply with all applicable laws.
Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.
Always feel free to ping us at email@example.com if you have any questions or want to check if we already know about an issue before you go to the trouble of creating a full PoC and bug report on HackerOne.
We believe in recognizing the work of others. If your work helps us improve the security of our service, we will happily acknowledge your contribution. We also offer a monetary bounty of $20-$???? for legitimate, non-duplicate security issues reported through HackerOne, provided you follow these rules. More serious issues will be rewarded appropriately.