> For the complete documentation index, see [llms.txt](https://docs.stakestone.io/stakestone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakestone.io/stakestone/stone-wallet/frequently-asked-questions/is-stone-wallet-secure.md).

# Is Stone Wallet Secure?

Stone Wallet is designed to be secure, private, and fully user-controlled, combining self-custody with a simplified user experience. Your funds always remain under your control, and the system is built to minimize risk while keeping the experience simple.

***

### Non-Custodial by Design

Stone Wallet uses a non-custodial smart wallet architecture.

This means:

* You are the only one who can authorize transactions
* No one  can move your funds without your approval
* Your assets are not held or controlled by a centralized party. Instead, they are secured on-chain and managed through your wallet.

***

### Secure Key Management

Stone Wallet uses secure key management powered by MPC (Multi-Party Computation). This removes the need for traditional seed phrases while avoiding a single point of failure.

Your wallet access is protected through distributed key security, making it both safer and easier to use compared to traditional crypto wallets.

***

### Trusted Payment Infrastructure

Deposits and withdrawals are supported through regulated third-party providers.

These providers operate under applicable compliance standards, including KYC and AML requirements where necessary. This ensures that fiat on- and off-ramps are handled securely and reliably.


---

# 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.stakestone.io/stakestone/stone-wallet/frequently-asked-questions/is-stone-wallet-secure.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.
