> For the complete documentation index, see [llms.txt](https://docs.novawallet.io/nova-wallet-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novawallet.io/nova-wallet-wiki/legal-and-security/security.md).

# Security

Self custody is the only way!

Nova Wallet is a **non-custodial** web3 wallet solution for **iOS** and **Android** devices. Your private key is stored locally on your device, in the enclaved secured storage of your operating system, and it is encrypted with the user's personal secret.

From a privacy aspect, Nova Wallet is not collecting any user data and therefore cannot send any user data anywhere for any purpose (even for analytics). **All data is stored locally, only on the user's device**.

In the event that a user is using a **Hardware (cold) Wallet** ([Polkadot Vault](/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault-legacy.md) / [Parity Signer](/nova-wallet-wiki/wallet-management/hardware-wallets/parity-signer.md) / [Ledger](/nova-wallet-wiki/wallet-management/hardware-wallets/ledger-devices.md)) in conjunction with Nova Wallet, then the private key isn't even stored on the user's device. It is stored within the Hardware (cold) Wallet only.&#x20;

In the case of **Watch Only Wallets**, since the user does not have access to the private key, the user cannot send transactions from those accounts.

All operations conducted via Nova Wallet are submitted directly to the blockchain's nodes, and the "read-only" data is queried directly from the blockchain's nodes as well. The exceptions to this are; fiat values, which are queried from [CoinGecko](https://www.coingecko.com/); and transaction history, which is queried from [SubQuery](https://subquery.network/).

{% hint style="warning" %}
⚠️ Store your mnemonic passphrase privately and **NEVER** share it with anyone ⚠️

Admins will **never** DM you first and will never request anything from you — if you see a person sending you a message with the same photo & name that admins have — it's a scam.

Admins will **never** ask you for crypto/private key/seed phrase. Do **NOT** open links from anyone in DMs to “verify/synchronize your wallet” or any requests to “fill Google form” — these people are trying to scam you. Please Report and block them.

**If you share your passphrase with anyone they will then have control of your account and your assets.**
{% 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 by asking a question.

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

```
GET https://docs.novawallet.io/nova-wallet-wiki/legal-and-security/security.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.
