> For the complete documentation index, see [llms.txt](https://docs.duels.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duels.trade/account-and-safety/privy-and-account-security.md).

# How duels.trade uses Privy

Privy provides authentication and wallet-security functions used by duels.trade.

## Authentication

Privy supports:

* Email verification-code sessions
* Google sign-in
* Wallet login and linking
* Embedded wallets for supported email or social accounts
* Linked identities such as X

## Embedded and self-custody wallets

### Embedded Privy wallet

An eligible email or social account can have an embedded wallet managed through Privy's wallet infrastructure. Wallet actions still require the authorization presented by the Privy flow.

### Self-custody wallet

When you connect a self-custody wallet, trades and signatures use that connected wallet directly. duels.trade does not replace it with a platform-managed trading wallet.

## Sensitive actions

Privy is used where applicable for:

* Wallet authentication
* Signing supported sends and transfers
* Deposit signer setup
* MFA enrollment and management
* X account linking
* Secure embedded-wallet private-key export

These functions reduce reliance on passwords and centralize identity and wallet authorization, but they do not make transactions reversible or remove trading risk.

## MFA

Open **Account → Security Settings** and select **Set up MFA**.

* MFA is managed through Privy.
* Enrollment requires a supported email or social Privy session.
* The app displays enrolled methods when available.

## Private-key export

Embedded wallet users may see **Export with Privy**.

The export occurs through Privy's secure flow. After export:

* Store the key offline.
* Never send it to support.
* Never paste it into an unknown website.
* Treat anyone with the key as having full wallet control.

## What Privy does not protect against

Privy cannot protect you from:

* Approving a malicious transaction
* Sending to the wrong address or network
* Sharing an exported private key
* Excessive leverage or trading losses
* A compromised email, social, or wallet account


---

# 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.duels.trade/account-and-safety/privy-and-account-security.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.