> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/safety-and-controls.md). # safety and controls ## safety and controls trover combines product controls with wallet and provider safeguards. those checks reduce risk, but they can’t remove smart-contract, market, custody, signing, bridge, or network risk. ### read before acting * [wallet security](/safety-and-controls/wallet-security.md) * [fees, routes, and risks](/safety-and-controls/fees-routes-and-risks.md) * [account controls](/safety-and-controls/account-controls.md) ### core safeguards * privy-backed authentication and wallet linking * separate x mention and dm controls * optional confirmation, mfa, disclosure, and delegated-wallet enrollment requirements * recipient, route, slippage, allowlist, denylist, liquidity, and notional checks * idempotent submissions and ambiguous-transaction reconciliation * operator hard stops for trading, bridging, and social execution {% hint style="danger" %} never share a seed phrase, private key, one-time password, or recovery code with trover, an x account, or anyone claiming to provide trover support. {% endhint %} --- # 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.trover.tech/safety-and-controls.md?ask=&goal= ``` `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.