4 ms·
I'm not a GDPR expert, so please confirm with your lawyers, but my reading of https://gdpr-info.eu/art-17-gdpr/ https://gdpr-info.eu/art-17-gdpr/ is that you on
by viraptor 9y ago
I'm not a GDPR expert, so please confirm with your lawyers, but my reading of https://gdpr-info.eu/art-17-gdpr/ https://gdpr-info.eu/art-17-gdpr/ is that you only need to remove the personal data, not old messages which still serve a purpose (they're a part of communication channel). Specifically, none of the grounds from point 1 apply:
a) data is still necessary (part of message chain)
b) consent wasn't necessary, the message was required for the messaging component of the service
c) again, necessary processing is excluded
d) it wasn't unlawful
e) I'm assuming you're not in one of the member states and this doesn't apply
f) it's not related to child consent
If anyone disagrees here, I'd be really interested to know why.
(Sethammons is right though that the headers / metadata would be likely covered)
- jdietrich 9y agoArt.5(1)(e) says "Personal data shall be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed". The messages themselves constitute personal data, as defined in art.4(1). Data doesn't need to be tagged with someone's name, address and social security number to be personal data - if you could even hypothetically identify someone based on that data, then it's personal data. Even if the users of this service never divulge any personal information about themselves in the content of their messages under any circumstances, they could still be identified by stylometry. There's a reasonable argument that retention of old messages is a necessary feature of the product, but I'd be strongly inclined to delete everything from the servers as soon as it's delivered. Old messages stored on the user's devices aren't your problem as long as your involvement in the processing of those messages was lawful. I'd also be strongly inclined to implement end-to-end encryption unless there's an overwhelming reason not to, because it adds a valuable layer of protection for both you and your users. https://gdpr-info.eu/art-5-gdpr/ https://gdpr-info.eu/art-5-gdpr/ https://gdpr-info.eu/art-4-gdpr/ https://gdpr-info.eu/art-4-gdpr/
- everdev 9y agoI would follow other prominent players in the space. When I delete my tweets, are those retweets and replies also deleted? When I delete my FB or Whatsapp account, are my messages deleted from recipients accounts? As a lean startup, I wouldn't pay my own lawyer to figure out what hundreds of well paid lawyers have already decided. You could write tech support for these companies and ask exactly how their GDPR compliance works. I'm sure they'll be happy if not legally obligated to tell you.
- jdietrich 9y ago>I would follow other prominent players in the space. Facebook can afford to play fast-and-loose with the rules. They have an army of lawyers waiting to contest any ruling from a supervisory authority. They have an army of developers ready to redesign their product if they're ordered to do so. They have an army of DBAs and CSRs to manage deletion requests and subject access requests. If you're running a startup that collects and processes lots of personal data and your resources are rather more limited than Facebook, it's sensible to interpret the GDPR cautiously. The more data you collect and store, the greater your potential liabilities. We're habituated to hoarding personal data, because the cost of storage is effectively nil and it might be useful at some point in the future. GDPR makes Schneier's argument that "data is a toxic asset" into a business reality. https://www.schneier.com/blog/archives/2016/03/data_is_a_toxic.html https://www.schneier.com/blog/archives/2016/03/data_is_a_tox...
- ldjb 9y agoWhen you delete your tweets, then yes, assuming people retweeted using the Retweet button, those retweets are also deleted. Replies are not deleted because those belong to the senders, not you. As for Facebook, it is true that deleting your account does not delete your messages. That's something they have been criticised for. However, I believe deleting your messages does result in recipients being unable to access them (except from cache, of course).
- weinzierl 9y agoAlso not a GDPR expert, but I disagree about the applicability of Art. 17 GDPR. What I have learnt about GDPR so far is that as long as you can argue the data is necessary and you get consent you are probably good to go. For the kind of service you are providing the messages are still necessary. I wouldn't rely on the fact that messages are or are not personally identifiable information. This is in my opinion just too risky and unnecessary. Again I'm not a lawyer and not a GDPR expert but you should talk to both. It's likely that your company needs a data security officer anyway and they should be the GDPR expert for you to consult in these matters.