Copilot's Memory of You Belongs to Your Employer, Not to Your Family

Microsoft's admin guidance is unusually direct about the location. "Memories, which include saved memories, details inferred from chat history and custom instructions, are stored in the user's Exchange mailbox in a hidden folder." Because they live in the mailbox, they inherit mailbox security and compliance behaviour, including Customer Lockbox and encryption at rest (Microsoft Learn, ms.date 18 November 2025, checked 29 July 2026).

One storage decision settles the whole ownership argument. On a work or school account the mailbox belongs to your employer's Microsoft 365 tenant. Not to you, and not to your estate.

Your prompts and Copilot's replies sit in a second place, as your Copilot activity history. Microsoft's privacy documentation, dated 9 July 2026, confirms that the prompt, the response and the citations to any grounding content are all retained, and that admins can view and manage that data through Content search or Microsoft Purview.

The retention documentation goes further into the plumbing. "Data from generative AI messages is stored in a hidden folder in the mailbox of the user who runs the AI app. This hidden folder isn't designed to be directly accessible to users or administrators, but instead, store data that compliance administrators can search with eDiscovery tools" (Microsoft Learn, ms.date 23 September 2025, updated 25 June 2026).

The mechanics, plainly, because families deserve them plainly and most coverage of this subject skips to sentiment:

• What happens to your Microsoft Copilot data when you die. Nothing moves and nothing is released. Saved memories, details inferred from your chat history and your custom instructions stay in your Exchange mailbox in a hidden folder, which on a work account your employer owns rather than your estate, and they surface in an export as a folder named CopilotMemory (Microsoft Learn, ms.date 18 November 2025, checked 29 July 2026).

• Who can read and export that memory. An administrator in your tenant holding the eDiscovery Manager role can open a case, search your mailbox for item class IPM.Contact, add the results to a review set, then review and export them (Microsoft Learn, ms.date 19 June 2026).

• Who can permanently delete that memory. An administrator holding the Search And Purge role can end the same workflow in a POST to the Microsoft Graph purgeData endpoint, capped at ten items per mailbox per run because Microsoft designed the call as an incident-response tool rather than a bulk eraser.

• What you can export yourself. On a work or school account, nothing. Deletion is the only user action Microsoft offers for activity history or for memory. Custom instructions are the exception, and Microsoft says they "can manually be exported by the user through Settings > Personalization."

• What your next of kin can get. For a Microsoft 365 work tenant there is no form, no nomination tool and no published request process. On a personal Microsoft account, Microsoft requires a valid subpoena or court order and states that even then it may be unable to release anything.

Two caveats sit over all of that, and both matter more than the detail. Copilot personalization and memory were still labelled preview in Microsoft's admin documentation as at 18 November 2025, page updated 22 May 2026, and preview behaviour changes without notice. And what your own tenant has configured, meaning retention periods, whether enhanced personalization is switched on, whether an eDiscovery hold sits on your mailbox, is set per tenant and visible only to your admins. Everything above is the platform default, not a statement about your company.

If you are here because a parent has died and you are trying to get into their Outlook account, this page will help you less than you want. It is written for the person whose data this is, while they are still around to act. If you use more than one assistant, what happens to your ChatGPT memories when you die is the hub for the whole question and sets out how the seven major assistants differ on export, nomination and deletion.

The route is documented step by step, and an administrator can follow the documentation line by line.

Copilot memories are stored with the item class IPM.Contact, and in an export they land in a folder named CopilotMemory. An administrator with the eDiscovery Manager role creates a case, runs a search against your mailbox, and adds the hits to a review set. "Saved memories and inferred memories from your chat history are discoverable using eDiscovery and Microsoft Graph Explorer." From the review set, they review and export (Microsoft Learn, ms.date 19 June 2026).

With the Search And Purge role, they can also delete, and the workflow ends in a POST to the Graph purgeData endpoint, capped at ten items per mailbox per run because Microsoft built the call for incident response rather than bulk erasure.

Custom instructions are the one part admins cannot reach. Microsoft says they "aren't yet discoverable" in eDiscovery or Content Search, and that they "can manually be exported by the user through Settings > Personalization." The word "yet" is doing real work in that sentence.

