# Data backup Data backup in Sealed is based on a local-first model. The app does not use a traditional cloud account where Sealed stores the user’s identity, messages, and recovery data. Instead, recovery depends on what the user controls locally and what can be reconstructed from blockchain-based encrypted data. This gives Sealed stronger privacy, because there is no central company backup containing user conversations or identity data. At the same time, it also means that backup works differently from normal web2 apps. There is no standard “forgot password” flow, and Sealed cannot recreate recovery material that the user has lost. ### Main identity recovery The main Sealed identity is backed up through the 24-word mnemonic phrase created during setup. This phrase is the recovery key for the user’s main identity and allows it to be restored on another device if the original device is lost, reset, or replaced. This is the most important backup element in Sealed. If the user keeps the mnemonic phrase safe, they can restore the main identity. If they lose it, Sealed cannot restore the identity through email, phone number, support request, or password reset. ### Recoverable blockchain data Some Sealed data can be recovered because it passed through the blockchain delivery flow in encrypted form. After restoring the main identity, the app can scan the blockchain, find relevant encrypted data, and decrypt what belongs to the restored identity. This is not the same as downloading a backup from a Sealed server. The blockchain provides access to encrypted delivery history, while the restored identity provides the ability to recognize and decrypt the data that belongs to the user. ### Device-bound data Not every part of Sealed is designed to be recoverable. Some data exists only on the device where it was created. This includes data that is intentionally separated from the main identity, such as Alias Chat information, local aliases, exchanged keys, shared hints, temporary wallets, and locally stored Alias Chat credit codes. This is a privacy trade-off. Device-bound data is harder to connect to the main identity, but it can also be lost if the device is lost, wiped, reset, or damaged. ### Wipe and reset consequences Sealed includes local wipe and reset mechanisms, such as the termination code and automatic reset after 5 incorrect access code attempts. These features are designed to protect the device in high-risk situations, but they also remove local data. After a wipe or reset, the main identity can be restored only with the 24-word mnemonic phrase. Device-bound data may not come back, because it was never meant to be recoverable through the main identity backup. ### User responsibility Because Sealed does not keep a central recovery copy, the user is responsible for protecting the mnemonic phrase. It should be stored safely, preferably offline and away from the device. The phrase should not be stored in screenshots, cloud notes, unencrypted files, or places that other apps or accounts may access. If someone else gets the phrase, they may be able to restore the identity. If the user loses it, Sealed cannot recreate it. ### Data Backup summary Data backup in Sealed has two categories: recoverable identity-based data and device-bound data. The 24-word mnemonic phrase restores the main identity and may allow the app to recover encrypted blockchain-based message data. Alias Chat and other device-bound information are intentionally local and may be lost with the device. This model gives Sealed stronger privacy and avoids central cloud backups, but it requires the user to protect their recovery phrase carefully. --- # Agent Instructions: 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://docs.sealed.channel/security-and-privacy/data-backup.md?ask= ``` 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.