Disabled accounts: losing every file at once, sometimes by automated flagging
Ongoing policy
Dropbox can disable an account for policy violations — and when it does, all access to the account and its files is terminated at once. Users widely report being locked out with little explanation, and that some disablings are triggered by automated abuse-detection.
What happened
Dropbox's own help page is blunt about the consequence of disabling an account: "When an account is disabled, all access to the account and content on Dropbox is terminated." Accounts can be disabled for violations such as malware, phishing or spam, child sexual exploitation material, extreme violence or terrorism, abusive behaviour, or storing or sharing illegal content. Dropbox offers an appeal path — "If you think we made a mistake in disabling your account, you can ask us to review your account by filling out this form" — but the form is the only recourse, and reinstatement is not guaranteed.
The deeper grievance, documented across Dropbox's own community forum, is that some accounts appear to be disabled by automated abuse-detection systems rather than human review, leaving legitimate users abruptly cut off from years of files with a terse, generic explanation. Because Dropbox holds and decrypts files server-side, a disabling decision instantly removes the user's only copy if they relied on the cloud as primary storage. Users widely report long, opaque waits on the review form and difficulty getting a specific reason for the action.
This is presented here as a documented policy and recurring pattern rather than a single incident; the representative year reflects the period in which the current help-center language and forum complaints are concentrated.
Impact
The all-or-nothing nature of disabling means a single enforcement decision — correct or mistaken, human or automated — can sever a user from their entire archive with no self-service way back in. For people and small businesses that treated Dropbox as their system of record, a wrongful disabling is effectively total data loss until (and unless) an appeal succeeds, and it reinforces the case for keeping an independent local backup of anything stored in the cloud.