> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/user-management/what-happens-to-data-when-a-user-is-deleted-in-reo.dev.md).

# What Happens to Data When a User Is Deleted in Reo.Dev?

Deleting a user in **Reo.Dev** has a **permanent** impact on the data they created, including **segments, custom lists, tags (admin-only), and deleted contacts/accounts**. Additionally, any **CRM syncs** initiated by that user will stop dynamically updating.

***

### **Impact of Deleting a User**

| **Data Type**                        | **Impact**                                                       |
| ------------------------------------ | ---------------------------------------------------------------- |
| **Segments**                         | Permanently deleted                                              |
| **Shared Segments**                  | Remains in the system but ownership is transferred to the system |
| **Custom List Uploads**              | Permanently deleted                                              |
| **Tags** (Admin-only)                | Permanently deleted                                              |
| **Contacts & Accounts** (Admin-only) | Only those by deleted by the users are permanently lost          |
| **Shared Custom Lists**              | Not visible to other users after deletion                        |
| **CRM-Synced Data**                  | Existing data remains in the CRM, but new syncs stop             |

### **Key Scenarios**

#### **1. Deleting a User Who Created Segments, Lists, or Tags**

* **All segments, custom lists, and tags (admin-only) will be permanently deleted.**
* Other team members **cannot access or recover** this data.

#### **2. Deleting a User Who Shared Custom Lists**

* If a user **shared a custom list** with team members, the list will be deleted.
* **Other users will no longer see the shared list** in their **Shared Lists** tab.

#### **3. Deleting Contacts & Accounts (Admin-Only Action)**

* If an **admin-level user** **deleted contacts or accounts before being removed**, those records **are permanently lost**.
* However, accounts and contacts that **were not manually deleted by the user** remain in Reo.Dev.

#### **4. Impact on CRM-Synced Data**

* **Existing data already synced to the CRM remains intact.**
* **Dynamic CRM syncing stops** for segments, accounts, developers, or buyers that were syncing every 24 hours.
* **No new accounts or profiles will be sent to the CRM** after the user is deleted.

***

If you need assistance, contact us at <support@reo.dev> before proceeding with deletion.


---

# 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.reo.dev/user-management/what-happens-to-data-when-a-user-is-deleted-in-reo.dev.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.