How can you end access to shared accounts without erasing your digital history?

Separate ownership, access and memory

A shared account can mix three different things: who owns it, who can sign in and which records belong to each person's history. Changing a password addresses only part of access; it does not decide who should retain photos, messages, files, lists, receipts or jointly created work.

List the accounts and what is at stake before changing anything. Trans, travesti, non-binary, femboy, gay, lesbian and bi experiences are different, not synonyms; an ordinary file may reveal a chosen name, support network, health, location or relationship that must stay private.

Decide where every asset goes before revoking

Make a minimal inventory of primary email, cloud storage, photos, social media, channels, calendars, subscriptions, domains, shops, documents and recovery methods. Record the owner, continuing users, payer and whether ownership or an admin role can be transferred.

Classify each asset as individual, shared, safely duplicable or disputed. If authorship, money or a legal duty is genuinely contested, preserve the current state and seek appropriate advice before deleting or transferring it.

Preserve a readable, proportionate copy

Use the platform's official export and select only necessary data. Google Takeout can create a copy of chosen data; for collaborative services, ownership transfer may preserve structure and continuity better than downloading and uploading again.

An export is not permission to copy everything. Exclude other people's intimate content, credentials and unnecessary conversations. Keep the copy privately, confirm it opens, note the date and leave no temporary archive on a shared computer.

Transfer roles without transferring identity

If a page, folder, channel or calendar must continue, add the new owner or admin first, verify that they can operate it and only then remove old access. Do not hand over an entire personal account merely because it contains one shared asset.

Authorship and administration are different. Preserve credit, dates and creation context where relevant, while removing recovery details, keys, sessions and payment methods that should not travel with the asset. History can remain without letting someone speak as another person.

Revoke access in an order that prevents lockouts

Start with the root account used to recover others. Update recovery email and phone, set a unique password, enable MFA controlled by the owner and issue fresh backup codes. Then end sessions and remove devices, connected apps, app passwords, integrations and old admin roles.

Do not assume a password change ends every route. Sessions, tokens, forwarding, albums, calendars and family groups may remain active. Review each layer and test legitimate access after every step.

Change the plan when coercion or abuse is possible

If the other person may retaliate through stalking, blackmail, outing, violence, money or file destruction, do not make a surprise revocation from a monitored device. Use a safe device, preserve essential evidence and plan physical, financial and housing support before visible changes.

Apple Safety Check can help review sharing and access, but no single screen covers every service. Do not notify through a channel the other person controls, and do not use history preservation as a reason to keep unwanted contact or surveillance.

Close with proof, deadlines and safe disposal

Confirm that everyone can access only what was agreed, essential files open in their copy or new destination, and billing and recovery point to current owners. A simple asset-action-owner-date list prevents omissions without storing sensitive content.

Set a short deadline to delete transition copies and revoke temporary links. Healthy digital separation preserves enough memory and authorship, removes access that no longer has a purpose and returns control of each person's presence.

• Map accounts, assets, owners and recovery routes.
• Classify individual, shared, duplicable and disputed material.
• Export only what is needed and test the copy.
• Transfer ownership or roles before removing access.
• Secure the root account and MFA first.
• End old sessions, tokens, apps and sharing.
• Plan safety first when abuse is possible.
• Delete temporary copies on the agreed date.