Probably not, because it’s ” difficult “
You can pick an arbitrary time frame for retention, but whatever you pick, you have to communicate to users, and you can't just change it on a whim. Normal customers want this clock short. They don't want you to retain their stuff after they cancel.
Why could they not turn it into a read-only database without access from the Heroku apps instead? Then it'd just be a routine change to the service offered, would it not?
I highly doubt normal customers want this clock short when the cancellation is not customer initiated.
Thus didn't happen because of the contract, but because the people implementing this transition didn't give a crap.
Silos lead to issues like this. Cross-functional teams cost more, etc.
Onboarding users/partners would be easier without making them read/click all those consent checkboxes, etc.
Ideally, product people defend the end users. Realistically, compliance people defend the company from getting screwed in an audit and ultimately sued by the government.
I had a vague thought for a moment about maybe being able to give customers the option to opt in to an updated set of terms that would've been better designed for the situation ... but since the original Tell HN author didn't get any emails about this at all, presumably they wouldn't've got that one either so even if (and given 'vague thought' I'm not claiming any particular level of 'good idea' to it) that had been done it presumably wouldn't've helped them anyway.
It seems to me the root problem here isn't so much the compliance initiated policies as a complete failure to take 'make sure people have been adequately warned' sufficiently seriously given the potential consequences.
Deeply unfortunate.
(read that last sentence in understated deadpan dry en_UK to get an appropriate read on just how impressed I'm not by the communications cockup)
I genuinely had to read this twice to get the intended meaning.
i'd probably prefer feces-by-email to surprise database deletion
You could easily block all incoming connections to the database. For a free database of 10k rows there were no SLAs, and you would still technically be hosting the database.
Even taking a dump and emailing it to me feels like a safer option here.
There were better answers here for sure. If the honest answer is we just didn't feel the effort was worth it for this class of users at least own that.