A safe exit closes four different doors
Leaving a companion app is not one button. Signing out ends a session, cancelling a subscription changes future billing, deleting the account starts the provider’s removal process, and uninstalling removes software from one device. Any one of these can leave the other three unchanged. A safer exit uses a four-state matrix and a deletion receipt. The matrix records each action and its result; the receipt records what happens to live account data, backups, connected providers, local files and exports. This avoids two common mistakes: uninstalling first and losing the only deletion route, or assuming an account confirmation also erased copies the user created elsewhere.
Map the four exit states before acting
Create four rows: session sign-out, subscription cancellation, account deletion, and app removal. For each, record where the control lives, whether it is reversible, what confirmation appears and what remains. Google Play’s current policy draws a firm product distinction between temporary deactivation and account deletion, and it expects covered apps to provide both an in-app route and an external web resource. Apple separately notes that deleting an iPhone or iPad app does not automatically cancel in-app subscriptions. These are platform examples, not proof that every service behaves identically. Use them to ask precise questions before you remove access.
Export only what has a continuing purpose
Decide whether anything needs to be kept. Request an export only for a defined purpose such as preserving selected media or moving records; do not create a full archive merely out of habit. Note the export cutoff, categories and destination, open a small sample, then give the copy a deletion date. Save essential support references outside the app without copying private conversations into an unprotected note. If there is no continuing purpose, skipping the export reduces the number of copies that need cleanup. Export is not deletion, and an exported file will remain after the account disappears until its owner removes it.
Cancel billing through its actual owner
Find who bills you: the app’s website, Apple, Google Play or another provider. Cancel through that billing owner and capture the effective end date rather than relying on a missing app icon. Check whether cancellation ends renewal immediately or leaves access until the current period closes. Do not confuse deleting a companion profile or character with deleting the billing account. A payment receipt need not contain conversation content; keep only the subscription name, account identifier, cancellation status and date. If the deletion flow says billing must be handled first, finish that step and then return to deletion.
Submit deletion and capture its stated scope
Start account deletion from the authenticated settings or the service’s official external page. Read the confirmation screen before accepting: does it name messages, journals, images, profile fields, saved memories and derived preferences? Does it state a waiting period, a reversal window, identity check or retained category? Google Play’s account-deletion guidance says covered developers should explain additional steps and retained data, including where service providers process account data. Record the request number, submission time, stated completion time and exact scope. Avoid placing private content in a free-text support ticket unless it is necessary to identify the account.
Track backups and connected processors separately
Backups need their own line because their timing may differ from live systems. The ICO’s current guidance, in the circumstances where its erasure rules apply, says organisations should be clear about backup handling; a backup may remain until scheduled overwrite while being put beyond use. Do not turn that conditional guidance into a universal deadline. Instead, ask the provider for its stated backup schedule, whether restored backups reapply deletion markers, and which retained categories remain usable. Also list connected sign-in, cloud, analytics or storage providers. A deletion receipt is incomplete if it simply says “all gone” without describing these boundaries.
Clean devices, downloads and shared links
After confirmation, remove local downloads, exported ZIP files, extracted folders, cached media you intentionally saved, cloud uploads and public or private share links. Revoke the app’s device permissions and connected-account access where those controls still exist. Then uninstall from each device. If you used a shared computer, clear the specific downloaded files and sign out without wiping unrelated browser data. Keep a minimal receipt containing dates, scope and support identifiers, not a duplicate of the content you wanted removed. This local cleanup is the part only the user can fully inventory.
Verify the end state without logging back in casually
Verify against the promised state. Check the provider’s deletion-status page or confirmation email first. If a post-completion sign-in attempt is part of the documented verification route, use it once and record the outcome; repeated sign-ins may cancel a grace-period request on some services. Look for an active subscription separately. Test old shared links from a signed-out view only when safe to do so. A failed login alone does not prove every backup or processor copy is gone, so report each result narrowly: account inaccessible, renewal cancelled, public link closed, local export removed, provider states backup overwrite by a given schedule. That is a useful receipt without claiming invisible facts.
Common questions
Is signing out the same as deleting the account?
No. Signing out normally ends the current session while the account and stored data remain.
Should I uninstall before requesting deletion?
Usually keep access until the official request and confirmation are captured, then uninstall after local cleanup.
Does deletion automatically cancel a subscription?
Do not assume so. Check the actual billing owner and record the cancellation state separately.