>Why oh why have you guys built and application that I can’t leave easily?
I feel your pain, but isn't it obvious though? Increase the pain of leaving and you increase the likelihood of staying. Annoying, but effective.
I feel your pain, but isn't it obvious though? Increase the pain of leaving and you increase the likelihood of staying. Annoying, but effective.
The delete button sets an account flag saying "this user is deleted." The front end UI honored that and no longer showed the user. A half dozen DELETE tasks were then tossed into a job queue, one for each major subsystem (cache, archival storage, etc). The visual effect of deletion was instant and within 20 minutes everything was gone.
That's an excuse, not a reason.
Time is a zero sum game. If I can make features/fixes that brings me money, why would I spend time/money/effort to design system for effectively... well, NOT make money, at the cost of the former?
You then need to choose how you explain that to users (preferably before they sign up and start entering sensitive data) as well as the normal problems of deciding the policy about having backups of "deleted" data (if you don't actually delete it - either from the live data set or from archived backups - a court could require you to hand it over).
But as a paid service - where you've been a paying customer for many months - and a service that is targeted towards corporate customers this should just be a given.
The run around about user data belonging to users and so on is just ridiculous. Yammer helped us to create a corporate network, where the data belongs to the company - so when we want to leave it should be as easy as signing up - hit delete and you're done.
It doesn't matter if their systems retain the data for a few weeks and batch delete it later.
I'm sure that if a larger customer expressed this, they would bend over backwards to accomodate. Just feels like they're screwing the little guy.
Until I read this and decide not to sign up in the first place.