You deleted that photo three months ago. The embarrassing one, the one with the document visible in the background, the one you definitely didn’t want on a server somewhere.
Is it actually gone?
In Google Photos, the answer is more complicated than a simple yes or no — and understanding the gap between “I deleted it” and “it no longer exists” is important for anyone who cares about what Google holds on their behalf.
Stage One: The Trash
When you delete a photo in Google Photos, it doesn’t disappear. It moves to the Trash (also called Bin in some regions).
The Trash holds deleted photos for 60 days. During that time, the photos still exist on Google’s servers, still count toward your storage quota, and are still accessible — including to anyone who can access your account.
This 60-day window exists as a convenience feature. Accidental deletions are common, and a recovery period is genuinely useful. But it means that “deleting” a photo is not the same as removing it from Google’s infrastructure.
If you want photos out of the Trash before the 60-day period, you have to empty the Trash manually:
- Open Google Photos
- Tap the Library tab
- Tap Trash
- Tap the three-dot menu and select Empty Trash (or select individual photos and delete them permanently)
Only after a photo is removed from the Trash — either manually or after 60 days — does the permanent deletion process begin.
Stage Two: Server-Side Deletion
Once a photo leaves the Trash, Google begins the process of removing it from their systems. Google’s documentation describes this as a multi-step process that can take time to complete across all of their infrastructure.
Google operates multiple layers of redundant storage. Files that appear “deleted” from the user-facing system remain in backup layers for a period while those backups cycle out. Google’s own data retention documentation acknowledges that deleted content may persist in backup systems for an unspecified period after deletion from primary storage.
The practical implication: there is a gap — potentially weeks or months — between when a photo is removed from your Trash and when it is fully purged from all Google systems. During that gap, the photo exists somewhere in Google’s infrastructure even though it’s no longer accessible through the Google Photos interface.
This is not unique to Google. It’s how cloud infrastructure works at scale. But it’s something users rarely consider when they think a photo is “deleted.”
What Google’s Privacy Policy Actually Says
Google’s privacy policy describes the deletion process as follows: when you delete data, Google follows a deletion policy to ensure it is removed from active storage and, eventually, from backup systems. The timeline is not a precise number of days.
For most users, in most circumstances, this is not a cause for concern. Google isn’t doing anything nefarious with photos sitting in backup cycles — they’re in automated systems designed to eventually purge them.
But for users who are deleting photos because of specific concerns — they contain sensitive information, they were taken in error, they depict something that shouldn’t persist anywhere — the “may take time” nature of server-side deletion is meaningful.
Shared Albums: A Different Problem
Photos in shared albums have a more complicated deletion path.
When you share a photo in a Google Photos album, the photo exists as part of that album, accessible to everyone who has the link or was invited. If you delete the photo from your library, it may still be visible in the shared album — depending on how the sharing was configured.
More specifically:
Photos you added to a shared album: Deleting them from your library may remove them from the shared album as well, but this depends on whether the album owner (if not you) has a copy or whether others have saved copies to their own libraries.
Photos others added to a shared album you’re part of: You cannot delete these from the album — only the person who added them (or the album owner) can remove them.
Saved copies: If someone who had access to a shared album saved a copy of a photo to their own library, that copy exists independently in their account. Deleting the original from your library has no effect on their copy.
The practical lesson: once a photo has been shared in Google Photos, the deletion path is no longer entirely within your control.
Google Shared Drives and Google Drive
Many users store photos in both Google Photos and Google Drive. These are related but distinct systems.
A photo that exists in both Google Photos and Google Drive needs to be deleted from both. Deleting from Google Photos doesn’t remove it from Drive, and vice versa.
If you’ve shared a photo via a Google Drive link — rather than a Google Photos link — the sharing controls and deletion behavior follow Drive’s rules, not Photos’ rules. Drive-shared files can be deleted from your Drive, but shared access doesn’t automatically terminate; collaborators may have already made copies.
Check both Google Photos and Google Drive if you’re trying to remove a photo from all Google systems.
Deleting Your Entire Google Photos Library
If you want to delete all photos from Google Photos, the process is more involved than selecting everything and hitting delete.
The most reliable method:
-
Download your data first. Use Google Takeout (takeout.google.com) to export all your photos before deleting anything. This ensures you have a local copy.
-
Empty your library. In Google Photos, go to the library, select all photos, and move them to Trash. You can do this in batches. On the desktop web app, you can select multiple photos efficiently using Shift-click.
-
Empty the Trash. Go to Trash and empty it manually. Don’t wait for the 60-day automatic deletion.
-
Check Google Drive. If photos were synced to or stored in Drive, repeat the process there.
-
Wait. Even after completing these steps, backend deletion takes time. If you’re concerned about the gap, Google’s privacy policy provides a contact for data-related questions.
When Photos Live in Multiple Places: The Backup Problem
Many users have Google Photos synced from their phone, which means photos back up automatically whenever the device is connected to the internet. This creates an important scenario:
You delete a photo from Google Photos. But if the photo is still on your phone, the next backup sync may re-upload it.
Before deleting photos from Google Photos, delete them from your device first (or turn off backup sync temporarily). Otherwise, the photo you’re trying to remove from Google’s servers will reappear after the next sync.
The sequence for true deletion:
- Delete from the device
- Delete from Google Photos
- Empty the Trash in Google Photos
- Confirm the photo isn’t still stored in Google Drive
What Happens to Deleted Photos Under GDPR and CCPA
For users in the European Union, GDPR gives you the right to request erasure of personal data (“the right to be forgotten”). For California residents, CCPA provides a similar right to request deletion of personal information.
Google has a formal process for these requests, separate from simply using the delete function in Google Photos. A formal erasure request under GDPR or CCPA requires Google to delete your data from active systems and, within a reasonable time, from backups as well.
If you need to ensure deletion for legal or compliance reasons — not just personal preference — submitting a formal data erasure request through Google’s privacy tools creates a documented record and triggers Google’s compliance obligations.
The informal deletion path (delete from the app, empty Trash) doesn’t create this record.
The Bigger Picture: What “Deleted” Means in Cloud Storage
The Google Photos deletion behavior is a specific instance of a general principle: deleting data from cloud storage is not the same as deleting a file from a hard drive.
On a local drive, deleting a file marks its space as available and overwrites it when new data needs that space. The process is simple and relatively complete.
In cloud storage, data sits across multiple redundant systems, backup layers, and content delivery networks. “Deletion” is a change in the record that says the file exists, not the physical obliteration of every copy. The copies cycle out over time.
This is true of Google, but also of Dropbox, OneDrive, iCloud, and virtually every cloud storage service. The cleanup happens — but on the infrastructure’s schedule, not yours.
Understanding daftei’s Deletion Policy
daftei handles account deletion differently from most cloud services. When you delete your daftei account, a 30-day grace period begins. During that window, you can reverse the deletion if it was accidental.
After 30 days, deletion is permanent and irreversible. daftei’s commitment is that this means actual erasure — files are not retained in backup systems indefinitely after that point.
For individual file deletion within an active account, files are removed from your library and are not retained for AI training, advertising, or any purpose that would require keeping copies beyond the operational need.
The 30-day grace window is documented and known in advance — unlike the vague “may take additional time” language in most cloud storage deletion policies.
A Practical Checklist for Permanent Photo Deletion
If you want a photo actually gone from Google’s systems:
- Delete it from your device first
- Verify backup sync won’t re-upload it
- Delete it from Google Photos
- Delete it from any shared albums (or remove it from sharing)
- Check Google Drive and delete it there if present
- Empty the Trash in Google Photos manually
- For sensitive photos: consider submitting a formal GDPR/CCPA erasure request
The 60-day Trash period and the backend deletion timeline mean that complete removal takes time even when you do everything right. Plan accordingly for anything time-sensitive.
The Lesson
“Deleted” in Google Photos means “moved to Trash.” “Emptied Trash” means “started the deletion process.” “Deletion process complete” is something that happens on Google’s timeline, not yours.
For casual use, this rarely matters. Photos of your lunch and screenshots of memes don’t require rigorous deletion protocols.
For photos that genuinely shouldn’t exist on someone else’s server — images of documents, personal moments you regret sharing, anything sensitive — understanding what “deleted” actually means is the first step to managing it properly.
The gap between intent and outcome in cloud deletion is real. Knowing about it is what lets you close it.