• Please use your own account for testing or research purposes. Do not attempt to gain access to another user’s account or confidential information.
• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
• Social engineering (e.g. phishing, vishing, smishing) is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
• Please do not test for spam, social engineering, or denial of service issues.
• Please do not engage in any activity that can potentially or actually cause harm to Adobe, our customers, or our employees.
• Do not engage in any activity that violates (a) federal or state laws or regulations or (b) the laws or regulations of any country where (i) data, assets, or systems reside, (ii) data traffic is routed, or (iii) the researcher is conducting research activity.
• Do not store, share, compromise, or destroy Adobe or customer data. If Personally Identifiable Information (PII) is encountered, you should immediately halt your activity, purge related data from your system, and immediately contact Adobe. This step protects any potentially vulnerable data, and you.

Some vulnerabilities are out of scope for the live hacking event. Please review the full list in the “Program exclusions” section of the policy page – https://hackerone.com/adobe?type=team#user-content-program-exclusions along with the testing plan for each product in scope before submitting any reports.