> For the complete documentation index, see [llms.txt](https://docs.prophetmarket.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prophetmarket.ai/your-wallet/sign-in-methods.md).

# Sign in methods

*Two paths, differing in who holds the signing key.*

Prophet supports two sign in paths. They deliver the same product but they differ in one respect that matters: who holds the key that signs your transactions. Choose based on how you want recovery to work.

## Path A: email or Google

An embedded wallet is created for you. The signing key is held in a secure enclave operated by Privy and gated by your email or Google login. Prophet then deploys a Gnosis Safe on Polygon owned by that embedded wallet. You never see a seed phrase and you never write anything down.

In practice this is the path for anyone who does not already live in crypto. Approvals happen silently in the browser after you click, and the experience is close to a conventional web application.

## Path B: your own wallet

You connect an externally owned account such as MetaMask, WalletConnect or Coinbase Wallet. Prophet deploys a Safe owned by that wallet, and you sign every action directly from your wallet application. The key never leaves your control and recovery is whatever your wallet already provides.

## Comparison

|                   | Email or Google                                | External wallet                 |
| ----------------- | ---------------------------------------------- | ------------------------------- |
| Who holds the key | Privy, in a secure enclave gated by your login | You, in your wallet application |
| Recovery path     | Privy account recovery                         | Your wallet's own recovery      |
| Approving trades  | Silently in browser after you click            | A popup from your wallet        |
| Key export        | Not exportable                                 | Already yours                   |
| Seed phrase       | None to record                                 | Whatever your wallet uses       |

{% hint style="danger" %}
**Email and Google users: treat your login like a seed phrase**

If you lose access to the email or Google account you signed in with, recovery goes through Privy, not through Prophet. Prophet cannot restore access to an account it does not hold the key for. Secure that login accordingly, ideally with two factor authentication.
{% endhint %}

{% hint style="info" %}
**You can link several sign in methods**

One Prophet account can link more than one sign in method, for example a wallet you started with plus an email you add later. See [Account & Identity](broken://pages/03798e06237d2208e7f519d935f7a7cd3c4c422f).
{% endhint %}


---

# 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.prophetmarket.ai/your-wallet/sign-in-methods.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.