None of this leaves a trail. "Memory and personalization actions don't generate audit log entries in Purview." Nobody gets a record of what your memory contained or when it changed. Not the auditors, not your admins, not you.

Now set that against the family position. A spouse holding a death certificate and a grant of probate has no request form, no nomination tool and no queue to join. The only route runs through your employer, at that company's discretion, and no law we can find obliges the company to agree.

Concede the point properly, because it is the strongest thing the other side has: declining is defensible. A work mailbox holds other people's confidential material, other people's medical leave, other people's severance conversations. A compliance officer who refuses to hand a mailbox to a bereaved family is not being cruel. They are protecting everyone else in the file.

In the United States the refusal is not even custom, it is statute. RUFADAA, the digital-assets act adopted in most states, expressly does not apply to an employer's digital asset used by an employee in the ordinary course of the employer's business, so an executor's right of access stops at the company mailbox (Virginia Code section 64.2-117, a RUFADAA enactment, checked 29 July 2026). We are not aware of a comparable right in the UK, EU or Australia that would compel an employer to disclose an ex-employee's mailbox to next of kin. The mailbox is a corporate record. Your death does not change whose record that is.

Your employer can search Copilot's memory of you with a role assignment. Your family cannot reach the same memory with a death certificate, a grant of probate and a lawyer.

Two beliefs about deletion are worth taking away from you before you rely on either.

The first is that the interface tells you the truth. Microsoft says otherwise, in an Important callout on the retention page: "Messages visible in your AI apps are not an accurate reflection of whether they are retained or permanently deleted for compliance requirements." Deleted items move to a second hidden folder called SubstrateHolds, sit there for at least a day, and are permanently removed only when a timer job next runs, typically one to seven days later. The screen is a view, not an inventory.

The second belief is that clearing your chats clears what Copilot decided about you. Memory and chats are separate objects with separate lifecycles. Microsoft states plainly that "Deleting a conversation or message from Microsoft Purview or eDiscovery doesn't delete the associated Copilot memory," and separately that "Deleting a chat doesn't delete saved memories that were generated from that chat." Saved memories persist until you delete them from their own screen, in Settings then Personalization, which is a different screen from the one you have been using. Details inferred from your chat history clear within seven days only if you delete every chat where the information appeared. Every chat. Not the embarrassing one.

So the version of you that survives your own housekeeping is the inferred version. The conclusions, not the conversations.

Nothing gets wiped when you leave the job. Your Copilot history moves into a mailbox you can no longer sign into at all.

Microsoft's retention documentation covers the case directly. "If a user leaves your organization and their Microsoft 365 account is deleted, their Copilot and other AI app messages that are subject to retention are stored in an inactive mailbox. The messages remain subject to any retention policy that was placed on the user before their mailbox was made inactive, and the contents are available to an eDiscovery search" (Microsoft Learn, ms.date 23 September 2025, updated 25 June 2026).

Resignation and death arrive at the same address. The record of how you think, phrased in your words, sits in an inactive mailbox at a company you no longer work for, searchable by a compliance team you never met, while the people who would actually want to hear from you cannot get within a mile of that folder.

One more line on ownership, because it gets quoted at me a lot. Microsoft's Copilot privacy documentation states that "Microsoft doesn't claim ownership of the output of the service." That is a statement about Microsoft and nothing more. Whether the output is yours or your employer's is answered by your employment contract, not by a privacy page.

Start building your legacy Free build, 50 memories, no card required.

Three things are worth doing this week. Two of them have nothing to do with me.

Copy out your custom instructions. They are the only part of your Copilot personality you practically own, because you wrote them and you can lift them. Microsoft's admin documentation says they can be manually exported through Settings then Personalization, and the user-facing help article describes no export button, so in practice this means opening the panel and copying the text into a file you control. Two minutes. No administrator can purge, withhold, or forget to hand over a file already sitting on your own machine.

