If you believe you’ve found a security issue, please report it responsibly. We take security seriously and will respond as quickly as practical.
Responsible reporting
What happens next
Security reports are handled with practical triage, impact assessment and follow-up rather than generic inbox silence.
We review incoming security reports and confirm we have enough information to investigate.
We assess impact, reproduction steps, affected areas and whether customer data or service availability is involved.
We prioritise fixes based on severity and coordinate internal engineering, support and customer communication where needed.
We follow up with practical status, remediation notes or disclosure coordination when appropriate.
If you follow the guidelines above, act in good faith, avoid accessing data that is not yours, and give us a reasonable time to investigate and remediate, we will treat your report as a responsible disclosure.
For enterprise customers and security researchers who need coordinated testing, contact us first and we’ll agree scope and environment.
Responsible disclosure should feel precise. These surfaces show how a report can reference the affected route, avoid customer data and move into remediation.
Secure Workspace
What you found and where (URL/path, screenshots if helpful)
Controlled Files
Do not access data that is not yours
Response Path
Remediate
Secure Workspace
Reports are easier to triage when they reference the exact workspace surface, route or data boundary involved.
Disclosure workflow anchor
What you found and where (URL/path, screenshots if helpful)
Controlled Files
Responsible disclosure guidance stays practical by asking for minimal proof and clear reproduction steps.
Disclosure workflow anchor
Do not access data that is not yours
Response Path
The response process maps to triage, impact review and follow-up so security reports have a visible route.
Disclosure workflow anchor
Remediate
Disclosure Control
Responsible disclosure is a trust surface. This layer keeps the reporting address, evidence expectations, safe boundaries and response path visible in one focused review band.
Report route
Make the security inbox unmistakable for sensitive findings and follow-up.
Evidence
Ask for reproducible detail without customer data, disruption or broad scanning.
Boundaries
Set clear rules for safe testing, disclosure timing and service protection.
Response
Show how a report moves from acknowledgement into impact review and remediation.
The vulnerability reporting page pairs reporting guidance with a visible operational path: route the issue, protect the record and keep follow-up accountable.
Give teams a clear path to status, support, recovery or security without hunting through the site.
Keep operational guidance connected to the documents, evidence and controls that matter on live work.
Help users get back to the app, the right page or the right contact route with less friction.
