Report the issue.
Protect sensitive details.
Submit reproducible product defects through the tracked issue route. Suspected vulnerabilities should follow the protected reporting guidance.
Use one tracked
ticket form.
Use the tracked issue form so the report, evidence and follow-up conversation remain together.
Issue report form
Replace this box with your live support form widget.
Keep the form inside this container so the spacing and width remain correct.
What makes a report
actionable.
Provide exact steps, expected and actual behaviour, time, environment, impact and sanitised evidence.
Exact steps
State the page, module, actions and failure point.
Expected vs actual
Include the expected outcome and exact error text.
Time and environment
Include date, time, timezone, device and browser.
Safe references
Use ticket-safe request or transaction references.
Business impact
Explain who is affected and whether work can continue.
Sanitised evidence
Remove credentials and unnecessary personal data.
Security issue: do not post exploit details, private keys, credentials or customer databases in a general ticket. Email hi@pintoptechnologies.com with a brief non-sensitive summary and request a protected exchange route.
Give the support team enough context to investigate.
Include the affected product, environment, time of occurrence, business impact, safe reference identifiers and steps already attempted. Never send passwords, OTPs, private keys or API secrets.