Code.org Vulnerability Disclosure Policy
Code.org welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.
In-Scope Systems
This policy applies to any digital assets owned, operated, or maintained by Code.org. However, vulnerability "testing" may only be performed on in-scope Targets defined at https://bugcrowd.com/codeorg, which we’ve established for security testing purposes.
Out-of-Scope Systems
This policy does not apply to assets or other equipment not owned by Code.org. Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate asset owner, vendor, or other applicable authority.
Our Commitments
When working with us, according to this policy, you can expect us to:
- Respond to your report promptly, and work with you to understand and validate your report;
- Strive to keep you informed about the progress of our review of your report as it is processed;
- Work to remediate confirmed vulnerabilities in a timely manner, within our operational constraints; and
- Extend Safe Harbor (as explained below) for your vulnerability research that is related to this policy.
Our Expectations
In participating in our vulnerability disclosure program in good faith, we ask that you:
- Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
- Report to us any vulnerability you’ve discovered promptly;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- Provide us a reasonable amount of time (at least 180 days from the initial report) to resolve the issue before you disclose it publicly;
- Perform testing only on in-scope Targets defined at https://bugcrowd.com/codeorg, which we’ve established for security testing purposes (i.e., do not perform test procedures on our production environments where the testing could result in disruption or data loss) and respect systems and activities which are out-of-scope;
- If a vulnerability provides unintended access to data, we ask that you limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), user project data, or proprietary information;
- You should only interact with test accounts you own or with explicit permission from the account holder; and
- Do not engage in extortion.
Official Channels
Please report security issues via our bug bounty program: https://bugcrowd.com/codeorg, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue. If you identify an issue or concern that does not appear to fall within the bug bounty program but you wish to report anyway, you may email us at security@code.org. Please note, however, no bug bounties will be paid for any issue that is not reported via https://bugcrowd.com/codeorg.
Safe Harbor
When conducting vulnerability research, according to this policy, we will consider such research to be:
- Authorized to the extent it might implicate any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
- Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms of Service (TOS) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that we believe your actions were conducted in compliance with this policy.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
Note that the Safe Harbor applies only to legal claims under the control of Code.org, and that the policy does not bind independent third parties.
Additional resources
Privacy Policy
Your privacy is important to us. We want to be transparent about the personal data we collect, why we collect it, and what we do with it.
Cookie Policy
Learn how Code.org uses cookies to enhance site performance and personalize your experience. Plus, manage your cookie settings.
Terms of Service
Review our Terms of Service for using Code.org’s platform, tools, and curriculum, including legal terms and user responsibilities.