# End-User Safety

We protect your funds by using a **separate** wallet both for deposits and withdrawals.\
\
User deposits are ***comingled*** address-wise but separated database-wise, obviously, however, besides that minimal & logical security measure, we also provide withdrawals through a wallet **different** than those of user deposits.\
\
This means that, in the case of someone finding an **exploit**, even if the user funds were **equivalent** to **100k** (which is still very little for the scope we're ready for) — we'd only limit **withdrawals** up to **5k** at a time, from a different wallet, which is loaded with such amount, and oriented for withdrawals only.\
\
Ultimately, if there was an **exploit**, we'd only lose **5k**, money which would be refunded from the team's pockets, hence no loss for the users.\
\
Withdrawals are **automatic**, only filling the wallets is not, which is what provides the extra safety mentioned above; in other words, don't worry, we're **not** doing **manual** withdrawals, the system will be as fast as if this measure did not exist.\
\
Users will also be able to see the **balance** of this wallet, which will be made public, serving as a **'current maximum withdrawal'.**\
\
In the case of someone wanting to withdraw **more** than the **maximum**, they'd have to wait for the **refill**. However, users in the first place **cannot** deposit more than such, meaning that this would be unlikely, unless you were an exceptional trader, thus withdrawing profits.\
\
All 'company' withdrawal wallets will be made and remain **public** for transparency & safety.\
\
Individual **deposit** addresses stay **private**, as it should. We value your privacy, even though we're not oriented towards it as our focus.


---

# Agent Instructions: 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:

```
GET https://anydex.gitbook.io/the-future-of-dexs./safety/end-user-safety.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.