Export Your Data Before You Delete: Why the Download and the Deletion Are Two Different Steps

Deleting an online account is not the same as taking your data with you. The Information Commissioner’s Office, which enforces UK data-protection law, makes this explicit: you can request your personal data in an accessible, machine-readable format such as CSV, and you can ask for direct transfer to another organisation if technically feasible. But receiving that export does not automatically erase the original. The ICO warns that organisations may not delete data simply because they have handed it over, and a separate erasure request is required if you want the service to purge its copies. The practical consequence is simple. Anyone leaving a platform must export first, verify what the archive contains, then deliberately choose whether to deactivate or delete. Reversing the order risks locking yourself out while your data remains on corporate servers.

The Portability Right and Its Limits

The right to data portability sounds comprehensive, but it delivers specific things and withholds others. Under ICO guidance, you are entitled to your own personal data—the material you provided and the traces generated by your activity—in formats that other services can read. CSV files, JSON exports, and structured archives satisfy this requirement. What you do not receive automatically is deletion. The portability mechanism is built for transfer, not for termination. A user who downloads a Google archive through Google Takeout, for instance, has exercised a portability right. Google confirms that this download does not delete the underlying data from its servers. The export and the erasure are separate transactions, and only the second removes the source material.

This distinction matters because the two actions have different deadlines. A portability request must be fulfilled within one calendar month in most cases. An erasure request, made under the separate right to be forgotten, runs on its own timeline and may involve additional verification. Requesting your archive does not queue you for deletion. The service retains everything until you explicitly demand its removal, and even then, retention periods may apply for legal or security purposes. The ICO notes that organisations cannot use the portability process as a shortcut to satisfy erasure obligations. If you want out, you must ask twice: once for the copy, once for the purge.

What Disappears From View and What Stays

Exported archives are snapshots, not complete records. Google’s documentation states that deleted activity is immediately removed from view and stops being used to personalise the user experience. But "removed from view" is not deleted from servers. The material may persist in backup systems or aggregated datasets even when it no longer appears in your account interface. Google Takeout, the company’s export tool, does not include data already deleted or data caught in the deletion process. If you have been cleaning house—remising old emails, clearing search history, deleting photos—those deletions precede the archive. The export captures what remains, not what was.

This creates a timing problem. Users who sanitise their accounts before requesting a download may inadvertently strip their own archive of material they wanted to keep. The service, meanwhile, may retain sanitized versions or activity logs that never appear in the export. Google’s deletion summary page, displayed before final account termination, lists what will be deleted by service category. But this summary does not necessarily match the export contents. The gap between "what I can download" and "what they will delete" is where users lose track of their own information.

Facebook’s Export-First Architecture

Facebook offers the clearest illustration of how platforms structure the export-before-delete flow. The service provides a "Download a copy of your information" tool, accessible through settings, and users with additional Facebook profiles can generate separate archives for each identity. The tool presents two scopes: "Available information," which captures standard profile and timeline data, and "Specific Types of Information," which adds data logs and granular activity records. CNET reported in 2025 that the "Available information" default excludes data logs unless the deeper option is manually selected. Users who accept the standard export leave behind a complete record of their platform behaviour even after account termination.

Format and quality settings introduce further variation. Facebook allows HTML output for human-readable browsing and offers a "High" media quality setting that preserves full-resolution photos and videos. The alternative compresses media to smaller files. These choices affect whether your archive serves as a functional replacement for the original service or merely a reference copy. Users who plan to migrate to another platform or to local storage must match their export settings to their intended use.

The deletion path itself branches. Facebook’s Account Center routes users through Personal details, then Account ownership and control, then to a choice between Deactivation or deletion. Deactivation preserves data and allows reactivation; deletion begins a permanent erasure process. The two options sit side by side in the interface, and the wrong selection either strands data indefinitely or initiates irreversible loss. The export tool remains available for deactivated accounts but not for accounts in deletion. Sequence matters absolutely: download, then decide, then delete.

The Gaps Users Miss

Even careful exporters leave material behind. Facebook’s data logs, which include detailed interaction records, require explicit selection and do not appear in standard archives. Google Takeout excludes anything already deleted, including material removed during the export process itself if the user has been pruning. Neither platform guarantees that shared content—posts visible to friends, collaborative documents, photos in shared albums—travels with the export. The portability right covers personal data, not social data. Comments you wrote on others’ posts may remain on their profiles even after your account vanishes.

The archive formats themselves create practical barriers. Google Takeout delivers exports as.zip or.tgz archives, with optional splitting into 2 GB or 10 GB chunks. Large accounts spanning years of Gmail, Drive, and Photos activity can generate dozens of files. Delivery options include email links, direct export to Google Drive, or transfer to Dropbox, OneDrive, or Box. Each route imposes its own storage limits and expiration dates. Email links typically expire after a set period; cloud transfers consume quota on the destination service. Users who request exports without planning for file size and storage location often find themselves with broken downloads or expired links at the moment they need the material most.

Reading the Deletion Summary Before You Commit

Every major platform now displays a pre-deletion inventory. Google’s deletion summary organizes pending losses by service—YouTube videos, Gmail messages, Calendar appointments—allowing final review before irreversible action. Facebook’s Account Center presents similar confirmation screens. These summaries are not exhaustive. They list what the service acknowledges holding, not what the user has already purged or what resides in backup systems.

The critical final step is verification against the export. Users should open their downloaded archive, confirm that expected categories appear, and check that media files are intact and readable. HTML exports from Facebook should display properly in a browser.zip and.tgz files from Google should decompress without corruption. Only after confirming archive integrity should the deletion proceed. The ICO’s guidance on separate erasure requests applies here: even after a verified export, the user must complete a distinct deletion workflow to trigger actual data removal. The service will not infer intent from the download request.

Platforms are not designed to make this sequence obvious. Export tools are buried in settings menus; deletion shortcuts appear prominently in account frustration flows. The user who follows the platform’s preferred path—straight to deletion—loses access without securing a copy. The user who exports without reviewing archive contents may preserve an incomplete record. The correct procedure is deliberate, multi-step, and platform-specific: request the portable copy, verify its contents, select the appropriate termination mode, then confirm through the deletion summary. Your data leaves only if you make it leave twice—first into your hands, then out of theirs.