> For the complete documentation index, see [llms.txt](https://docs.lollipop.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lollipop.gg/lollipop-authenticator-for-chrome/recover-existing-account.md).

# Recover an existing account

Use this flow if you already have a Lollipop account and want to restore it in this browser.

## Start recovery

From the welcome screen, click **I already have an account**.

![Welcome screen](https://3764565543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKjec3KUOsY9wSOPFigE%2Fuploads%2Fgit-blob-e6614b5b7805ec9816b890a9e33098ae66c6d5a0%2Fwelcome.png?alt=media)

The welcome screen lets existing users start account recovery.

## Enter your recovery phrase

Enter your 12-word or 24-word secret recovery phrase in the original order.

![Recover account screen](https://3764565543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKjec3KUOsY9wSOPFigE%2Fuploads%2Fgit-blob-d7675df2fad3ee20e6032dc9ce457010649b1536%2Frecover-account.png?alt=media)

The recovery screen detects how many words you have entered.

Check the confirmation box, then continue.

If the words are missing, misspelled, or out of order, the account cannot be restored.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lollipop.gg/lollipop-authenticator-for-chrome/recover-existing-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
