> ## Documentation Index
> Fetch the complete documentation index at: https://developers.callaro.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Responsible Disclosure

> Learn how to report security findings safely and what information should accompany a report.

# Report potential security issues privately with enough detail for reproduction and triage.

Include a clear issue summary, reproduction steps, impact assessment, and safe proof-of-concept details.

## How to report

1. Submit your report through your existing Callaro support/security channel.
2. Include affected endpoint/page/environment details.
3. Share minimal reproducible steps and expected-versus-actual behavior.
4. Provide potential impact severity and affected customer scope.
5. Include your preferred contact details for follow-up.

## What to include in a high-quality report

* Vulnerability type and affected component.
* Reproduction sequence with request examples where applicable.
* Security impact (confidentiality, integrity, availability).
* Mitigations already tested on your side.
* Suggested remediation if known.

## Response workflow

* Triage acknowledgment from the security team.
* Severity assessment and fix prioritization.
* Remediation progress updates for validated findings.
* Closure and guidance for any required customer-side action.

<Warning>Do not perform destructive testing or access data you are not authorized to view.</Warning>