Exactly. The default behavior is exactly as it should be-- scrub the VM itself but keep a snapshot for 48 hours in case it was deleted accidentally. There is n

Exactly. The default behavior is exactly as it should be-- scrub the VM itself but keep a snapshot for 48 hours in case it was deleted accidentally. There is no security concern here but if some users are still upset with this default behavior then they should be manually scrubbing their sensitive data prior to deleting the droplet or, better yet, they should be using their own hardware. Frankly, I'm shocked at a lot of the responses here. When I first came across this article it was immediately obvious to me that this was not an actual security concern but rather a mixture of misunderstanding and skepticism. So I came here to hackernews feeling entirely confident that this article would have been efficiently debunked and instead I find all manner of ill-informed arguments. The people that don't understand the original article, its fallacies, and the reality of how Digital Ocean is handling droplet destroys, should not be running servers IMO. This stuff should be obvious to you and furthermore, if your data is particularly sensitive, you should have already been under the assumption that the host could not be trusted and that data scrubbing must be done manually.