I just posted a long reply to your original message, without first seeing that you'd replied to this comment (made by someone else). If this is how the 30 day

I just posted a long reply to your original message, without first seeing that you'd replied to this comment (made by someone else). If this is how the 30 day policy works, it is slightly more appealing than what I thought. However, it's still not enough peace-of-mind for me. This means that recent files are vulnerable to corruption during their first month of existence (through accidental overwriting, and some kinds of viruses and ransomware). The "most recent version" that is backed up may end up being a corrupted, useless version. I agree that retaining infinite versions of every file would be cost-prohibitive. However, you may be able to find a healthy compromise. Maybe you could retain a ton of versions of small files and fewer versions of large files. Maybe you could provide users with a space allowance for versioning and allow them to decide which versions of which files to delete (if they reach the allowance limit) or to pay more to increase the allowance. To summarize: You need versioning in order to be an awesome backup service (and an awesome backup service is the only thing I'll happily settle for!)