Then clear what you do not want sitting in a mailbox after you die. Deleting your activity history is something you can do yourself, though the button is buried several menus deep. Sign in to the My Account portal with your work or school account, go to Settings and Privacy, then Privacy, then Data options, open the Copilot activity history section, choose Delete history, tick Microsoft 365 Copilot and confirm. Anything Copilot helped you write that you saved into a file stays in the file, and the deletion is queued rather than instant (Microsoft Support, checked 29 July 2026).

And if you are on a personal Microsoft account, set up OneDrive Digital Legacy. In OneDrive settings you invite a trusted contact who has a Microsoft account, they accept the invitation, then you select Get code and share that code with them. They enter the code under Request access, and after a 72-hour waiting period they get read-only access to your OneDrive files and photos (Microsoft Support, checked 29 July 2026). The code does not change and does not expire, which is why Microsoft's own guidance suggests writing the code into your will or leaving the code with your executor. Files only. Not your mail, and not Copilot memory. Where Digital Legacy was never set up, the same page is blunt about the alternative: Microsoft "is generally unable to provide information to non-account holders."

A personal Microsoft account also gets the export a work account does not. In the privacy dashboard you can run Export all activity history, delivered as a CSV file. Consumer Copilot retains conversation history for 18 months by default (Microsoft Support, checked 29 July 2026), so on that side of the fence the clock is at least published.

If nomination is the pattern you want, Google's Inactive Account Manager and what it actually hands over is worth setting up in parallel, and what happens to your Gemini history when you die explains how far a nomination reaches into assistant memory.

Everything past that point needs a lawyer. For a deceased or incapacitated user's information, Microsoft's position is that it "must first be formally served with a valid subpoena or court order to consider whether it is able to lawfully release" that information, and Microsoft warns that "sending a request or providing a subpoena or court order does not guarantee that we will be able to assist you" (Microsoft Support, checked 29 July 2026). In Europe, documents are served on Microsoft Ireland Operations Ltd in Dublin. Germany is the one comfortable exception: customers there can contact Microsoft customer support directly with a death certificate, a copy of the deceased person's identity document, an inheritance certificate (Erbschein) or equivalent court documentation, and the requester's own identification.

Time is working against your family the whole way through that process. Microsoft's guidance states that Outlook.com and OneDrive accounts are frozen after one year of inactivity, with messages and files deleted shortly afterwards. The separate Microsoft account activity policy requires a sign-in at least once in a two-year period to keep the account open, with reference to section 4(a)(iv)(2) of the Microsoft Services Agreement for what a closed account means (both checked 29 July 2026). A family that spends eight months on probate before anyone thinks about the email can arrive to find the content already gone, subpoena in hand.

For the wider shape of who is allowed to act on your accounts at all, who controls your identity after you die is the concept doing most of the work, and it reaches well past Microsoft.

Microsoft sits at the harsh end of a range with no comfortable end. All seven publish some kind of self-serve export you can run while you are alive, though Copilot's only works on a personal Microsoft account. Google is the one platform shipping an advance-nomination tool that reaches account content, and Meta's legacy contact stops at the Facebook profile.

Every row checked against the vendor's own published policy on 29 July 2026. These policies change without notice, so treat the date as the important column.

Read the table as a whole and the pattern is not a Microsoft problem. Seven products, four of them holding the most candid material their users have ever typed, and between them one nomination tool. The industry built export buttons for regulators and forgot that users die.

And a transcript was never the answer anyway. Even a perfect export of everything Copilot ever held on you would be a record of your prompts. Your daughter, in 2049, will not arrive with a prompt. She will arrive with a question nobody thought to ask in 2026, and a folder of your work emails has no answer for her.

Everything above is why Afterlife.ai™ exists, and the pitch is narrower than this category usually admits. We do not stop death. We do not bring anyone back. What we build instead are Personas, and yours starts as a conversation and ends as a record you made on purpose, in an account with your name on the deed rather than your employer's.

A guide called Idy interviews you. No form and no questionnaire, just a conversation that keeps going and asks about the things that produced you. The decision you still defend. The argument you lost. The job you walked out of. What you do when a problem goes sideways at four on a Friday. Your answers become memories, and nothing gets manufactured around them. What you never said stays unsaid.

