Vulnerability Disclosure Policy

Guidelines 

We require that all security researchers:

• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
• Use the identified communication channels to report vulnerability information to us; and
• Keep information about any vulnerabilities you’ve discovered confidential between yourself and Class Creator until we’ve had 90 days to resolve the issue.

By following these guidelines when reporting an issue to us, we commit to work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission). We do not provide compensation for reporting such issues.

In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:

• Findings from physical testing such as office access (e.g. open doors, tailgating);
• Findings derived primarily from social engineering (e.g. phishing, vishing);
• UI and UX bugs and spelling mistakes; and
• Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive:

• Any personally identifiable information (PII)

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms please use this link.

Please include the following details with your report:

• Description of the location and potential impact of the vulnerability; and
• A detailed description of the steps required to reproduce the vulnerability (proof of concept scripts, screenshots, and compressed screen captures are all helpful to us).

Please do not disclose your security research that relates to Class Creator until we have finished addressing the vulnerability.