> For the complete documentation index, see [llms.txt](https://prerich-app.gitbook.io/prerich-app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prerich-app.gitbook.io/prerich-app/advanced/private-key-management.md).

# Private Key Management

We do **NOT** have access to your private keys.\
\
**Secure and Easy Access with Prerich**

At Prerich, we prioritize the security of your digital assets while ensuring a seamless and user-friendly experience. By partnering with PRIVY for managing private keys, we provide you with an easy login process via Google or email while ensuring you retain complete control over your funds.

**Key Features**

1. **Simple Login with High Security**:
   * **Easy Access**: Log in with Google or email instead of having to remember a complex 12/24 word private key.
   * **Full Control**: While Prerich facilitates easy login, you retain full control over your private keys. Neither Prerich nor PRIVY can access your funds.
2. **Enhanced Security Measures**:
   * **Secure Architecture**: Your private key is securely managed in-memory within an isolated environment, ensuring it is never stored or accessible outside this secure setup.
   * **Non-Custodial**: Your funds remain completely under your control. The security architecture ensures that even Prerich cannot access your private keys.
3. **Session Management**:
   * **Access Tokens**: Once logged in, you receive an access token that maintains your authenticated session securely.
   * **Refresh Tokens**: These tokens ensure that you don’t have to log in frequently, providing a smooth and continuous user experience.
4. **Private Key Management**:
   * **Secure Key Generation**: When you create a wallet, a secure private key is generated and [split into three parts](https://en.wikipedia.org/wiki/Shamir%27s_secret_sharing) for added security. 
   * **In-Memory Operations**: The full private key is only ever assembled in-memory for signing transactions, ensuring it is never exposed or stored persistently.
5. **Recovery Options**:
   * **Device Share**: Stored securely on your device.
   * **Auth Share**: Encrypted and managed securely to ensure only you can access it.
   * **Recovery Share**: Can be managed by you directly or automatically secured, depending on your preference.

**Why You Can Trust Prerich**

* **Non-Custodial**: Your private keys are managed in a way that ensures Prerich has no access, keeping your funds safe.
* **User-Friendly**: We combine high security with ease of use, so you can focus on trading without worrying about the safety of your assets.

By using Prerich, you benefit from advanced security measures while enjoying a simple and intuitive trading experience. \
\
Your funds should always be under your full control.


---

# 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://prerich-app.gitbook.io/prerich-app/advanced/private-key-management.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.