# No kyc verfication

KYC (Know Your Customer) verification is a process where financial service providers verify the identity of their customers. However, it is not mandatory for cryptocurrency wallets to conduct KYC verification.&#x20;

In the case of Armour Wallet, the non-custodial approach means that the wallet does not have access to users' personal information or funds. Therefore, there is no need for KYC verification. Armour Wallet offers a high level of privacy and anonymity to users by not requiring any form of personal information or identity verification. Users can simply download the wallet and start using it without going through any additional verification steps. This is particularly beneficial for users who value their privacy and do not want to disclose their personal information to a third-party service.&#x20;

The absence of KYC verification also means that the user's information is not stored on a centralized database, reducing the risk of data breaches and identity theft. Users can rest assured that their personal information and digital assets are secure and private when using Armour Wallet.&#x20;

However, it is worth noting that some cryptocurrency exchanges and services may require KYC verification for certain transactions. In such cases, users can still use Armour Wallet to manage their digital assets and conduct transactions, but may need to go through KYC verification on the exchange or service they are using.


---

# 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://armourwalletappwhitepaper.gitbook.io/whitepaper/game-changing-features/no-kyc-verfication.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.
