This shields them from individual liability as well as makes the company liable for their actions (as long as they are acting as agents of the company in an official capacity).
The customer has no business relationship with the individual customer support person, so whether they are lying or telling the truth is irrelevant to the customer -- they do have a business relationship with the company (a single actor, with multiple agents) and the company can easily tell lies via these agents.
If the above narrative is correct, the company did very likely tell a lie since the fact that the customer's data was recoverable was probably known by the company and also the company likely actively worked to make the opposite of this known via their agents.
That's... ambiguous. Agents aren't liable for contractual violations, but agents are typically liable for torts. Liability depends on exactly what the employee did.
AFAIU, theoretically an employee committing a tort could be liable personally as well as the employer; and if service is disrupted the employer could be contractually liable.
Also keep in mind the perspective and context that the end user has no way of knowing.
And even if the data can be recovered in an unofficial manner whether they will actually bother is highly unlikely if they care as little as they most obviously do.
So, as a user it is a pretty safe bet to just assume it is gone (but do keep poking).
"Your data has been deleted" pretty much has always meant that it was deleted from the live servers and that the deletion will propagate through backups depending on the orgs retention policy/requirements.
The organization knows that they have the data, but they trained their staff to reply that it was destroyed.
That's a lie. Not an untrue statement, but a deliberate lie.
To whom? My mother? Nope- she thinks it's gone. So yeah- it's a lie, and you only catch it if you know better.
"Yes Dad I did my homework" has pretty much always meant that he hasn't started it yet.
No, it's a lie and the organization knows it. They are responsible for training their CS folks.
You people are throwing around the word "lie" very loosely here...
No, the exact opposite in fact.
Am saying that if you weren't told there's a backup, you'll not think there's one and treat the data as completely deleted, even if they really aren't.
(Although given privacy regulations, it's a bad sign if a support agent can't give a precise answer about data stored or at least know not to make unchecked claims about it)
No it doesn't. Deleted most places means deleted and gone forever. There are a number of legal requirements (in the U.S.) at least when dealing with certain government organizations, and many non ones as well surrounding this. Think of it this way, a customer comes and says, there is sensitive information on your server, and since we no longer want to do business with you, you are now required to delete it. Normally there is an end date to allow the backups to be purged through propagation etc., but at the end, when they say it's deleted, it means deleted from everywhere. Sometimes this also means completely wiping drives so there is absolutely no trace of it left.
"A lie is a statement used intentionally for the purpose of deception"
I don't think you can prove it was a lie.
Definitely worth considering in more depth, thanks for the perspective.
Well, that "person" lied. Regardless of the specific agency it employed in doing so.
(And, this type of banning and cut-off from data is obviously -- just look at the comments here -- not a one-off scenario. I find it difficult to believe that the consequences, including the customer's lost access to their data, were not thought about by MailChimp, as an organization and by people in their official roles within MailChimp.)
P.S. As I've grown older and observed and thought about things, I've come to see this as a primary role of the corporation or other such entity: To "dilute" responsibility and accountability to the extent that no member -- or, no member who has sufficient influence, who "matters" -- is ever held personally accountable for their actions within and on behalf of the corporation. [Addendum: And, in turn, the corporation is never truly held accountable, because the employees involved "lacked knowledge". Nicely circular, eh? By the way, I don't consider paying a dollar amount that is often a fraction of the gains realized by the behavior, to be "being held accountable".]
I've stopped letting people in such corporate or institutional roles off the hook, just because "they didn't know". Or rather, I've stopped letting the corporations and institutions off the hook because employee X didn't know. All too often, it's set up precisely that way and on purpose.
I bet you people just assume or their manager doesn't know either.
Why was my account suspended -
> If we suspended your account, we'll contact you as soon as possible to let you know why, and to give you details on how to fix the situation.
And that's clearly a lie, based on OP's experience, and those of other commenters.
Top executives maintain ignorance of operational unpleasantness. Technical staff know operational specifics, but little about business design and usage. Intermediate management know pieces of business design and usage, but nothing about technical implementation.
Nobody needs to lie, and still there's often no way to know for sure what happened.
After all, how can we know what an alleged liar is really thinking?
What matters is that the institution as a whole - the way their policies and procedures come together - lied.
The institution certainly knows of it's capabilities. It deliberately chose to not tell that to it's CS reps, because of a multitude of reasons, that come down to 'It makes our/their jobs easier.'
My ISP, for example, lies to me every time I make a call to customer service. Is the front-line CS rep lying to me? No. But his employer is, by making him tell me a pile of bullshit about why my Internet is busted - again.
"It doesn't matter if they're liars"
C'mon, man.
In other words, data recovery that can't be handled by the customer service reps and that requires developer intervention should be a "surprise and delight" sort of situation and not a "customer should expect this" type of situation.
The answer should be: "I can't know." Followed by one of: (1) Let me connect you to someone who can know (2) Let me tell you how much it costs to find out (or 3) Also we don't care.
That would be honest. Not saying it's easy.
Because, in that case, the intent of the statement is to deceive. If the intent of the statement is simply to not set an expectation that can't be guaranteed rather than to intentionally deceive, then it's not a lie, in my opinion.
I work in audio editing and recovery/enhancement and there are situations on a regular basis where we tell customers that their audio can't be recovered. I don't think we're lying to customers in saying that despite the fact that, in some cases, we may be able to recover or enhance the audio to the point where it's usable if we invested an exorbitant amount of time on it. In the most literal sense, yes we can recover the audio but in the practical sense and, most importantly, to the customer we can't recover the audio in any meaningful way because they either can't afford the work necessary, we don't have the resources to devote to that work, or we can't guarantee that, even if we can recover it, it's acceptable for whatever purpose they need it for despite being "good enough" for us.
If I tell somebody that something's unrevocerable because I know they wouldn't want to pay the recovery, I'm not lying. But saying nothing can be done when I'm just afraid of the cost of righting my mistake: that is lying.
> regardless of whether it's something that would require developer intervention to recover.
For most intents and purposes, data existing only on archived backups or raw server logs is "completely wiped".
Irrelevant, customer service can know if the data record exists without having access to it.
For most intents and purposes, data existing only on archived backups or raw server logs is "completely wiped".
My intent and purpose in asking the question may not be part of "most", yet it's still valid.
Not defending Mailchimp, but keep in mind the perspective and context. To a customer support agent using some backend interface, it very well could be "completely wiped". To an escalation team, they may be able to pull it from backups in an "unofficial" manner.