Ledger Recover, provided by Coincover, is an optional paid service designed to restore access to a compatible Ledger wallet when the original device or physical recovery backup is unavailable. With the owner’s approval on the Ledger device, recovery data is encrypted, divided into three protected fragments and distributed to separate backup providers. A later recovery uses identity verification and two fragments to restore the wallet on a compatible Ledger device.
Last reviewed: September 28, 2026. Availability, price, taxes, accepted identity documents, supported countries, devices and application requirements can change. Confirm current terms in Ledger’s official documentation before subscribing or relying on the service. This independent educational guide is not affiliated with Ledger or Coincover and is not financial, legal or security advice.
What is Ledger Recover?
Ledger Recover is a subscription-based wallet recovery service. It addresses a common self-custody failure: an owner loses the hardware wallet and also cannot use the physical Secret Recovery Phrase. Instead of depending only on a written or metal copy, an enrolled user can prove identity and reconstruct the wallet backup through the service.
The service does not hold cryptocurrency in an account like an exchange. Blockchain assets remain associated with private keys derived by the wallet. Recover provides a route for restoring those keys to a compatible Ledger device under its documented protocol.
Enrollment changes the recovery model. Traditional hardware-wallet recovery depends on possession of the exact recovery phrase and any additional passphrase. Ledger Recover adds companies, identity data, secure servers, hardware security modules and a claims process. Whether that trade is appropriate depends on the owner’s risks, technical ability and recovery needs.
Ledger Recover is optional
Installing supported firmware does not by itself create a remote backup. According to Ledger’s design, the device must receive an explicit command and the owner must approve the operation on the physical device. Without enrollment and approval, the three backup fragments are not created for the service.
This distinction matters because firmware must be technically capable of performing supported functions, while the function still requires user action. Users who do not want the service can continue using a conventional offline recovery backup. They should nevertheless evaluate firmware through their own threat model and obtain updates only through the official Ledger application.
Seed, entropy and Secret Recovery Phrase
Discussions about wallet recovery often use seed, entropy and recovery phrase as though they were identical. They are closely related but describe different representations.
- Entropy: the original random information from which wallet recovery material is generated.
- Secret Recovery Phrase: a human-readable encoding, commonly 24 ordered words on Ledger devices.
- Seed: the cryptographic value derived through the recovery process and used to derive wallet keys.
- Private keys: account-specific signing keys derived from the wallet seed.
Ledger states that Recover operates on encrypted entropy rather than uploading a plaintext list of 24 words. The distinction is technically important, but the security consequence remains substantial: reconstructed recovery material can restore the same private keys and therefore must be protected as a critical wallet secret.
How Ledger Recover creates the backup
- The user checks that the service is available for the country, document and Ledger model involved.
- The user creates or signs in to the required Ledger Recover account and starts a subscription.
- The enrollment workflow performs identity verification using an accepted government-issued document and required biometric or liveness checks.
- The compatible Ledger device displays a request associated with creating the backup.
- The owner reviews and physically approves the operation on the device.
- Inside the Secure Element, the recovery entropy is encrypted and divided into three fragments.
- The fragments are protected for separate backup providers and transmitted through authenticated encrypted channels.
- Each provider stores its protected fragment using controlled infrastructure and hardware security modules.
The computer or phone coordinating enrollment should not receive the plaintext recovery phrase. If a website, application or support agent asks the user to type the 24 words during a Recover subscription, stop. That is not the intended enrollment model.
Why three fragments are used
A single complete cloud copy would create one obvious target. Ledger Recover instead uses a threshold design: the protected backup is split into three fragments, and two are required for restoration. One fragment alone should not reconstruct the wallet.
The providers identified in Ledger’s current public material include Ledger, Coincover and EscrowTech. This distribution is intended to reduce dependence on the compromise or loss of one provider. It does not remove trust entirely. The protocol, provider separation, encryption, identity systems, claims process and operational controls all become parts of the recovery boundary.
| Condition | Expected consequence | What remains important |
|---|---|---|
| One fragment is unavailable | Two remaining eligible fragments can support recovery | Identity verification and service operation |
| One stored fragment is copied | It should not reconstruct the wallet alone | Encryption, provider isolation and incident response |
| Two fragments are authorized for recovery | The recovery material can be reconstructed within the protected workflow | Correct claimant verification and genuine device handling |
| User never enrolls | No Recover backup is created for that wallet through the service | The user’s own recovery backup |
Encryption and hardware security modules
Ledger describes the fragments as encrypted in the device and protected during transfer. Backup providers use hardware security modules, or HSMs, to control sensitive cryptographic operations. The protocol includes authenticated communication intended to ensure that a genuine Ledger device exchanges protected material with genuine service infrastructure.
An HSM is not a promise that nothing can ever fail. Its purpose is to limit secret exposure and enforce operations inside hardened hardware. Security still depends on correct protocol implementation, access control, monitoring, separation of duties, vendor maintenance and response to newly discovered vulnerabilities.
Users should distinguish “encrypted” from “risk-free.” Encryption reduces what a database thief can learn, while the complete service must still be able to authorize legitimate restoration. The controls deciding when protected fragments may be used are therefore as important as storage encryption.
How recovery works on a replacement device
- Obtain a supported genuine Ledger through a trusted purchase route.
- Install Ledger Wallet from Ledger’s official domain and complete Genuine Check.
- Choose the Recover restoration workflow rather than initializing an unrelated new wallet.
- Sign in using the account connected to the subscription.
- Complete the required identity-verification and liveness process.
- Review every instruction on the Ledger device, not only on the computer or phone.
- After authorization, two protected fragments are supplied through the service workflow.
- The required recovery material is reconstructed in the protected environment and restored to the Ledger device.
- After restoration, verify known public addresses and account history before receiving or moving a large amount.
Ledger Recover is intended to restore keys to a Ledger device; it is not designed to reveal the 24 words to the user. Do not expect support to email, display or dictate a recovery phrase. Any message offering that behavior should be treated as suspicious.
Identity verification is a recovery key
With a paper recovery phrase, possession of the phrase is the central recovery credential. With Ledger Recover, the service must determine that the claimant is the enrolled person before releasing the required recovery path. Identity verification therefore becomes a security-critical control.
Ledger distinguishes its identity verification from full financial KYC. The enrollment process may collect identity-document information and biometric or liveness data needed to establish that the applicant owns the document. The exact provider, accepted evidence and manual-review process can vary.
The user should evaluate two opposite risks:
- False acceptance: an impostor succeeds in being treated as the owner.
- False rejection: the real owner cannot pass verification because documents, appearance, name, jurisdiction or records changed.
Stronger checks can reduce impersonation while increasing recovery friction. No identity process has zero error, so subscribers should keep account information accurate and understand escalation procedures before an emergency occurs.
What personal information may be involved?
Current Ledger explanations describe collection of necessary identity-document data, a selfie or video-derived image and additional information during a recovery request. Data can be processed by identity-verification providers as well as entities involved in the Recover service.
This is different from an offline metal backup, which can be created without sending identity documents to a recovery provider. Users choosing Recover exchange some data minimization for an identity-based recovery route.
Before subscribing, read the current Recover privacy policy and determine:
- which organizations act as controllers or processors;
- which identity and biometric information is collected;
- where information may be processed;
- how long active, cancelled and dispute-related records are retained;
- which deletion rights and legal exceptions apply;
- how to contact the relevant privacy team.
Cancellation does not necessarily mean that every record disappears immediately. Financial, security, fraud-prevention or litigation obligations may require limited retention. The current policy, not an old summary, controls those details.
Supported devices, countries and documents
Ledger has expanded device support over time, but desktop and mobile availability can differ by model. Country eligibility and accepted documents are also narrower than global Ledger-device availability. A user may own a technically compatible device but still be unable to subscribe because the service, document or residence is not supported.
Check all of the following immediately before relying on Recover:
- exact Ledger device model;
- required firmware version;
- desktop or mobile Ledger Wallet requirement;
- country or regional availability;
- accepted passport, national identity card or driver’s licence;
- document expiration date and name consistency;
- subscription currency, taxes and payment method;
- recovery availability after moving to another country.
Do not buy a device or discard an existing backup based on an old compatibility list. Product names and eligibility rules can change.
Ledger Recover does not back up a passphrase
A BIP39 passphrase, sometimes informally called a “25th word,” derives a different wallet when combined with the recovery phrase. Ledger states that this additional passphrase is not included in the Recover backup.
That separation can be intentional: a Recover restoration of the base wallet does not reveal the passphrase-protected wallet without the exact additional passphrase. It also creates a permanent-loss risk. If the owner loses the passphrase, successful Recover restoration may display a valid base wallet with different or empty accounts.
Every character, space and capitalization choice matters. Store the passphrase through a separate tested recovery plan, and document that the protected wallet exists without placing all required secrets together. Never assume identity verification can reset a missing wallet passphrase.
Ledger Recover compared with other backup methods
| Method | Primary benefit | Main dependency | Main failure risk |
|---|---|---|---|
| Paper recovery phrase | Simple and offline | Physical storage and accurate transcription | Fire, water, theft, copying or deterioration |
| Metal recovery backup | Better physical durability | Correct marking and secure location | Theft, discovery, transcription error or lost passphrase |
| Ledger Recover | Identity-based restoration without locating the physical phrase | Subscription, providers, ID verification and supported device | Service, privacy, impersonation or verification failure |
| Ledger Recovery Key | PIN-protected physical recovery method on supported devices | Compatible card, device and correct PIN handling | Lost or damaged card, forgotten PIN or unsupported workflow |
| Recovery phrase plus passphrase | One component alone does not open the protected wallet | Accurate preservation of both components | Loss or typo of either required secret |
| Threshold or multi-share backup | Can tolerate loss of some shares | Correct standard, threshold and distribution | Too few surviving shares or operational confusion |
These methods are not automatically interchangeable. A provider-managed 2-of-3 encrypted service differs from a user-managed multi-share standard. A PIN-protected card differs from written BIP39 words. Understand exactly what each method can restore and on which devices before combining them.
What trust does Ledger Recover add?
Conventional recovery asks the owner to trust personal storage practices and the cryptographic wallet standard. Recover introduces additional assumptions:
- the device firmware performs fragment creation only after informed physical approval;
- encryption and threshold protocols are correctly implemented;
- backup providers remain sufficiently independent;
- HSM keys and administrative access are protected;
- identity providers distinguish the owner from an attacker;
- manual claims staff resist social engineering and insider abuse;
- the service remains available when recovery is needed;
- legal orders, corporate changes and jurisdictional rules are handled consistently with published commitments.
Adding trust is not automatically unacceptable. Banks, exchanges, cloud services and estate professionals all introduce trust for particular benefits. The correct question is whether the added recovery capability addresses the user’s most likely failures without creating a larger unacceptable risk.
Security risks to evaluate
Provider collusion or coordinated compromise
The threshold design intends that one provider cannot restore the backup alone. A threat model should still consider two providers, compromised authorization systems, insiders and legal compulsion. Encryption, separation of duties, audits and monitoring reduce these risks but cannot make institutional dependencies disappear.
Identity impersonation
An attacker may combine stolen documents, personal data, account access and manipulated video. Recovery controls must resist that combined attack. Users can reduce exposure by securing the email and password connected to Recover, monitoring identity-data breaches and reporting lost identity documents.
Real owner cannot verify
A changed legal name, expired document, facial injury, aging, relocation or unsupported replacement document can complicate automated checks. Learn the manual-claims path in advance, especially when the wallet may be part of an estate or incapacity plan.
Phishing during enrollment or recovery
Recover creates vocabulary that scammers can imitate: subscription expiry, failed payment, identity revalidation and emergency restoration. Open Ledger Wallet through the installed application and use official bookmarks. Never disclose 24 words to “reactivate” the service.
Account compromise
The Recover login and associated email are not the wallet seed, but compromising them may help an attacker initiate or study the claims workflow. Use a unique password, strong account authentication and secure email recovery. Do not approve an unexpected operation on the Ledger screen.
Long-term service change
Prices, providers, terms, supported regions and corporate ownership can change over the lifetime of a wallet. A recovery plan should be reviewed periodically and should not assume today’s interface will exist unchanged years from now.
What happens if the subscription stops?
Payment failure, cancellation and voluntary backup deletion are different events and may follow different timelines. Do not infer that a missed payment instantly destroys the backup, or that cancellation instantly deletes every operational and identity record. Read the current subscription and privacy terms.
Before cancelling:
- Confirm that the Ledger device still works.
- Verify an independent recovery method without exposing the secret.
- Move assets only if changing to a genuinely new wallet is part of the plan.
- Follow the official cancellation and backup-deletion workflow.
- Save non-sensitive confirmation records.
- Check whether account and identity records have separate retention rules.
Deleting a Recover backup does not erase blockchain history or move assets. It removes a recovery route. If the only other usable backup is already lost, deleting that route can create permanent lockout after device failure.
Who may benefit from Ledger Recover?
- A user comfortable with identity verification who is more likely to lose a physical phrase than face a targeted institutional attack.
- A household that cannot safely manage exposed recovery words but can maintain current identity documents and account access.
- A traveler or renter without a suitable long-term physical storage location.
- A user who understands that the service supplements a recovery strategy rather than guaranteeing access in every circumstance.
Who may prefer an offline backup?
- A user whose threat model requires minimal personal-data disclosure.
- A user in an unsupported or frequently changing jurisdiction.
- An experienced owner with tested geographically separated physical backups.
- A wallet protected by an additional passphrase whose recovery remains owner-managed anyway.
- A person unwilling to depend on recurring payment, identity providers or a manual claims process.
Neither group is automatically more sophisticated. A complicated offline system that heirs cannot use may be weaker in practice than a carefully evaluated service. Conversely, a convenient subscription can be inappropriate for someone who specifically chose self-custody to avoid identity-linked recovery.
Checklist before subscribing
- Define the failure being solved: device loss, damaged backup, incapacity or poor physical storage.
- Confirm current country, document, device and Ledger Wallet compatibility.
- Read the price, tax, renewal, cancellation and missed-payment terms.
- Read the Recover privacy policy and identify every relevant provider.
- Secure the subscription email with a unique password and phishing-resistant authentication where available.
- Download Ledger Wallet only from the official Ledger domain and run Genuine Check.
- Review enrollment on the trusted device screen before approving it.
- Never enter the Secret Recovery Phrase into a computer, phone, browser or support form.
- Record the existence of any separate BIP39 passphrase.
- Keep subscription and identity information current.
- Document an estate or incapacity plan; identity verification is not legal authority to administer assets.
- Review the arrangement annually and after provider, document or residence changes.
Estate planning and incapacity
Ledger Recover is designed to verify the enrolled user. It should not be assumed to transfer access automatically to an heir, executor or family member. Death and incapacity raise separate questions about legal authority, identity procedures, device possession and knowledge of any additional passphrase.
A complete plan should identify the wallet, authorized decision-makers, recovery method and relevant legal documents without placing a spendable secret in an ordinary will or public record. Consult an appropriate estate professional for the applicable jurisdiction. Test whether the plan remains understandable without exposing the recovery material.
Common Ledger Recover mistakes
- Believing a firmware update automatically uploads the wallet backup.
- Assuming the service stores a readable copy of the 24 words in one database.
- Typing recovery words into a website during a fake enrollment.
- Discarding the physical backup immediately after subscribing.
- Forgetting that a separate passphrase is not included.
- Relying on an expired or unsupported identity document.
- Confusing Ledger Recover with Ledger Recovery Key.
- Assuming cancellation, backup deletion and personal-data deletion are identical.
- Failing to secure the related email and subscription login.
- Expecting Recover to reverse a blockchain transaction or recover assets sent to the wrong address.
- Never checking whether country and device support changed.
Frequently asked questions
Is Ledger Recover mandatory?
No. It is an optional paid service. Creating a backup requires enrollment and user approval on a compatible Ledger device. Users can continue with their own recovery backup without subscribing.
Does Ledger Recover upload my 24 words?
Ledger describes the device as encrypting the underlying recovery entropy and splitting it into three protected fragments. The intended process does not ask the user to type or upload plaintext recovery words.
How many fragments are needed to recover?
The published design uses three fragments and a two-of-three restoration threshold. One fragment alone should not reconstruct the wallet.
Can Ledger Recover show me my Secret Recovery Phrase?
No. The service is designed to restore the wallet material to a compatible Ledger device, not reveal the 24 words to the subscriber.
Does it include a Ledger passphrase?
No. Ledger states that an optional BIP39 passphrase is not included. The exact passphrase still needs its own secure, tested recovery plan.
Is Ledger Recover the same as KYC?
Ledger describes it as identity verification rather than full financial KYC. It still involves government-issued identity evidence and biometric or liveness information, so users should review the current privacy terms carefully.
Can Recover reverse stolen crypto?
No. Recovery restores wallet access. It cannot reverse confirmed blockchain transfers, retrieve assets sent to an incorrect address or cancel a malicious smart-contract action.
Is Ledger Recover safe?
It uses encrypted fragments, a threshold model, device approval, HSM-backed providers and identity checks. It also introduces service, privacy, identity and institutional dependencies that an offline backup does not have. Safety depends on which set of risks better matches the user.
Should I destroy my written recovery phrase after subscribing?
Do not destroy the only independent recovery method without a deliberate replacement plan. Keeping both routes can improve resilience but also creates more secrets and locations to protect. Decide according to a documented threat model.
Final assessment
Ledger Recover changes wallet recovery from a possession-only model into a hybrid of device consent, threshold cryptography, protected providers and identity verification. Its value is practical: a verified owner may restore a wallet even after losing both the original Ledger and immediate access to the physical phrase. Its cost is not only the subscription. It also adds personal-data processing and reliance on multiple organizations and operational procedures.
The service may be reasonable for someone whose greatest risk is accidental loss and who accepts identity-based recovery. It may be unsuitable for someone whose priority is minimizing external trust and identity linkage. Before enrolling, verify current eligibility, understand the two-of-three fragment model, preserve any separate passphrase and decide what independent recovery route should remain.
Official sources and further reading
- Ledger Academy: What Is Ledger Recover?
- Ledger: Recover cryptographic protocol white paper announcement
- Ledger: Identity verification in Ledger Recover
- Ledger: Recover threat analysis and evaluation
- Ledger Recover privacy policy