What to include
- The affected route, integration, or component
- Reproduction steps
- Expected behavior
- Observed behavior
- Potential security impact
- Non-sensitive screenshots or technical details where helpful
Security reporting
Report a potential vulnerability.
Send enough information for us to understand and reproduce the issue without accessing customer data or disrupting the service.
Testing boundaries
- Do not access or modify customer data
- Do not include credentials or authentication tokens
- Do not perform destructive testing
- Do not degrade service availability
- Do not use social engineering
- Stop testing when unintended access to sensitive information becomes possible
Submit a report
Use the security-reporting form so the request is routed separately from product sales. No response-time commitment is stated.