Comment by ryandrake | Hacker News Reader

Comment by ryandrake | Hacker News Reader

Parent Full thread

At the company I work for, a human being gaining access to “look” at a user’s actual prod data (anything that might contain PII) is super rare and very, very difficult. And I’m not even in Europe. At least a dozen people need to approve the access, including people very senior in leadership, you need to describe exactly what data you need to see, what the business purpose is, what steps you are taking to anonymize the data (can you live with a redacted view?), exactly how long you need that access, how you are going to destroy any copies after that access is finished, and so on. This employee access, IF approved, gets logged and can be scrutinized later. And I have absolutely no doubt if you misused that access it would be noticed and you’d be fired (it has happened). I’m pretty confident that nobody at my company is going on the internet and posting “OMFG LOL our users have such crazy data u should see it LOL.”

I always assumed most SeriousBusiness companies over a certain size, not run by 20 year olds, operate similarly.

If that's all true then it's almost certainly because you work at a large, mature, bureaucratic, unusually privacy-focused company. Verrrrry few companies work like this when they're small and new. I'd round down to ~0%. And I would bet that, if your company was ever a small startup, it didn't work like this back then, either.

Also, this idea that it's bad or weird to anonymously discuss customers is strange. I've known cops, doctors, dentists, and all sorts of other people who routinely share stories about weird things that happen with people and customers at work, anonymously. This is the norm in the world and always has been.

It's also the norm for the companies who own your data to look at it, when asked to. What do you think customer support even is?

It's only really a small corner of the tech world that treats these things as strange and sacrilege.

Yeah, that is the correct behavior what I would expect in a business setting - its a basic decency, not to mention customers switching to competition if they find out their data is not protected.

> anything that might contain PII

Sounds like your software might require HIPAA compliance in which case everything that you just said makes sense and is likely required in that context. But for the average SaaS that doesn't need HIPAA compliance it doesn't work like that.

What do you do when you're providing tech support to a customer about an issue that is related to their data? Obviously there should be some process in place but a customer going 'hey could you look at this' is a perfectly valid reason to, you know, look at it.

And it's not particularly unusual to discuss vague details of your customers anonymously. Even in the medical field, with very strict privacy rules, doctors will often publicly discuss encounters they have had with patients, and they only cross the line when they identify the patient.

That’s a good question, I honestly have no idea how customer support works. My guess is they have access to heavily audited systems that automate away these approvals, are limited to tools that can delete/reset but can’t read, and/or are given a filtered/redacted window to the user data they do actually need to see with human eyes.

Reply on news.ycombinator.com