Start with the item you want someone to recover
“My family can get into my Google or Apple account” sounds like a complete plan. It leaves an important question unanswered: get into it to do what?
Recovering family photographs, reading an instruction sheet, unlocking a phone, and restoring a Bitcoin wallet are different tasks. A successful outcome for one does not prove the others will work. Begin with an asset inventory that gives each task its own row.
The useful question is not which company has the better inheritance feature. It is which service holds the information your contact needs, and what remains outside that service. Many households need both features plus a separate wallet plan.
Compare the two handoff routes
The table summarizes the provider documentation checked on September 12, 2026. Check the linked instructions again before changing settings or making an actual request.
| Question | Google Inactive Account Manager | Apple Legacy Contact |
|---|---|---|
| What starts the process? | The account reaches the inactivity period configured by its owner | A contact requests access after the owner's death |
| What is the main job? | Notify chosen people and optionally share selected account data | Provide access to certain Apple Account data after review |
| What must be prepared? | Contact details, sharing choices, and an inactivity plan | A designated contact and their access key |
| What should not be assumed? | A notification is proof of death or authority to spend assets | Data access includes saved passwords, passkeys, or every purchase |
These are different mechanisms, not interchangeable settings. See Google's feature description and Apple's introduction. The final row describes planning boundaries, not a determination of anyone's legal rights.
Set up Google without creating an email dependency loop
In Inactive Account Manager, the owner chooses the waiting period, recipients, and data-sharing options. Google evaluates several activity signals rather than merely whether one device is powered on. It does not notify contacts during setup, so discuss the arrangement directly.
Our recommended preparation checklist is:
- Name the exact personal account in your private inventory. Avoid an ambiguous instruction such as “check Gmail.”
- Decide what the recipient actually needs. An instruction document and a private photo archive may have different audiences.
- Verify the recipient's contact details with them. Ask where they will look for an unexpected but legitimate notification.
- Record the chosen settings and review date without copying passwords into the inventory.
- Check the destination of every instruction link. A document that requires the unavailable owner's login creates a circular dependency.
Treat inactivity as a reason to verify circumstances, not an automatic instruction to transfer assets. Tell the recipient how to reach a second trusted person before taking consequential action.
Set up Apple and preserve the access key independently
On a supported Apple device, follow Apple's Legacy Contact setup instructions. Confirm that the intended contact has received the access key, and keep a protected copy that does not depend solely on opening the owner's account. This is not the same key as a wallet seed or a PingVaults recovery phrase.
Apple's request procedure requires the access key and death-related documentation; documentation varies by country or region. Apple reviews requests, and cannot retrieve or replace a lost access key. Do not assume that naming the contact is the entire handoff.
Prepare three short notes for the recipient:
- Where to start: the official Apple support page, not a link supplied by an unknown helper.
- What to locate: the protected key copy and the person coordinating required documents.
- What to preserve: a list of wanted records, with a destination for authorized downloads.
Apple currently describes access as lasting three years from approval of the first Legacy Contact request. Include a reminder to preserve needed data after approval, rather than treating this as permanent cloud storage. The same request guide explains this limit.
Keep cloud data separate from device and wallet recovery
Apple's accessible-data list covers categories such as iCloud Photos, Notes, and iCloud Drive files, while excluding iCloud Keychain information and purchased content. The absence of saved passwords is a real planning gap if your instructions depend on them.
Device access is another boundary. Apple says it cannot remove an unknown device passcode without erasing the device. Do not erase a phone as an exploratory step when locally stored information may still matter. Record what needs preservation and get appropriate help first.
For a BIP-39 wallet, the mnemonic and any additional passphrase participate in generating its seed; an Apple or Google account designation cannot reconstruct missing wallet material. See the BIP-39 specification and our wallet credential comparison. Other wallet designs have different recovery requirements, so record the actual setup rather than assuming all wallets use the same words.
A cloud file may explain where wallet recovery starts. That does not make a general-purpose cloud note an appropriate place to collect every spending secret.
A fictional household with three separate jobs
This example is fictional, not a customer case or a tested service outcome.
Maya keeps family photos in iCloud, household records in Google Drive, and Bitcoin in a hardware wallet. Her brother is comfortable organizing documents but has never restored a wallet.
| Job | Planned starting point | Question still to resolve |
|---|---|---|
| Preserve photos | Apple legacy instructions and protected access-key copy | Where will authorized downloads be stored? |
| Locate household records | Google's selected data-sharing arrangement | Can the brother identify the current instruction version? |
| Coordinate wallet recovery | Separate wallet instruction sheet | Who can assist without taking possession of all secrets? |
Maya does not solve the third row by forwarding a seed phrase. She identifies the missing role, checks the backup arrangement, and plans a rehearsal. Our contact-selection guide helps separate the organizer from the technical helper.
Rehearse the map without triggering a real claim
Use a harmless sample document and a fictional inventory to check whether the contact can find the right instructions. Ask them to explain the difference between an Apple access key, a device passcode, and wallet recovery material in their own words.
Record confusion as an unresolved issue. Do not simulate a death claim, switch off normal account activity for months, or expose real wallet secrets merely to test whether instructions are understandable. A family recovery drill should have a defined scope and stop conditions.
PingVaults can be another place to organize encrypted instructions; the digital inheritance vault guide explains its role. Keep a tested export and an independent route to its recovery phrase. Adding a vault does not replace either provider's process or the wallet's recovery requirements.
Common digital legacy questions
What if no Google plan was configured?
Use Google's deceased-user request process. Google reviews requests and does not supply passwords or login credentials. It also warns that closing an account prevents a later request for its contents. Clarify the objective before requesting deletion.
Can my contact sign in as me to deal with everything?
Do not build the plan around impersonation. Use the provider's authorized procedure and distinguish locating information from permission to manage or distribute assets. A saved login is not a universal authorization document.
What if someone offers to unlock everything for a fee?
Stop and independently verify their identity and proposed method. Never provide seeds or private keys to prove ownership. Read the recovery-scam warning signs before accepting remote help.