Your voice is cloned from your own recordings, so what your family hears later is the voice they know rather than a synthetic reading of your text. For the consent and verification side of that, whether voice cloning is safe sets out how a clone is protected against being lifted and reused.

You nominate who gets access. Named people, chosen by you, while you are here to choose them. Release runs through Executor Lock™, which opens on evidence and not on a phone call: a seven-day, evidence-verified process, and then a complete snapshot with nothing pruned and nothing down-weighted. What your family receives is the character you built, not a summary of one. How Executor Lock releases your record to the people you named sets the process out step by step.

While you are alive you can talk to what you have built, correct anything a memory has wrong, delete memories, and change who is nominated. Recording is open on every plan, hearing the voice back is metered at three playbacks a month on the free build, and what each Afterlife.ai plan includes covers the rest.

Three limits, because we build this and we know where the edges are. Fifty memories is a start and not a life, so anyone who stops after one sitting gets something thin, and I would rather say that here than let you discover the fact in ten years. We run on cloud infrastructure like everyone else, so owning your data means your account, your export and your deletion controls, not a private server in your spare room. And the export is honest without being total: one request returns a JSON file holding your profile, your memories, your own chat transcripts and the people you nominated, while your voice recordings and your cloned voice model stay outside that file today. Any company can fail, ours included. The design principle is that our failure leaves your family holding your material rather than nothing.

If the idea that anyone would want to talk to what you built feels like a stretch, that objection deserves reading rather than dismissal: I am not important enough to leave anything behind is the most common thing people say before they start, and the most common thing they retract afterwards.

Copilot is going to keep learning you either way. Every Tuesday email, every rewritten paragraph, every prompt you thought better of, all of that accruing in a hidden folder in a mailbox a compliance team can search and your daughter cannot open.

The only real decision left is which record your family gets. The one your employer holds, or the one you made on purpose.

Start building your legacy Free build, 50 memories, no card required.

• What happens to your ChatGPT memories when you die is the hub for this question across every major assistant, and OpenAI's answer differs from Microsoft's.

• What happens to your Gemini history when you die is the one to read next if you also use a Google account, because Google's advance-nomination tool works differently from Microsoft's.

• What happens to your Claude conversations when you die is the closest comparison for export, because Anthropic publishes a self-serve export and no nomination route at all.

• What happens to your Meta AI memories when you die matters if your assistant use is mostly inside WhatsApp or Instagram, where memory and messaging history are entangled.

• Google's Inactive Account Manager, and what it actually hands over is the one advance-nomination tool any of these platforms ships, and it is worth setting up even if you mostly live in Microsoft.

• How Executor Lock releases your record to the people you named is the release mechanism this page refers to, set out step by step.

• What an AI trained only on you can actually do covers the other side of the argument, about what you can deliberately build rather than what a vendor happens to keep.

Every platform claim here comes from primary sources: Microsoft's own admin and compliance documentation on Microsoft Learn, Microsoft's published support articles for account holders and bereaved families, statutory text for the legal points, and the equivalent published policies of the other six assistant vendors for the comparison table. Each carries the date Microsoft or the vendor published, and we quote that date rather than our reading of the page. Claims about our own product were checked against the running code and not the marketing site, which is why the export paragraph names what the export file does not contain.

What is not settled: Copilot personalization and memory are still labelled preview, so storage location, discoverability and retention can change; there is no published post-deletion retention window for Copilot, so we state none; whether custom instructions become discoverable in eDiscovery is explicitly open in Microsoft's own wording; and what a given employer has configured in its tenant is invisible from outside. The RUFADAA point is drawn from an enacted state version of the uniform act, and the exact wording varies between states. We could find no UK, EU or Australian equivalent that would compel an employer to disclose, but a negative finding is weaker than a citation, so we state that as a limit of our research rather than as settled law. Nothing on this page is legal advice, and estate law differs by country and by state.

If you think something here is wrong or has changed, report the error on our contact page and we will recheck the source and correct the page.

