# Account Security Best Practices

## Use Trusted Wallets

* Use wallets like Anchor, TokenPocket or Vaulta Wallet
* Always review transaction permissions before approving

## Use Custom Permissions for dApps

* Avoid giving dApps your full active permission
* Use custom named permissions tied only to specific contracts and actions
* This limits the damage if a contract is compromised

## Use Multi-Signature (Multisig) for High-Value Accounts

* For organizations or treasuries, require 2 or more keys to approve actions
* Use the eosio.msig contract for multi-sig governance

## Audit Contract Authorizations

* Use block explorers like [Unicove](https://unicove.com) to view:
  * Which contracts have eosio.code permission
  * Which keys or contracts can act on your behalf

## Keep owner Key Offline

* Generate and store your owner key cold (offline)—preferably on a hardware wallet or air-gapped device
* Only use it to:
  * Rotate keys
  * Recover access if your active key is compromised


---

# 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://vaulta.gitbook.io/vaulta-guides/security-and-staying-safe/account-security-best-practices.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.