What is the SaaS retention gap?
The SaaS retention gap is the difference between how long a software-as-a-service provider keeps deleted or changed data recoverable and how long an organization actually needs it. Data lost and noticed within the provider's window can be recovered with built-in tools. Data needed after that window has closed is gone unless a separate backup exists.
Where does the gap come from?
SaaS applications include recovery features intended for everyday mistakes. Each has a time limit set by the provider.
| Built-in feature | What it covers | Where it stops |
|---|---|---|
| Recycle bin or deleted items | Recently deleted files and messages | Purged after a fixed period, or earlier by a user or administrator |
| Version history | Earlier versions of a file | Limited number or age of versions, and deleted with the file |
| Account grace period | Data of a removed user | Deleted after a short period once the license is gone |
| Retention policies and holds | Content preserved for compliance | Built for discovery, not for restoring a working site or mailbox |
Which situations expose the gap?
Four are common. A deletion discovered late, months after the recycle bin was emptied. Deliberate removal by a departing employee or by an attacker using a stolen account, who clears the recycle bin too. Corruption that spreads quietly, such as a sync client overwriting good files, so that version history fills with bad copies. And data belonging to former staff, removed with their accounts and requested long afterwards.
How is the gap different from a provider outage?
The gap concerns data that the service has deleted as designed, on schedule and without any failure. Provider redundancy does not help, because every replica faithfully reflects the deletion. This is why high availability and backup address different risks. Under the shared responsibility model, the provider answers for the service and the customer answers for the data.
How is the gap closed?
By keeping an independent copy with a retention period the organization chooses. A SaaS backup stores items outside the tenant, keeps them for as long as policy requires and can restore a single item or a whole mailbox or site to a point in time. Storing that copy on immutable storage protects it from the same compromised administrator account that could empty the recycle bin. SaaS backup retention sets out the comparison in detail.
Frequently asked questions
How long do SaaS providers keep deleted data?
It varies by provider and service, typically from a couple of weeks to about three months by default.
Do retention policies in the SaaS application close the gap?
They preserve content for compliance, which helps. They are not designed to restore mailboxes or sites to a working state, and they are managed by the same administrator accounts.
How can an organization tell whether it has a gap?
By asking whether something deleted six months ago could be restored today. If the answer relies on the recycle bin, the gap exists.