Omniscient Wrote:You have full control by not joining. I stopped using my Facebook accounts a very long time ago. I am careful about sites I join and if I am worried about abuse of the information I give them then I don't join.
That's exactly what the GDPR addresses. As you understand, a lot of your (active) userbase involves kids. A lot are adults, but an alarming number will be < 18 I imagine, a majority < 21. This is a young age. The GDPR classes < 18s as vulnerable individuals, and they are. They have no clue what they're consenting to, or the importance of their data. I'm not sure I can say I did, and you perhaps can't say so either (ofc I can't comment on your behalf).
The people charging back on you may well be 13-17 years old. They don't know what they're doing, they perhaps don't see it as scamming, and in general they sure don't know what can happen to people on this site that "piss off" certain types. A policy of putting addresses in signatures puts them at risk. That, in my opinion, would be the most concerning policy of yours. They'll have other digital footprints anyway, any motivated individual can find them if they want, but my point is that these kids aren't always competent enough to engage on this site.
Even as adults, it's hard to know what you're getting into. A key aim of the GDPR is to make privacy polices more verbose, so individuals signing up better know what they're getting into, and can not sign up if some of this info concerns them.
Even then, they can mess up and I don't think it's fair to have that looming over their heads forever. The previous data protection acts already had (rather absolute) rights to erasure if processing caused "significant duress". Generally speaking, I don't think a data controller should be processing information they have no reason to process other than for the sake of it.
You, yourself, realise now you don't want your data on Facebook (and you're in a rather unique position to care more about your privacy, I'd guess), others may take longer to realise that, perhaps not until after they've consented to processing. Also, sometimes we can't control who we have to give our data to. We may strictly speaking have the right to not use a service, but we're effectively blackmailed into using such service. An example is centralised application services for universities. We may not want them to process our data, but if an individual wants to get into X university they're effectively forced into it. Same goes for CRAs etc...
Omniscient Wrote:I assume you don't own a business or at least one that has to comply with GDPR.
I reside in Europe, and do run a business that needs to comply with the GDPR, processing more personal information than Hack Forums (based off what you've said). I also freelance for businesses processing sensitive information. My opinions of the GDPR are more following my personal opinions on individual rights to privacy.
The GDPR is stretched out of context. The rights offered are not absolute rights, and delving deeper into the legislation shows that. Before the GDPR, I've adhered to providing the same protections to users I would expect myself (and I expect a fair bit), so the main changes for me personally were mainly privacy policy changes to be more transparent. Complying with the GDPR is not a burden. If you look at headlines like "right to erasure" it may sound like it, but delving deeper you realise the GDPR is not there to make your life harder, it's there to make it harder for businesses that couldn't care less about personal (and perhaps sensitive) information about their users. That's wrong, with or without GDPR.
I have no problem with the additional burdens though. I went out of my way to do a fair bit of it regardless, and to me my customers having sufficient faith in my respect for their privacy is more important than some additional hours I 'waste' into ensuring those protections. I don't think any of them care tbh., but I would in their shoes so it's worth my time for me. I'm aware not all business owners feel this, though. None of my freelance clients share the same view and all of them viewed it as a burden. Some possess very sensitive information, so I find it very concerning that they don't view the GDPR as an opportunity. Perhaps I'm just the naive one here, though, since clearly nobody else views it in the ways I do.
Omniscient Wrote:There is a number of things written into GDPR which requires a lot of work on the part of businesses. Just trying to understand the full scope of this huge law and how it applies to your business is a vast undertaking. I am easily 50+ hours into my own research and implementation trying to be compliant. And I bet another 20-50 hours gets logged before this is done. I'm one small site, so imagine your a multinational corporation with thousands of employees. They not only have to comply but if they don't they do risk facing the $20 million fine for each violation.
It's an easy law to understand but a difficult one to implement, admittedly. It's clear in the rights it wants to give and its purpose, as if it were a manifesto, but it isn't concrete in how businesses should reasonably implement these rights. That's the same for most EU legislation tbh, future legislation looks worse.
It's actually easier for the multinational corps imo, they have access to large consultancy firms that have interpreted the hell out of this for years. For places like Google they just had to deploy new privacy policies. Their operations haven't changed much from what I can tell. They (presumably) just found better ways to process data and have used the entire 2 year transition window for this.
Even then, even the data protection authorities aren't fully sure on the GDPR. There are inconsistencies in enforcement across the EU. The UK DPA says one thing, the Finnish one says another, and it's the DPAs that do enforcement in the first instance. The EU made this regulation up and forced it down on the member states to enforce, so it's not really the most centralised piece of legislation. The issue is that a complaint can be filed in any EU member state, so I'm not sure how jurisdiction works here when they themselves aren't 100% here.
Omniscient Wrote:I am listening to feedback and doing my absolute best to quote the actual law when I do interpret. I don't want to quote articles about the law or posts from the web. I prefer to read the law myself and use the words in it to justify my own policy. That's the only way imho we can be compliant.
The current agreement will likely be changed and updated and definitely the Help Doc will get completely rewritten too. Oh, we'll also be adding that little cookie popup thing soon too. More annoying crap.
I probably have read more about this law then a US lawyer. Also, I don't intend to keep addresses. I may have to go into some archive folders and just delete all my very old backups. I still have site files from 10 years ago, which I'm willing to bet most webmasters do that. You run backups, drop into folder, and forget it. No one puts an expiration date on files to self-delete.
Agreed. You're the best person to understand your operations. It's hard to explain tech sites to traditional lawyers/firms (in my experience anyway). It's more just a case of checking your interpretations are valid and justifiable. At the end of the day, the people that would review violations think similar to the traditional firms providing consultancy. The EU is clearly out of the loop in tech, as evident by their copyright regulations they're cooking up. Some interpretations you find valid may not be is all, I ran my logic by someone as well and found some flaws, helps to have someone "experienced" check (although, they tend to hint that they're uncertain).
BTW, you may be able to keep those backups. The GDPR (and previous data protection acts) apply to sortable data. If you can run a search, or if data is categorised (either physically in a file and filing cabinet, or in a database) it falls under the GDPR. If it's stored in various backups over a long period I do not believe the GDPR reasonably requires you to delete or modify data from them all.
See: gdpr-info.eu/art-2-gdpr/
Quote:This Regulation applies to the processing of personal data wholly or partly by automated means and to the processing other than by automated means of personal data which form part of a filing system or are intended to form part of a filing system.
Of course this is ironic, because you can retain all the data you want in backups and if you really want some data you can fish it out of them. Recommendations here: acronis.com/en-us/blog/posts/backups-and-gdpr-right-be-forgotten-recommendations
Seems to me like they would expect you to categorise individual data separately in backups so it's easily, widely, erasable but for prior backups they won't expect you to sort through and delete data. IANAL so YMMV.