Bug Bounty Policy (December 31, 2016)

December 31, 2016 -

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. However, some of our products are in beta, so we do expect a large volume of changes in our code and may already be aware of the issue. If you submit a report for a known issue, we will do our best to let you know quickly so you can move on.

Rules

In the words of Cesar Millan: “no talk, no touch, no eye contact”. Basically, use good judgment (except as outlined below in “Destructive/Invasive Attacks”).

As long as your research stays within the bounds of the criteria in this policy, we welcome the dialogue and promise not to take legal action.

Report Focus & Tips

We are particularly interested in problems that allow unauthorized access to other user’s documents and will award monetary bounties accordingly. However, YOU MUST ONLY ATTEMPT THIS IN OUR NON-PRODUCTION ENVIRONMENT (legalrobot-uat.com).

Our www subdomain only hosts static, non-sensitive content like our blog and marketing pages, so many attacks against this subdomain are unlikely to result in a bounty. We suggest that you focus your efforts on our app subdomain.

We proudly use Stripe as our payment processor. To simulate a payment and gain access to a paid-only section of our app, we suggest you work in our non-production environment (legalrobot-uat.com) and check out the Stripe testing documentation which has test credit card numbers.

If you accidentally perform a live transaction, just let us know at hello@legalrobot.com and we’ll make things right. Security researchers that dispute a live transaction will be immediately banned from our HackerOne program and will no longer be exempted from legal action. We may take further action outside of this policy (but always in accordance with our terms of service).

Destructive/Invasive Attacks

We provide a non-production environment (legalrobot-uat.com) that you may use for destructive and invasive attacks. All of the data in this environment is non-sensitive, so have at it… just DO NOT do anything illegal, or launch an extended denial-of-service or similar attack that could disrupt or get us blacklisted with our service providers (keep any DoS attempts short… like, under a few minutes). Because legalrobot-uat.com is not a full production environment, DMARC, SPF, and similar email issues will not be eligible. To be clear, issues that exist on the legalrobot-uat.com domain but not on legalrobot.com will not be accepted.

Ineligible Reports

You must be the first person to report the issue to us. If a duplicate reproduction is submitted while the vulnerability is still in the wild, we will only award a bounty if the duplicate submissions provide more information or show the issue to be more extensive.

Questions

For any questions or clarification on this policy, feel free to email us at hello@legalrobot.com or ask us inside the app through the Intercom chat window (bottom right corner when logged in). All security reports must be performed through HackerOne so we can track reports and compensate you.

Thanks & Compensation

We believe in recognizing the work of others. If your work helps us improve the security of our service, we’d be happy to acknowledge your contribution. In addition to showing our appreciation for our security researchers, we also offer a monetary bounty for security issues, provided you follow the rules. More serious issues will be rewarded appropriately. Many researchers find similar or identical issues at the same time so unfortunately, duplicate issues will only receive our appreciation.