Reversible storage: soft delete, versioning and retention
A recovery layer over your cloud storage keeps deleted and overwritten files restorable for as long as your retention rules say, and records every delete and restore.
The challenge
In shared storage, someone will eventually delete the wrong file. Users, scripts and integrations can all remove or overwrite legal, financial and customer records, and without a safety net the loss is permanent.
Recovery then becomes a slow, manual effort with no self-service path and no clear record of what happened. The result is lost work, compliance exposure and long arguments about who deleted what.
What it does
Soft delete
Deleted files are held in a recoverable state for a set period instead of being removed at once, so a mistake can be undone.
Versioning
Earlier versions of a file are kept when it is overwritten, so a bad edit or a faulty script can be rolled back to a known good copy.
Configurable retention
Retention windows are set per dataset or sensitivity tier, so important records are kept longer and routine data does not pile up.
Controlled restore
Only authorized roles can restore, and restores can run through the admin tools or by script, so recovery is not open to everyone.
Delete and restore history
Every delete and restore is logged with who did it and when, which gives reviewers the context they need after an incident.
Options for regulated content
Legal hold and write-once immutability can be used for regulated records where the storage platform supports them.
How it works
Set the retention rules
Decide how long deleted items and old versions are kept for each dataset or tier, based on business need and regulation.
Turn on protection
Soft delete and versioning are enabled over the storage container, so removal and overwrite stop being final.
Recover when needed
An authorized user restores a deleted file or an earlier version, either in the file manager or through scripted workflows.
Review and expire
Delete and restore events are reviewed through the log, and data leaves the recoverable window only when its retention period ends.
Under the hood
- Storage
- Cloud object storage
- Soft delete
- Blob versioning
- Retention
- Lifecycle rules
- Retention policies
- Legal hold and immutability where supported
- Access
- Role-based permissions
- Time-limited access links
- CLI and SDK scripts
- Monitoring
- Activity log
- CSV export
- Event streaming to monitoring tools
Inside the harness
Audit
Each delete, overwrite and restore is recorded with identity, time and context, so reviewers can reconstruct what happened to a file.
Policy
Retention windows and restore rights are set per dataset and role, then applied everywhere, instead of being left to each team.
Security
Restore is a separate privilege, so the people who can delete data are not automatically those who can bring it back or purge it.
Data transfer
Files arriving by upload, folder transfer or partner drop-off land in storage already covered by these protections.
Business outcome
Mistakes become recoverable. Destructive actions turn into reversible ones, so an accidental delete is an inconvenience handled in the file manager rather than a lost record.
Predictable retention. Retention follows written policy by data category, which makes it easier to show why something was kept or removed.
Cleaner audit trails. Every delete and restore is logged with context, so incident reviews rest on records instead of recollection.
Support for regulated records. Where the storage platform offers legal hold and immutability, they can be applied to the content that regulation requires to be preserved.
Where it is used
- Recovering a contract folder deleted by mistake in storage shared by several partners.
- Rolling a dataset back after a faulty script or integration overwrote it.
- Keeping financial records for a defined period before they can be purged.
- Preserving records under legal hold while a dispute or review is open.
Frequently asked questions
Does soft delete keep data forever?
No. Deleted items are recoverable only for the retention period you set. After that window, they are removed under your lifecycle rules, so you stay in control of how long data is held.
Can we make records immutable?
Where the underlying storage platform supports write-once immutability and legal hold, they can be applied to regulated content. Availability depends on the platform and your configuration, so confirm for your case.
Who is allowed to restore files?
Only roles with restore rights. Restore is its own permission, separate from upload and delete, and each restore is logged with who performed it.
Does it work with our own cloud storage?
Yes. The protection sits over storage in your own cloud account and region, so your data stays where you keep it.
See it on your own documents and data
Tell us what you want to automate and we will show you how it runs inside the harness.