TECHNICAL SUPPORT / RESPONSIBLE DISCLOSURE
Report the issue once. Route it correctly.
Use one intake for technical defects, incidents, API problems and security reports. Security reports are triaged separately and should contain only the minimum evidence needed to reproduce safely.
Ticket reference Severity routing Security triage No credentials
Responsible disclosure
Send reproducible, minimal-impact findings. Avoid accessing unrelated data or disrupting availability.
P1
Critical
Active compromise, exposed credentials or broad data access.
Active compromise, exposed credentials or broad data access.
P2
High
Significant security or production impact without active compromise.
Significant security or production impact without active compromise.
P3
Normal
Functional defect with a workaround or limited scope.
Functional defect with a workaround or limited scope.
P4
Low
Cosmetic, documentation or low-impact improvement.
Cosmetic, documentation or low-impact improvement.
What happens next?
Submission → validation → reference → category routing → triage. Staff-only actions and internal notes stay in the protected Helpdesk workspace.
Helpdesk