║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║

---

title: Vulnerability disclosure policy description: Clerk's vulnerability disclosure policy.

Guidelines

We require that all researchers:

1. Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
2. Perform research only within the scope set out below.
3. Use the identified communication channels to report vulnerability information to us.
4. Keep information about any vulnerabilities you've discovered confidential between yourself and Clerk, Inc. until we've had 90 days to resolve the issue.

If you follow these guidelines when reporting an issue to us, we commit to:

• Not pursue or support any legal action related to your research;
• Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 3 business days of submission);

Scope

• https://dashboard.clerk.com
• https://accounts.clerk.com
• https://api.clerk.com
• https://clerk.clerk.com
• Production instances created on https://dashboard.clerk.com

Out of scope

Any services hosted by 3rd party providers and services are excluded from scope. These services include:

• https://clerk.com

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 in Development or Staging instances created on https://dashboard.clerk.com
• Findings from physical testing such as office access (e.g. open doors, tailgating)
• Findings derived primarily from social engineering (e.g. phishing, vishing)
• Findings from applications or systems not listed in the ‘Scope’ section
• UI and UX bugs and spelling mistakes
• Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive

• Personally identifiable information (PII)
• Credit card holder data

How to report a security vulnerability

If you believe you've found a security vulnerability in one of our products or platforms send it to us by emailing security@clerk.dev. 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 (POC scripts, screenshots, and compressed screen captures are all helpful to us).

║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║