Secure Workspace
Give researchers the right product context.
Reports are easier to triage when they reference the exact workspace surface, route or data boundary involved.
Security
Vulnerability reporting and responsible disclosure.
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
Disclosure route
A clear path for good-faith security researchers, buyers and administrators.ReportSecurity issue
ScopeGood faith
Follow-upsecurity@zektrx.com
What to include
- ✓ What you found and where (URL/path, screenshots if helpful)
- ✓ Steps to reproduce (clear and minimal)
- ✓ What you expected vs what happened
- ✓ Any proof-of-concept data that avoids real customer data
- ✓ Your preferred contact details for follow-up
What not to do
- • Do not access data that is not yours
- • Do not disrupt service (no denial-of-service testing)
- • Do not use automated scanning against production without permission
- • Do not publicly disclose before we have a chance to investigate and fix
- • Do not include sensitive personal data in your report
What happens next
A clearer response path for responsible reports.
Security reports are handled with practical triage, impact assessment and follow-up rather than generic inbox silence.
01
Acknowledge
We review incoming security reports and confirm we have enough information to investigate.
02
Triage
We assess impact, reproduction steps, affected areas and whether customer data or service availability is involved.
03
Remediate
We prioritise fixes based on severity and coordinate internal engineering, support and customer communication where needed.
04
Close the loop
We follow up with practical status, remediation notes or disclosure coordination when appropriate.
Safe harbour (good-faith)
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
Make security reports easier to route and verify.
Submit a precise report that identifies the affected area, avoids customer data and gives our team the evidence needed to investigate.
Controlled Files
Protect evidence without touching customer data.
Responsible disclosure guidance stays practical by asking for minimal proof and clear reproduction steps.
Response Path
Track your security report.
The response process maps to triage, impact review and follow-up so security reports have a visible route.
Reporting Guidance
A security report path that feels deliberate.
Find the reporting address, evidence requirements, safe testing boundaries and what to expect after you submit a report.
1
Report route
security@zektrx.com
Make the security inbox unmistakable for sensitive findings and follow-up.
2
Evidence
Minimal proof
Ask for reproducible detail without customer data, disruption or broad scanning.
3
Boundaries
Good faith
Set clear rules for safe testing, disclosure timing and service protection.
4
Response
Triage to fix
Show how a report moves from acknowledgement into impact review and remediation.
Report To Response
Report a security concern responsibly.
Send security concerns to the reporting contact above, including the affected area and steps to reproduce the issue.
Route the issue
Give teams a clear path to status, support, recovery or security without hunting through the site.
Protect the record
Keep operational guidance connected to the documents, evidence and controls that matter on live work.
Return to work
Help users get back to the app, the right page or the right contact route with less friction.