Legal Posture

Dropzone will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting email (sirt-report@dropzone.ai). We openly accept reports for the the currently-offered Dropzone products. We agree not to pursue legal action against individuals who:

• Engage in testing of systems/research without harming Dropzone or its customers.
• Engage in vulnerability testing within the scope of our vulnerability disclosure program.
• Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software, etc.
• Adhere to the applicable laws of their location and of the location of Dropzone. For example, violating laws that would only result in a claim by Dropzone (and not a criminal claim) may be acceptable as Dropzone is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.
• Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.

How to Submit a Vulnerability

To submit a vulnerability report to Dropzone’s Product Security Team, please utilize the following email: sirt-report@dropzone.ai.

Preference, Prioritization, and Acceptance Criteria

We will use the following criteria/guidelines to prioritize and triage submissions:

• Well-written reports in English will have a higher probability of resolution.
• Reports that include proof-of-concept code equip us to better triage.
• Reports that include only crash dumps or other automated tool output may receive lower priority.
• Reports that include products not on the initial scope list may receive lower priority.
• Please include how you found the bug, the impact, and any potential remediation.
• Please include any plans or intentions for public disclosure.

What you can expect from Dropzone

• A timely response to your email (within 2 business days).
• After triage, we will send an expected timeline, and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.
• An open dialog to discuss issues.
• Notification when the vulnerability analysis has completed each stage of our review.
• Credit after the vulnerability has been validated and fixed. If we are unable to resolve communication issues or other problems, Dropzone may bring in a neutral third party to assist in determining how best to handle the vulnerability.