> For the complete documentation index, see [llms.txt](https://docs.supertrade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supertrade.com/rulebook/soft-vs.-hard-breach/appeals-and-review-process.md).

# Appeals & Review Process

Supertrade provides an appeals process if you believe a breach or violation was flagged incorrectly. This ensures fair treatment in cases of technical errors, outages, or disputes.

### When You Can Appeal

You may request a review if:

* A breach was triggered due to **technical errors** (e.g., data outage, platform disconnect).
* You believe the system flagged a **false breach** not aligned with actual equity/drawdown levels.
* There are **extraordinary market conditions** (e.g., feed errors, duplicate ticks).

<h3 align="center">How to File an Appeal</h3>

{% stepper %}
{% step %}

### Gather evidence

Collect everything related to the breach: account ID, funding model (Challenge / Instant Funding), date & time, screenshots of equity/drawdown, trade IDs, platform logs, and a short description of what happened (e.g., outage, feed error).
{% endstep %}

{% step %}

### Submit your appeal

Go to our [Help Center](https://supertrade-help.zendesk.com/hc/en-us/requests/new?utm_source=gitbook\&utm_medium=docs\&utm_campaign=contact_support\&utm_content=). Create a new ticket with the subject line **“Breach Appeal – \[Account ID]”**, attach your evidence, and include a short explanation of why you believe the breach was incorrect.
{% endstep %}

{% step %}

### Provide required details

In the ticket, include:

* Account ID and plan type
* Exact breach timestamp (with timezone)
* Brief explanation of why it’s incorrect
* Screenshots/logs (equity curve, orders, connection status)
  {% endstep %}

{% step %}

### Risk Team review

Support forwards your case to the Risk Team for manual verification (equity, drawdown calculations, execution data, platform status).
{% endstep %}

{% step %}

### Outcome & next steps

You’ll receive the decision by email/in-app:

* **Approved:** account may be reinstated or reset (case-dependent).
* **Declined:** breach stands; the account remains paused/closed.

{% hint style="info" %}
**Tip:** File the appeal as soon as possible after the incident and keep all evidence attached in one ticket to speed up review.
{% endhint %}

{% hint style="warning" %}
**Warning:** Drawdown limit breaches are typically treated as **hard breaches**; if confirmed, they are not reversible.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.supertrade.com/rulebook/soft-vs.-hard-breach/appeals-and-review-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.