Hacker News new | ask | show | jobs
by koopajah 4223 days ago
What I don't understand is why not have this be "opt-in". Meaning if your company does not need this feature for real legal reasons they don't enable it and everyone is happy. I've heard a few people saying they did not want this feature in Hipchat and would have to switch to make sure there team was not suspicious. If my company never needs to access private chats for legal reasons, there is no reason it should be enabled today and they can have access to it in 3 years.

I understand specific companies have specific needs and Slack has to meet some of these but there is no reason that this should impact everyone else.

1 comments

Did you read the article? It explains a very thorough opt-in process which involves mailing a signed letter on company letterhead and manual reviewal.
Sorry if I wasn't clear enough. What I mean is that if in 3 years my company needs to have access to some logs, they will have to go through the multi-steps process but then have access to whatever they need (starting from today's logs)

What I meant was that the possibility to access private chats should stay not retroactive and only happen once the company has explicitly stated it will need this feature enabled.

EDIT: so that if my company has no legal needs today it won't have access to private chats made today once they decide in the future that they now need the feature

That is how it works. "It’s worth repeating – Compliance Exports are not retroactive and do not apply to past private conversations before the feature is enabled."
I did not understand the sentence that way even after reading multiple times but that seems to make sense now. I must have been too biased when reading it before. Thank you for pointing this out.