I have thought about that, and I might implement later.
GDPR applies to personal data only. So, whether posts are personal or not? If so, you also have to delete them on the user's request.tojag wrote: ↑Fri May 11, 2018 10:56 amThe extension displays the position "user's posts", that is, however, do you treat posts as private personal data? I guess everyone here convinced me that posts on the public forum can not be private. Uhmm ... I do not know what to think about it. Because if it is private data, then it will be necessary to export them on demand and delete them with the deletion of the account. Since there is no unambiguous solution to this problem, it would be good to have an option to disable links to user posts in the settings. This is just my suggestion.
I think you mean any personal data must be retrievable, not any data. If you are going down that route then, technically, you would have to store all header information of every packet that you transmit - and that is never going to happen.tlem wrote: ↑Mon May 14, 2018 9:28 pmAccording to the GDPR, any data transmitted to a platform by a user must be retrievable for possible retransmission to another platform.
It also seems to me that in a detailed text concerning the GDPR I read that this data should be able to be recovered in cvs format.
In what way - that is the first I have heard about that being a problem.
I take exception to that statement, I know us ‘older’ people are sub-millennial but we’re still breathing and quite capable of holding our own. I’m quite able to install whatever I want when I want, please do not generalise you’ll be old yourself one day.
Code: Select all
Registration IP: 220.127.116.11 IP addresses that you have used: 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124