1. Microsoft Learn, "Manage Copilot personalization and memory", ms.date 18 November 2025, page updated 22 May 2026. Storage in the user's Exchange mailbox hidden folder, saved memories and custom instructions behaviour, IPM.Contact and CopilotMemory, admin discoverability, no audit logging. https://learn.microsoft.com/en-us/copilot/microsoft-365/copilot-personalization-memory

2. Microsoft Learn, "Search for and delete AI application data in eDiscovery", ms.date 19 June 2026. Item classes, eDiscovery Manager and Search And Purge roles, Graph purgeData, ten-item limit, memory not deleted with conversations. https://learn.microsoft.com/en-us/purview/edisc-search-copilot-data

3. Microsoft Learn, "Learn about retention for Copilot and AI apps", ms.date 23 September 2025, page updated 25 June 2026. Hidden mailbox folder, SubstrateHolds, one to seven day timer job, inactive mailbox on user departure. https://learn.microsoft.com/en-us/purview/retention-policies-copilot

4. Microsoft Learn, "Data, Privacy, and Security for Microsoft 365 Copilot", ms.date 9 July 2026. Storage of prompts and responses, admin management via Content search and Purview, ownership of output. https://learn.microsoft.com/en-us/microsoft-365-copilot/microsoft-365-copilot-privacy

5. Microsoft Learn, "Microsoft Purview data security and compliance protections for generative AI apps", ms.date 27 May 2026. Prompts and responses stored in the user's mailbox, eDiscovery search and export workflow. https://learn.microsoft.com/en-us/purview/ai-microsoft-purview

6. Microsoft Support, "Accessing Outlook.com, OneDrive and other Microsoft services when someone has died", checked 29 July 2026. Subpoena or court order requirement, Germany exception, service address in Ireland, one-year freeze, two-year expiry. https://support.microsoft.com/en-us/accounts-billing/manage/accessing-outlook-com-onedrive-and-other-microsoft-services-when-someone-has-died

7. Microsoft Support, "Microsoft account activity policy", checked 29 July 2026. Two-year sign-in requirement, Microsoft Services Agreement section 4(a)(iv)(2). https://support.microsoft.com/en-us/accounts-billing/manage/microsoft-account-activity-policy

8. Microsoft Support, "Preserve your digital legacy with OneDrive", checked 29 July 2026. Trusted contact setup, read-only access, 72-hour waiting period. https://support.microsoft.com/en-us/onedrive/preserve-your-digital-legacy-with-onedrive

9. Microsoft Support, "Delete your Microsoft 365 Copilot activity history", checked 29 July 2026. My Account portal path, scope of deletion, saved file content unaffected. https://support.microsoft.com/en-us/office/76de8afa-5eaf-43b0-bda8-0076d6e0390f

10. Microsoft Support, "Microsoft Copilot privacy controls", checked 29 July 2026. The 18-month default retention of consumer Copilot conversation history. https://support.microsoft.com/en-us/microsoft-copilot/microsoft-copilot-privacy-controls

11. Code of Virginia, Article 3.1, "Uniform Fiduciary Access to Digital Assets Act", sections 64.2-116 and 64.2-117, checked 29 July 2026. RUFADAA as enacted, including the exclusion of an employer's digital asset used by an employee in the ordinary course of the employer's business. https://law.lis.virginia.gov/vacodefull/title64.2/chapter1/article3.1/

12. Perplexity Help Center, "GDPR Compliance at Perplexity", last updated 28 July 2026, checked 29 July 2026. Right of access is self-serve via the Export my data button on the account details page. https://www.perplexity.ai/help-center/en/articles/11564568-gdpr-compliance-at-perplexity

13. X Help Center, "Contacting X about a deceased family member's account", checked 29 July 2026. Deactivation on a verified request with requester ID and death certificate, and no account access to anyone. https://help.x.com/en/rules-and-policies/contact-x-about-a-deceased-family-members-account

Platform policy checked: 29 July 2026. Last reviewed: 30 July 2026. This page is on a 30-day recheck cycle because Copilot personalization and memory are still marked preview in Microsoft's documentation.