---
title: Vulnerability disclosure policy
description: Our guidelines and commitment for working with the security community to report and resolve vulnerabilities.
---

At Avra, we consider the security of our systems a top priority. We value the essential role the security community plays in helping us protect our platform and our customers. We are committed to working with skilled, good-faith researchers to identify and resolve vulnerabilities in a responsible and timely manner.

If you have discovered a security vulnerability, we encourage you to report it to us privately. We will work with you to understand and resolve the issue promptly.

## Reporting a Vulnerability

Please report any potential vulnerabilities to our security team via email: `security@avra.ai`

To help us investigate efficiently, please describe the vulnerability clearly in your report, including its potential impact. Include detailed steps to reproduce the issue, with any URLs, request/response captures, or proof-of-concept code. Add your contact information and, if you wish, a link to a public profile for recognition.

## What to Expect (Our Commitment)

When you report a vulnerability in accordance with this policy, we promise to:

1. **Triage**

    Acknowledge receipt of your report.

2. **Investigation**

    Validate and investigate your report. We may contact you for additional
    information if needed.

3. **Communication**

    Provide status updates as we work on a fix, keeping you informed of our
    progress.

4. **Resolution**

    Notify you when the vulnerability has been resolved.

5. **Recognition**

    With your permission, credit you for the report. We value your work and
    believe in giving credit where it is due.

## Rules of Engagement

To ensure the process is safe and productive for everyone, we ask that you adhere to the following guidelines.

Please report any vulnerability you've discovered promptly and privately. Avoid privacy violations, destruction of data, and interruption or degradation of our service during your testing. Make a good-faith effort to avoid accessing or modifying data that does not belong to you. If you encounter any non-public user or company data, stop your test and report it immediately.

Please do not perform any actions that could negatively affect Avra's users, such as Denial of Service (DoS), spamming, or social engineering (phishing). Do not access or attempt to access data that does not belong to you beyond what is necessary to demonstrate the vulnerability. Do not disclose any vulnerabilities to the public or third parties without our express written consent. Do not attempt physical attacks against Avra employees, offices, or data centers.

## Safe Harbor

Avra is committed to protecting security researchers. If you comply with this policy during your security research, we will consider your research to be authorized. **We will not initiate legal action or a law enforcement investigation against you in response to your report.**

We will work with you to understand and resolve the issue quickly, and we will not engage in legal action for accidental, good-faith violations of this policy.

## Scope

This policy applies to all systems and services owned and operated by Avra. The in-scope assets are `*.avra.ai` (including subdomains), `app.avra.ai`, and `api.avra.ai`.

### Out-of-Scope Vulnerabilities:

While we encourage any reports that could have a security impact, the following issues are generally considered out of scope for our disclosure program (unless they can be shown to lead to a higher-impact vulnerability):

- Missing security headers (for example, `Content-Security-Policy`, `Strict-Transport-Security`) without a demonstrated, practical exploit.
- Descriptive error messages (for example, stack traces) without the exposure of sensitive information.
- Reports from automated scanners without manual validation.
- Self-XSS (Cross-Site Scripting) that cannot be used to attack other users.
- Issues related to software or protocols not under Avra's direct control (for example, vulnerabilities in a third-party service we use).
- Rate limiting or brute-force attack issues on non-authentication endpoints.

Thank you for helping keep Avra and our users safe.
