> For the complete documentation index, see [llms.txt](https://docs.candychain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candychain.com/candy-chain-intro/general-help/security-guide.md).

# Security Guide

## Candy Chain Security Guide

<figure><img src="/files/CGIpq5pUy97eOfZiPMxf" alt=""><figcaption></figcaption></figure>

### Protecting Your Private Keys and Seed Phrase

At Candy Chain, the security of your assets is our top priority. As part of our commitment to protecting your investment, we've prepared this guide to help you understand the importance of safeguarding your private keys and seed phrase.

### Private Keys

A private key is a critical component of your digital wallet. It acts as a unique identifier, granting you access to your funds within the Candy Chain blockchain. Here's why you should never share your private keys:

1. **Control Over Funds**: Your private key is the only way to access and control your funds. If someone else has your private key, they have complete control over your assets.
2. **Irreversible Damage**: If you lose control of your private key, there's no way to regain access to your funds. It could lead to a permanent loss.
3. **Potential Scams**: Criminals often ask for private keys to access and steal funds. Sharing this key with anyone, even someone claiming to represent Candy Chain, can lead to theft.

### Seed Phrase

A seed phrase, also known as a recovery phrase or mnemonic phrase, is a set of words that can be used to recover your private key. It's just as sensitive as the private key itself. Here's why you should never share your seed phrase:

1. **Access to Multiple Wallets**: Your seed phrase might provide access to all the wallets derived from it. Sharing it can provide others with control over multiple accounts.
2. **Phishing Risks**: Scammers may disguise themselves as support agents and ask for your seed phrase. Candy Chain will NEVER ask for this information.
3. **Irrecoverable Loss**: If you share your seed phrase and someone misuses it, you could lose all your assets without any chance of recovery.

### Best Practices

* **Ignore Unsolicited Communications**: Always ignore messages or emails claiming to be from Candy Chain support asking for private keys or seed phrases. Reach out to us directly at <support@candychain.com> if you need assistance.
* **Use Secure Storage**: Store your private keys and seed phrase securely, such as in a hardware wallet or secure offline location. Avoid storing them digitally where they can be hacked.
* **Enable Two-Factor Authentication (2FA)**: Utilize 2FA wherever possible to add an additional layer of security.
* **Stay Informed**: Keep up-to-date with security practices by regularly visiting [our official docs](https://docs.candychain.com/).

Remember, your private keys and seed phrase are your responsibility. By following these guidelines, you can ensure the safety of your assets within the Candy Chain ecosystem. If you have any concerns or need assistance, don't hesitate to contact us at <support@candychain.com>.

<br>


---

# 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.candychain.com/candy-chain-intro/general-help/security-guide.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.