Three Things Have to Line Up
An executor with a certified death certificate and valid letters testamentary can walk into this expecting it to work like a bank account. It does not. Requests get refused, and the refusal usually is not a mistake.
What is actually happening is that three separate questions are being answered, in order, and a "no" on any of them stops the whole thing:
- Does state law entitle a personal representative to this? Usually yes for some of it, and usually no for message content.
- Will the provider hand it over, and by what process? Each one has a different answer, and some of those answers require a court.
- Can anyone actually sign in? This is where password managers, two-factor codes, and locked phones decide the outcome regardless of the first two.
Most of the frustration in this area comes from working on question 2 or 3 without understanding question 1 — or, more expensively, from spending money on a court petition that question 3 was going to defeat anyway.
Layer 1: What the Law Actually Gives You
Since 2015, states have been adopting a uniform act on this subject — the Revised Uniform Fiduciary Access to Digital Assets Act, usually shortened to RUFADAA. What matters is your state's enacted version, which may sit in an unexpected chapter of the code. Florida's is a clean worked example because the numbering is easy to follow, so the citations below use it; check your own state's text, because definitions and defaults vary.
Content versus catalog
The single most important distinction in the statute is between two things that sound similar:
| Term | Statutory definition | Default for a personal representative |
|---|---|---|
| Content of an electronic communication | "information concerning the substance or meaning of the communication" (Fla. Stat. § 740.002(5)) | Not disclosed unless the user consented or a court directs it (§ 740.006) |
| Catalog of electronic communications | "information that identifies each person with which a user has had an electronic communication" (Fla. Stat. § 740.002(4)) | Disclosed, unless the user prohibited it or the court directs otherwise (§ 740.007) |
Read the second row again, because it is more useful than it first appears. The catalog is the record of who the deceased was communicating with and when. For an executor trying to build an asset inventory, that is often the actual goal — not reading the emails, but finding out which bank, which brokerage, which insurer, which subscription. A catalog disclosure plus other non-content digital assets is the default entitlement, and it does not require anyone's consent.
Both disclosures require the same paperwork from the personal representative: a written request, a certified copy of the death certificate, and proof of authority such as letters of administration or a court order.
Why content is walled off
The content rule is not the states being cautious. It is federal law sitting underneath them. The Stored Communications Act provides that a provider of electronic communication service to the public "shall not knowingly divulge to any person or entity the contents of a communication" held in storage (18 U.S.C. § 2702(a)(1)), with a parallel bar for remote computing services in § 2702(a)(2). One of the listed exceptions is disclosure made "with the lawful consent of the originator or an addressee or intended recipient of such communication" (§ 2702(b)(3)).
That exception is the hinge. A provider that hands over a dead user's email content without consent or a court order is exposed under federal law. This is why "but I'm the executor" does not move a provider, and why the state statute carefully routes content through consent or a judge.
The priority order nobody checks first
The statute sets a hierarchy, and it runs in an order that surprises people:
- An online tool. "[A] direction regarding disclosure using an online tool overrides a contrary direction by the user in a will" (§ 740.003(1)).
- The will, trust, or power of attorney. A direction the user gave "overrides a contrary provision in a terms-of-service agreement" that does not require separate, affirmative assent (§ 740.003(3)).
- The terms of service. Where the user gave no direction at all, fiduciary access "may be modified or eliminated by a user, by federal law, or by a terms-of-service agreement" (§ 740.004(3)).
So the first thing to do is not to draft a letter. It is to find out whether the deceased used one of the providers' own tools — because if they did, that instruction wins, and the process is a form rather than a petition.
Layer 2: The Providers, One at a Time
Each large provider has built its own process, and they differ enough that a request written for one will fail at another.
| Provider | Pre-death tool | Post-death route without the tool | Will it release message content? |
|---|---|---|---|
| Inactive Account Manager | Deceased-user troubleshooter (three separate request types) | "In certain circumstances," after review | |
| Apple | Legacy Contact (access key) | Court order naming you as rightful inheritor | Via Digital Legacy / court order; not end-to-end encrypted data |
| Microsoft | None equivalent | Subpoena or court order served on its registered agent | Only through that legal process, with no guarantee |
Google maintains both halves — a tool for the living and a process for the bereaved.
Inactive Account Manager lets a user nominate up to ten trusted contacts to receive specified categories of account data after a chosen period of inactivity. Google watches signals such as recent sign-ins, My Activity, Gmail usage, and Android check-ins to decide when that period has elapsed. Contacts are told nothing at setup; after the trigger they receive an email the user wrote in advance, with a download link and a Google-added footer explaining why they are receiving it. A phone number is required so that only the intended contact can download. Where no plan exists, Google may delete an account that has been inactive across Google for at least two years (About Inactive Account Manager).
Without a plan, Google's deceased-user troubleshooter offers three distinct requests: close the account, submit a request for funds from the account, or obtain data from the account. Google says that "[i]n certain circumstances we may provide content from a deceased user's account," that it "cannot provide passwords or other login details," and that any decision "will be made only after a careful review."
There is one ordering trap here that is worth more than anything else in this section. Google states that if you choose to close the account, it "is unable to process any request to turn over the contents of the account at a later date." Closing is the request people instinctively make first, because it feels tidy. Make the data request first, and only close the account after it has resolved.
Apple
Apple's two routes are far apart in cost.
With a Legacy Contact, the designated person holds an access key. Apple notes the key "may be in the account settings, printed out, or in estate planning documents" — so this is worth hunting for in a filing cabinet before concluding there isn't one. The request starts at Apple's Digital Legacy site.
Without one, the U.S. route is a court order, and Apple specifies what it must say: the name and Apple Account of the deceased person, the name of the next of kin requesting access, that the deceased was the user of all accounts associated with the Apple Account, that the requestor is "the decedent's legal personal representative, agent, or heir," and "[t]hat Apple is ordered by the court to assist in the provision of access to the decedent's information" (Request access to a deceased family member's Apple Account). Apple also states that "[o]nly one person can request access to a deceased person's Apple Account" — so if several family members are circling, decide who it will be before anyone files.
Two limits deserve to be read before any money is spent. "Some data might be end-to-end encrypted and Apple isn't able to decrypt it." And a device locked with a passcode is "protected by passcode encryption," which Apple cannot remove without erasing the device. A court order does not change the mathematics of either one.
France, Germany, Japan, Australia, and New Zealand accept "alternative documentation and process instead of a court order." The United States does not.
Microsoft
Microsoft is the most restrictive of the three and says so directly: "For privacy and other legal reasons, we are generally unable to provide information to non-account holders." Its route for account contents is legal process — Microsoft "must first be formally served with a valid subpoena or court order," will "only respond to non-criminal subpoenas and court orders" served on its registered agent in the requesting party's state or region, does not accept faxed or emailed requests, and warns that "sending a request or providing a subpoena or court order does not guarantee that we will be able to assist you" (Accessing Outlook.com, OneDrive and other Microsoft services when someone has died).
Microsoft also publishes the clocks, and they are the tightest of the three. Outlook.com and OneDrive accounts "will be frozen after 1 year" of inactivity, with files and email deleted shortly after. Without credentials, the account "will be closed automatically after two (2) years of inactivity." If you do have the credentials and close the account yourself, you can reopen it within 60 days by signing in; after that Microsoft "permanently delete[s] the account and its data."
Germany and China are the two places where Microsoft's page describes a documented next-of-kin path rather than legal process, with country-specific document lists.
Layer 3: Password Managers
This is the layer where the law simply does not help, and it is worth understanding why.
A password manager is built so that the vendor cannot read the vault. The encryption key is derived from the master password, which the vendor never stores. That is the entire value proposition. It also means there is no administrator to appeal to, no account-recovery flow that produces the plaintext, and no court order that can compel a company to produce something it does not possess. An executor who understands this stops wasting weeks on support tickets.
What does work is a feature the user had to enable while alive.
Bitwarden's Emergency Access is a good model for how these work. A user designates trusted contacts at one of two levels. "View" lets the contact read every item in the individual vault, including login passwords and attachments. "Takeover" has the contact create a new master password, which replaces the previous one and removes any existing two-step login methods. The flow is: the holder invites a contact, who has five days to accept; the holder confirms them; later the contact submits an access request; the holder is emailed and may approve or reject it; and if they do neither, the request is approved automatically once a wait time the holder chose has expired (Bitwarden Emergency Access). That auto-approval on a timer is precisely the post-death behavior families need. Adding trusted contacts requires a premium or paid-organization plan.
Other managers approach it differently — a printed recovery kit containing a secret key, or a recovery path through a family-plan organizer. The common thread is that it has to be set up in advance, and the question for an executor is only whether it was.
If it was not, do not treat the vault as the path. Rebuild access institution by institution instead: each bank, insurer, and brokerage has its own deceased-customer process that runs on letters testamentary and a death certificate, not on a password. Our guides to finding a deceased person's bank accounts and building the estate inventory cover that route.
One related warning. Enabling "Takeover" style access, or resetting an account password you can reset, often removes the two-factor methods tied to it. That can be the right call — but if that account is the recovery address or authenticator for a dozen others, do the irreplaceable downloads first.
Cloud Photo Libraries: Preserve Before You Negotiate
Photographs are usually what the family actually cares about, and they are the asset most likely to be lost while everyone argues about process.
Three things are true at once:
- Legally, photos stored in an account are "other digital assets" rather than communication content, so they sit in the more accessible category under the statute (§ 740.007) — better than email content, in principle.
- Technically, some of it may be end-to-end encrypted and genuinely unavailable to the provider, as Apple states on its own support page.
- Commercially, the storage is usually a subscription, and the subscription is usually paid by a card that is about to be closed.
The third one is what bites. Nobody has ever lost a photo library to a legal doctrine; people lose them when the card stops working, storage is downgraded, and the provider's own retention schedule runs.
So the sequence is: if anyone living has access to a signed-in device or the credentials, export everything now. Both Google and Apple offer full data exports. Do that before cancelling cards, before closing accounts, before resetting a phone, and before filing anything with a court. Preservation is reversible. Deletion is not.
A phone or tablet that is already unlocked and signed in is the single most valuable object in this whole exercise. Do not reset it, do not let it run out of battery for weeks, and do not remove it from the account.
Domain Names: A Bill Nobody Is Watching
Domain names are the quietest item on this list and the easiest to lose outright, because a domain is not a thing you own permanently — it is a registration that expires on a date.
If the deceased ran a business, a side project, or a personal site, there may be a domain renewing annually on a card that is about to be cancelled, with renewal notices going to an email account nobody can open. Our guide to what happens to a business when the owner dies covers the wider business side; this is the piece that fails on a timer.
Transferring the registration to the estate or an heir is a Change of Registrant under ICANN's Transfer Policy. The mechanics:
| Step | What the policy requires |
|---|---|
| Trigger | A "Material Change" to the registrant's name, organization, or email address. Any change to the registrant email address counts; a pure typo fix does not. |
| Confirmation | The registrar must obtain confirmation from both the new registrant and the prior registrant (or their designated agents) through a secure mechanism. |
| Timing | The registrar processes the change within one day of receiving both confirmations and notifies both parties. |
| Lock | A 60-day lock on inter-registrar transfers follows the change. The holder may opt out, but only before the change request is made. |
| Denial | The registrar must deny the change if the registration has expired beyond the point where it can be renewed or transferred, if it was not properly authorized, or if a UDRP/URS/TDRP proceeding or court order prohibits it. |
Two points matter for an executor. First, the policy expressly excepts the case where "a court order requires updating the Prior Registrant's information" — so a probate order can stand in for the prior registrant's confirmation, which is otherwise impossible to obtain from a deceased person. Second, and more urgent: check the expiration date and the payment method first. A registrar must deny the change once the registration has lapsed past recovery, and an expired domain that gets re-registered by someone else is simply gone. Fifteen minutes spent confirming the renewal date beats any amount of paperwork afterward.
The Order of Operations
Most of the avoidable losses in this area are sequencing errors rather than legal defeats.
| Priority | Action | Why the order matters |
|---|---|---|
| First | Find and keep any unlocked, signed-in device; keep it charged and on the account | It defeats most of the access problem without any process at all |
| First | Export irreplaceable data — photos, documents — wherever you already have access | Preservation is reversible; retention schedules are not |
| First | Check for an online tool: Inactive Account Manager, Legacy Contact, a password-manager emergency contact, a printed recovery kit | By statute this direction outranks the will — and it skips the court |
| Early | Identify the renewal dates and payment cards behind storage subscriptions and domains | These are the only items with hard, provider-set deadlines |
| Early | Confirm the domain's expiry and that the card on file still works | A lapsed registration cannot be transferred at all |
| Early | Request the catalog and non-content digital assets, with the written request, certified death certificate, and proof of authority | This is the default entitlement and often answers the asset-inventory question |
| Then | Make any data request before any account-closure request | Google states it cannot turn over contents after a closure |
| Then | For Apple without an access key, or Microsoft generally, assess whether a court order is worth it | Weigh it against end-to-end encryption and passcode limits, which no order overcomes |
| Later | Memorialize or close social accounts | See closing social media accounts |
| Later | Freeze credit and watch for fraud on identities that are now attractive targets | See preventing identity theft of the deceased |
| Ongoing | Record each account, its status, and what was recovered, in the estate inventory | Digital assets are reportable estate property, not a side quest |
If the estate includes cryptocurrency, that is a materially different problem — private keys are not recoverable by any process, and self-custodied holdings behave nothing like an account with a customer-service department. Our guide to cryptocurrency after death covers it.
Where Professional Help Earns Its Cost
Much of this is organizational, and an executor who understands the content/catalog split and the ordering rules can do most of it alone.
An estate attorney earns their fee in a few specific places: drafting the petition when Apple's court-order route is genuinely necessary, and getting the order to recite the elements Apple actually requires rather than generic language a provider will reject; responding to a provider that has refused a request you believe the statute entitles you to; handling the situation where a will or trust contains digital-asset language that conflicts with an online tool the deceased set up later; and advising where a business, client data, or intellectual property sits inside a personal account, which raises duties beyond the probate code. Where the deceased lived in one of the states that require counsel to administer probate at all, that decision is made for you.
None of that means the whole category needs a lawyer, and none of it means it does not. It means a narrow slice of the work is where advice changes the outcome — and knowing which slice puts you in a position to make an informed decision about whether to bring in professional help.
How SwiftProbate Helps
SwiftProbate is probate task management software. It helps you understand what needs to happen in an estate, organize documents and deadlines in one place, and keep track of what is done and what is still open.
Digital accounts are a good illustration of why that matters, because the work is not one task. It is a search for online-tool directions that outrank the will, a different request process at each of three providers, a written request plus certified death certificate plus proof of authority for each one, a strict ordering rule about data before closure, a set of renewal dates and payment cards that will expire whether or not anyone is watching, a domain registration with a hard deadline and a two-sided confirmation requirement, a password vault that may be permanently closed, and a list of discovered accounts that then has to feed the estate inventory.
Each piece is manageable. What gets lost is the sequence — and in this particular area, losing the sequence is how a photo library or a domain name disappears for good.
SwiftProbate keeps that as a tracked list rather than something you are holding in your head, with the death certificates, letters, provider correspondence, and exported data attached to the estate instead of scattered across an inbox.
If you are earlier in the process, the step-by-step probate checklist lays out the overall sequence, letters testamentary explained covers the proof of authority every provider in this article asks for, and the estate inventory checklist covers where digital assets belong once you have found them.
SwiftProbate provides software to help navigate the probate process. SwiftProbate is not a law firm, does not provide legal advice, and is not a substitute for the advice of a licensed attorney. No attorney-client relationship is created by using this service. Probate laws vary by state and county.