What really happens to files deleted from the cloud

Deleting a photo from your cell phone seems like a simple and instantaneous gesture: tap, confirm, and the file disappears from the screen. But, for most cloud storage services, this gesture starts a process that can take days (or even months) before the data actually ceases to exist on the company's servers.

Between the moment a user deletes a file and the moment it is permanently deleted, there is an entire layer of temporary retention, cross-device synchronization and backups that few people know about in detail.

The recycle bin: the first destination for everything you delete
Most large cloud services don't delete a file the instant the user asks to delete it. Instead, the item is moved to a temporary trash, an intermediate space created precisely to prevent accidental deletions.

In Google Photos, deleted files are stored in a recycle bin for up to 60 days before being permanently removed, according to the service's own documentation. During this period, the content continues to be stored on the company's servers and may even remain accessible in shared albums or synchronized with other applications linked to the same account, such as Gmail or YouTube.

On Google Drive, the logic is similar, but the period is shorter: deleted files remain in the trash for up to 30 days and can be restored at any time within that window. After the deadline, or if the user empties the trash manually, the deletion becomes permanent.

In the Apple ecosystem, the equivalent folder is called "Recently Deleted" within the Photos app. According to the company's official documentation, the items remain there for up to 30 days before being permanently removed from all devices connected to the same Apple account.

As iCloud mirrors content between iPhone, iPad and Mac, a deletion made on a single device, with sync enabled, automatically propagates to all others.

Why deleting in an app doesn't delete everywhere
One of the points that generate the most confusion is the relationship between different services from the same company. Until 2019, Google Drive and Google Photos shared some storage and file structure. Since then, direct integration between the two has been discontinued: a photo deleted from Google Photos is not automatically removed from Google Drive, and vice versa, unless the user originally saved the same file manually in both places.

This mismatch between services is one of the main reasons why "deleted" files reappear months later: the deletion was real in one application, but the same content continued to exist, independently, in another storage space linked to the same account - an external memory card, an email attachment or a backup made by a third-party application.

What happens on servers after recycle bin
When the recycle bin expires, or when the user empties this space manually, the technical removal process enters a second phase, generally invisible to the end user.

Large cloud providers do not store a single file on a single server: for reasons of redundancy and failure protection, data is often replicated across multiple data centers, often located in different countries.

This means that the "definitive" deletion of a file from the user's point of view is not instantaneous from the infrastructure's point of view: the system needs to propagate the remove command to all replicated copies, a process that can take additional days before each replica is effectively overwritten or erased from the physical hardware.

The role of automatic backups in data retention
Even after a file disappears from the recycle bin and main servers, it may continue to exist for longer in a specific place: the cloud company's own security backups. These backups are additional copies, created automatically to protect the system against failures, ransomware attacks or mass data loss, and usually follow their own retention cycle, regardless of the period of the recycle bin visible to the user.

Specialists in compliance with the LGPD (General Data Protection Law) point to this discrepancy as one of the biggest technical challenges of Brazilian legislation. Retroactively deleting specific data within an already created backup is technically unfeasible in most cases, as backups are consolidated blocks of information, not isolated and individually editable files.

The most common practice adopted by the industry, and considered acceptable by data protection authorities in Europe who have faced the same challenge under the GDPR, is to keep a record of the deletion request and automatically apply it as soon as that specific backup is naturally overwritten, within the retention cycle defined by company policy, typically between 30 and 90 days.

What the LGPD guarantees to those who request deletion
The General Data Protection Law, in force in Brazil since 2020, gives the data subject the right to request the deletion of their personal information at any time. Companies that store this data (whether cloud providers, social networks or any digital service) are obliged to comply with this request, removing the content not only from the main access systems, but also, within reasonable deadlines, from the backup copies linked to that information.

This requirement created a new standard of technical requirements for the sector: technology companies today need to document exactly where each category of data is stored, who has access to it and what retention period applies to each copy - including redundant copies kept exclusively for security and service continuity purposes, and not for active use by the user.

Why "deleted" files sometimes still appear
Cases of photos or videos reappearing months or years after an apparently complete deletion often have relatively simple technical explanations, even when they seem alarming to those who experience them.

The most common causes include incomplete synchronization between devices at the time of the original deletion, parallel copies saved on external memory cards or local folders on the computer, and duplication of files between different services linked to the same account, as occurs, for example, when the same image is simultaneously saved in Google Photos and shared by a messaging application that maintains its own copy in the cloud.

The general technical recommendation in these cases is to independently verify each service linked to the account and not to assume that deletion in one application automatically eliminates all existing copies in the others.

The difference between deleting and making unrecoverable
For those who need absolute guarantee that a sensitive file will not be recovered by anyone (not even technically, within the company's servers), data security experts recommend an additional step: manually emptying the service's trash, instead of simply waiting for the automatic deadline to expire. This gesture accelerates the start of the data overwriting process in the provider's infrastructure, although, as detailed previously, it still depends on the life cycle of the company's internal backups for the complete removal of all redundant copies.

The central finding, according to the cloud providers' own technical documentation and the LGPD compliance guidelines, is that "erasing" and "making irrecoverable" are distinct processes: the first is immediate from the point of view of the interface that the user sees; the second depends on a chain of technical steps that, in practice, usually takes between 30 and 90 days to be completed effectively.

Is it possible to recover deleted conversations or files on WhatsApp?

Source: CNN