> For the complete documentation index, see [llms.txt](https://docs.reloadsol.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reloadsol.app/understand-risk/sl-tp-and-exit-protection.md).

# Exit mechanics & protection

How spot exits work on reloadSol—why there are no exchange-side stop-loss or limit orders on the public app, and how to manage exits safely.

**TL;DR:** On the public reloadSol app, your tokens live in your own non-custodial wallet—you exit manually via **Bulk Sell**, **Single Swap**, or **Fast Sell** on `/pnl`. reloadSol does **not** place exchange-side stop-loss, take-profit, or resting limit orders for your wallet.

[Open P\&L Fast Sell →](https://reloadsol.app/pnl)

***

## What reloadSol does (and does not) offer

{% hint style="warning" %}
reloadSol public trading surfaces are **spot, fully-collateralised, non-custodial** market execution. There is **no margin, no leverage, no liquidation, no resting limit order, and no exchange-side stop-loss or take-profit order**. Your position is a token in your own wallet and you exit by selling it.
{% endhint %}

***

## Practical exit discipline for spot traders

Because you sign every exit yourself, plan your exit *before* you buy:

| Exit habit                               | Why it helps                                                                                                                                                  |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Decide your invalidation level first** | Avoids freezing during a fast drop—remember a **−50%** loss needs **+100%** to break even.                                                                    |
| **Take partial profits into strength**   | Use the `20%`, `50%`, or `75%` presets on [Bulk Sell](https://reloadsol.app/sell/solana) to lock gains while keeping a runner.                                |
| **Watch liquidity, not just price**      | A token up +100% on thin liquidity can suffer heavy [price impact](https://docs.reloadsol.app/start-here/trading-terms.md#quote-and-execution) when you sell. |

*Explore how dynamic trailing stops and early breakdown cuts compare to static stops in our illustrative model:* [Open the OHLC Defense Simulator ↗](https://studentofcoding.github.io/reloadsol-docs/widgets/index.html?view=ohlc)

***

## Related

* [Risk basics for spot traders](https://docs.reloadsol.app/understand-risk/risk-basics.md)
* [Sweep dust & reclaim rent](https://docs.reloadsol.app/trade/bulk-sell-and-dust-reload.md)
* [P\&L, trade history & portfolio](https://docs.reloadsol.app/trade/pnl-history-and-portfolio.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reloadsol.app/understand-risk/sl-tp-and-exit-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
