> For the complete documentation index, see [llms.txt](https://brightid.gitbook.io/brightid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightid.gitbook.io/brightid/install/recover-move/social-recovery/set-it-up.md).

# Set it up!

Before you start, [connect to at least three people](/brightid/verifications/making-connections.md) that know, care, and trust you personally, just as well as you know them. Have them [install BrightID](/brightid/install.md) if needed.

* As mentioned in [the introduction](/brightid/install/recover-move.md), they do not necessarily have to receive any verifications if they do not want to right now.

For recovery, two types of information is secured, the first being the most essential, and second optional.

1. **BrightID private key**\
   It is secured through a [secret sharing mechanism](https://en.wikipedia.org/wiki/Shamir%27s_secret_sharing) with your recovery connections. This is the main and the most important information that is recovered by social recovery.
2. **Profile data(optional)**\
   Your and your connection's names and photos is secured by password and stored peer-to-peer with your contacts locally in mobile phones of everybody you are connected to. Your recovered BrightID can still be functional even if the profile data could not be retrieved during recovery as long as the private key was recovered successfully.

### 1) Securing BrightID private key

**Step 1.** Go to Menu on your BrightID app's home screen. 

![](/files/1h4sqItsFpg3UM678IxN)

**Step 2.** Select "*Recovery Connections*".

{% hint style="info" %}

### Listen and follow alerts about recovery

If you are new to BrightID, and since Social Recovery is so important, you will continually receive an alert to set it up until it is done. You can also tap the alert message to get to the recovery connections screen.
{% endhint %}

**Step 3.** Choose your recovery connections from the eligible connection list. The app will show you the list of eligible people for your recovery connection.

{% hint style="warning" %}

### The recovery connection eligibility

Again, recovery connections are picked from [close connections you make](/brightid/verifications/making-connections.md), and are meant to help you recover your BrightID. Be careful who you choose because they can take over your BrightID if two of them decide to cooperate against you.\
\
The eligibility criteria for someone to be your recovery connection is that the person should have marked you as '**Already Known,**' and you have marked them as '**Already Known**' as well. Please be sincere about it. Dishonesty could lead you to lose your BrightID.
{% endhint %}

![](/files/dIiIF1iTCulfQb6E5d8l)

**Step 4.** Click the 'Add' button to confirm your selection.

![](/files/YyZ5SbmNwmByihQUrefH)

### 2) Securing Profile data

Set up a password to encrypt and back up profile data consisting of your name and photo and the *names* and *photos* of your connections. You can view or change this password from your profile screen, accessible from the Menu. Even though it is less essential than securing the private key, take measures to secure it; Write it down and keep it safe so you can remember it when needed.

## [Next section details how to update recovery connections](/brightid/install/recover-move/social-recovery/set-it-up/update-recovery-connections.md)


---

# 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:

```
GET https://brightid.gitbook.io/brightid/install/recover-move/social-recovery/set-it-up.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.