You uploaded a sensitive PDF to an online tool a year ago. Today you want it gone. Clicking delete in the UI feels final — but most cloud services keep backups, replicas and audit logs that survive the delete.
What 'delete' usually means
In most cloud services, clicking delete marks the file as deleted in the user-facing system. The file may then:
- Sit in a trash/recycle bin for a recovery window (30-90 days). - Persist in backup snapshots for the backup retention period (weeks to years). - Remain in audit logs and access histories indefinitely. - Be flagged for eventual cryptographic erasure but not immediately overwritten.
Soft delete is the default; hard delete needs to be requested explicitly.
How to actually delete
1. Delete in the UI — clears from your view. 2. Empty the trash/recycle bin — clears from the recovery window. 3. Request permanent deletion via support — explicitly asks for backup purging and retention waiver. 4. Confirm in writing — get a deletion attestation from the vendor.
For GDPR/CCPA right-of-erasure requests, vendors have legal obligations. For non-personal data, they may not.
The right-to-deletion request
Under GDPR Article 17 and CCPA, data subjects can request deletion of personal data. Vendors must respond within 30 days (GDPR) or 45 days (CCPA).
Make the request in writing. Reference the legal basis. Specify the file or data. Ask for confirmation of deletion including backup purge.
For your own (non-personal-data) files, vendors are usually willing but not legally obligated. Polite requests work in most cases.
How to avoid the problem
Use tools that don't store your files in the first place. Flint processes in your browser; there's nothing on Flint's servers to delete. The deletion problem doesn't arise.
For tools that must store files, prefer those that auto-delete after a short retention period (1 hour, 24 hours). Less data accumulates; less to chase down later.
FAQ
Will backup snapshots really keep my file?
Yes — most enterprise services retain backups for 30 days to several years. Standard practice; not malicious. Right-to-erasure requests can force purging.
Does Flint store any of my files?
No file content. Flint processes in your browser; your PDF doesn't reach Flint's servers. There's nothing to delete.
What's cryptographic erasure?
Encrypting data with a key that's then destroyed. Functionally deletes the data without overwriting it. Used in some cloud systems for efficient deletion.
Can I force deletion without legal basis?
Without GDPR/CCPA leverage, vendors aren't obligated. Most reputable vendors will accommodate reasonable requests; less reputable ones won't.
The cleanest deletion is no upload in the first place. Use Flint for in-browser processing and never have to delete.