> For the complete documentation index, see [llms.txt](https://docs.degate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degate.com/security-and-self-custody/security-overview.md).

# Security Overview

DeGate is self-custodial: your private keys are generated and used on your device (or, for hardware wallets, on your hardware device), and DeGate's servers do not hold them.

## What DeGate can and cannot do

* DeGate **cannot** read your private keys or recovery phrase.
* DeGate **cannot** move funds from your addresses; only signatures produced by your key can do that.
* DeGate **can** construct transactions for you to sign, quote routes, and manage gas purchases, none of which requires custody of your assets.

## Key storage by wallet type

DeGate supports several ways of holding a wallet. Where the key material lives, and how independently you can recover it, differs by type:

* **Created or imported mnemonic wallets:** your recovery phrase is generated (or entered) locally and your keys stay on your device. This is the most independent option: your phrase alone restores your wallet in DeGate, or in any BIP39/BIP44-compatible wallet, with no dependency on DeGate at all.
* **Hardware wallets:** your private key never leaves the hardware device. DeGate reads your addresses over standard derivation paths, so your primary balance is recoverable with your device and any compatible wallet software, independent of DeGate.
* **Email wallets:** your signing key is an embedded wallet provided by our wallet infrastructure partner, tied to your email login, not generated or held by DeGate directly.
* **External-wallet and web-sync accounts** (Connect External Wallet / Sync from DeGate Web): your root key stays in your own external wallet; DeGate derives an operating wallet from a signature you provide with that wallet.

None of these methods gives DeGate access to your raw private keys. However, they are **not equally independent of DeGate today**: see "What this means for recovery" in [Wallet Addresses & Networks](/security-and-self-custody/wallet-address-and-networks.md) for the practical difference between wallet types.

## Independent review

Audit reports and their scope are documented on the [Audits](/security-and-self-custody/audits.md) page; vulnerability reports are welcome at <bounty@degate.com> ([Bug Bounty](/security-and-self-custody/bug-bounty.md)).

## FAQ

**How do I make sure I'm using the real DeGate?** Check every domain, app link, and community channel against [Official Links & Verified Contracts](/about-degate/official-links.md) before connecting a wallet or entering credentials. DeGate will never ask for your recovery phrase, private keys, or password; anyone who does is not DeGate.

**Can DeGate freeze my account?** There is no custodial account to freeze. Assets sit at addresses controlled by your key; only you can authorize transactions from them.


---

# 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.degate.com/security-and-self-custody/security-overview.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.