> For the complete documentation index, see [llms.txt](https://docs.allscale.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allscale.io/supplement-material/bug-reports-and-security/how-to-report.md).

# How to Report

### 1. Send Your Report by Email

Send your report to the right inbox:

* **Security vulnerabilities:** <security@allscale.io>. Reports go directly to our engineering team
* **Other bugs:** <support@allscale.io>

If you're not sure whether an issue is security-related, send it to <security@allscale.io>.

Use a clear subject line, for example: `[Bug] Invoice PDF shows wrong currency` or `[Security] Access control issue on Payroll API`.

If you find more than one independent issue, you can include them in one email, but please describe each issue separately.

***

### 2. Include the Right Information

The more detail you share, the faster we can verify your report. A good report includes:

* **Affected product, page, or API endpoint**, plus the app version or platform (web, iOS, Android) if relevant
* **Steps to reproduce**, numbered and in order
* **Expected result vs. actual result**
* **Evidence**: screenshots, screen recordings, request/response samples, or logs

For security reports, please also include:

* **The test account(s)** you used and the **time** of testing (with time zone)
* **The potential impact**: what an attacker could do and which users or funds could be affected

{% hint style="info" %}
You don't need a full exploit script to report a security issue. A clear description and enough evidence to verify it is sufficient. Please don't expand your testing just to prove impact.
{% endhint %}

{% hint style="danger" %}
Never send passwords, private keys, passkeys, or recovery phrases, and we will never ask for them. If your report involves sensitive data you came across, describe it without including the data itself.
{% endhint %}

***

### 3. We Confirm Receipt

We aim to confirm receipt within **2 business days**. Our reply will include a **report ID** for you to use in follow-ups.

If we need more information to reproduce the issue, we'll ask you once with a specific request. Reports that remain incomplete for **14 days** may be closed and reopened later if new evidence arrives.

***

### 4. We Verify and Keep You Updated

Our engineering team reviews each report, assesses its impact, and works on a fix where needed. We'll keep you informed as your report moves through these stages:

| Status                    | What it means                                                     |
| ------------------------- | ----------------------------------------------------------------- |
| **Received**              | Your report is logged and has a report ID                         |
| **Under review**          | We're reproducing and assessing the issue                         |
| **Confirmed**             | We've verified the issue and are planning a fix                   |
| **Fix scheduled / Fixed** | A fix is planned for a release, or has been deployed and verified |
| **Closed**                | No further action is needed, and we'll explain why                |

Fix timelines depend on complexity and impact. Issues that could affect user funds or data are prioritized immediately.

***

### 5. Rewards Are Confirmed Individually

If your report is a valid contribution, we'll contact you by email to confirm the reward and the details we need to deliver it. Rewards don't have to wait until a fix is deployed.

See [Rewards & Recognition](https://docs.allscale.io/supplement-material/bug-reports-and-security/rewards-and-recognition).

***

### 📌 Notes

* Please report each issue privately to us first, and don't share it publicly or with third parties while we work on it
* Sending repeated emails or follow-ups doesn't affect how a report is assessed or rewarded
* Product suggestions and usage questions are welcome at <hi@allscale.io>
