> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/6.-resources-documentation-and-terms/faq/account-security/how-to-safely-handle-lost-or-damaged-devices.md).

# How to Safely Handle Lost or Damaged Devices?

First, determine whether the device stores an MPC shard of the Cregis wallet. If it does not contain a shard, no special action is required.

If the device does store an MPC shard and is lost, to prevent unauthorized use of the lost device, follow these solutions based on the scenarios below:

## **1. If the wallet creator’s device is damaged or lost**

If the wallet creator has multiple devices with the wallet shard, authorization can be completed using another functional device. You might refer to [**here**](/3.-wallet-and-risk-control/shard/shard-authorization.md) for instruction details.

If there are security concerns regarding the shard on the inaccessible device, it can be deleted using another functional device. Refer to this [**here**](/3.-wallet-and-risk-control/shard/delete-a-shard.md) for instructions.

If the wallet creator has only one device and that device becomes unavailable, the shard reset function can be used. By entering the recovery phrase, all shards in the wallet can be reset, and non-creator members will need to reauthorize their shards. Refer to this [**here**](/3.-wallet-and-risk-control/shard/shard-authorization.md) for detailed steps.

## **2. If a non-creator member’s device is damaged or lost**

If you are concerned that the shard stored on the device might pose a security risk, the wallet creator can delete the shard of the specific device using the shard management function. The deleted shard will become invalid. Refer to this [**here**](/3.-wallet-and-risk-control/shard/delete-a-shard.md) for instructions.

If the member has a new device that needs to continue using the shard, the shard can be reauthorized through the regular shard authorization process. Refer to this [**here**](/3.-wallet-and-risk-control/shard/shard-authorization.md) for detailed steps.


---

# 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://support.cregis.com/6.-resources-documentation-and-terms/faq/account-security/how-to-safely-handle-lost-or-damaged-devices.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.