Concerning backups: If you have a short turnaround time (e.g. 14 days) it shouldn’t be a problem, the legislation acknowledges the fact that deleting data and ensuring data integrity (also in accordance with GDPR) are sometimes mutually exclusive from a practical point of view. You need to make sure that deletion requests also get honored when restoring from backup though, so ideally you want to store the requests in a third system and check them when you restore backups.
Concerning the democratic aspect of participating in the online world I think GDPR actually helps, as before it was not possible to reliably get your own data deleted, rectified or transferred, which is not very democratic either IMHO.
This is where the GDPR has really helped me. I posted a comment on a blog critical of a government data sharing initiative. Nothing illegal, or questionable - it was a simple two sentence opinion comment which I posted under my real name. I didn't stop to think for a minute that it would cause me any problems.
It did. I discovered that I couldn't get to work on any government projects because when a background check was carried out on me, the above comment was found and according to Revenue (the gov agency responsible for such checks) it indicated that I was hostile to the governments IT plans.
I asked the blog owner (same country as me) to please remove the comment, they refused. So I submitted a right to be forgotten request to Google to stop the blog post appearing in searches for my name.
I'm not sure if the contract for Revenue is exactly the same as the civil service, but I would presume on this front it is very similar.
There have been three occasions where the IT contracting firm I was working for sent me to work on government IT projects as a contractor. None of them were for Revenue, but it is Revenue who do these checks for all other departments. On one occasion my employer managed to pull a few strings to get me on the project (DSP), on the other two I was told no government work for me (HSE and DoT).
On one of the three three occasions I was forwarded an email from Revenue that said "he expresses a desire for personal privacy that indicates he would be unwilling to fully embrace the governments data sharing strategy".
I did write to a few news outlets about this, none were interested. Even the ICCL wasn't interested, which really surprised me.
Well, that's kind of Orwellian.
You might as well tell them that compilers can provide the functions necessary to comply.
If you are using software to process my personal data, and you don't know how to do that while protecting my personal data, then I'd like you to stop using that software right away.
You record that these people need to be scrubbed if you restore backups, and you delete old backups.
The ICO has excellent guidance on this and other subjects:
https://ico.org.uk/for-organisations/guide-to-data-protectio...
> This will have a silencing effect for people wanting to operate non-profit sites as they won't be able to afford to comply with such requests
I can't understand what your question is.
There's absolutely no reason someone can delete spam from their public forum, but can't delete people's phone numbers from items that are pointed out to them.
If they have no search capabilities, and don't use a search capability, they're not required to create one.
The GDPR is extremely easy to comply with- European companies have been doing it for a long time (before it gained the force it has now) because it's largely a unification of existing data protection laws.
It’s really just a slight mental shift. Instead of seeing data as an asset see it as a liability. Once you do that everything comes naturally.
If it's only due to technical skills then this problem can be solved technically.
The forum software needs to enable people to be GDPR compliant.
> On a semi-related note: if you are a small SASS operator wanting to comply with such requests, what are you meant to do about your DB backups that contain data that is meant to be forgotten?
This hasn't been tested in court, yet. But there are several possible approaches. Like delete on restoration or backing up in slices, so that the personal data becomes anonymous unless you have all the parts.
Don't forget that the "right to be forgotten" is not an absolute right. It doesn't trump everything else. Nobody would expect somebody to sue ESA for their "right to be forgotten" for a public message that they could send to ESA to put on a CD on a probe they sent into space and win.
First of all, it forces everybody involved with personal data to think about how they handle personal data and inform the users about that.
If you state "due to technical limitations, your personal data in backups can't be erased at the time of the request but will be deleted on restoration" up front during the signup of the user, this is already an improvement over the past where nobody knew what happened with their data.
You are probably not trading with North Korea, so ignoring their laws has zero impact on anything. China is already getting more tricky though, although they are not choosing to throw their entire weight behind enforcing their demands abroad(yet).
But ignoring the demands of the largest trading block on the planet? That's not going to go well if you do any sort of business with the EU. Unless you can just afford to ignore all EU customers entirely.
And no, thank fuck for the GDPR, it's a great legislation.
https://inshorts.com/m/en/news/european-union-is-worlds-larg...
2) I don't think you understand how GDPR works at all. GDPR says how data about EU citizens has to be processed in a certain way. If you want to do business with EU, you have to comply. If you don't want to comply, you don't get to trade with EU. No one is claiming jurisdiction over other countries - it's simply a matter of agreements. Just like EU respects certain American laws just because it wants to trade with USA and it was requested. It's a mutual thing.
I understand it just fine, perhaps you don't understand what I'm saying. No, if an EU citizen comes to my US website, that does not grant the EU authority over me no matter what they claim. I live under US law, not EU law, not Chinese law, not North Korean law. Those countries are free to pass laws claiming they have jurisdiction over me when I do business with their citizens, but claiming it doesn't make it true. No I do not have to comply, the EU has zero authority over me no matter who I do business with _unless_ I'm in the EU where they can do something about it. They can attempt to stop their citizens from using my website, but it is not upon me to do so.
There is no agreement between the US and the EU to respect the GDPR, it's an untested assertion of global authority that cannot stand. The world cannot function if every country can assert every citizen in the world must comply with its laws because their citizens came to my US website. That's a violation of national sovereignty and it will fail when the EU tries to assert that authority and the US courts say, sorry, but no, you don't have jurisdiction over our citizens which is what's going to happen.
The EU can and will enforce the GDPR within its borders, that's expected; outside its borders, it has no jurisdiction and no teeth; I don't have to give a damn about EU law while operating my US business in the US. That a visitor comes from someone outside the US does not change that my business is in the US. I do not have to obey other countries laws.
You have it backwards. It's not an EU citizen coming to your US website - it's your US website choosing, willingly, to serve EU citizens. You can also choose to not serve them - that's fine. And yes, EU cannot fine you in any way, there's no legal possibility to do that. However, if your operation was detrimental to EU citizens in any way, EU could ask US to cooperate in asking you to stop. Obviously US has the jurisdiction to do something about it, there's no question about that.
To maybe give a different example - if you were selling something that is legal in US but not legal in EU, advertising it, selling it and shipping it to EU customers could still get you in trouble, because at a certain point EU will ask US authorities to stop you from sending illegal products to their territory. You are not breaking US law, but countries do cooperate in this manner. Same would happen in the other direction - if someone was sending drugs that are completely legal in EU over to US, they wouldn't be braking EU law - but US definitely and absolutely would ask local authorities to find you and politely ask you to stop. Does that mean US suddenly has jurisdiction in the EU? No - but EU would most likely comply with such a request as a matter of international cooperation.
And yes, the same request sent from North Korea or from China would likely be ignored - that boils down to what I said earlier about negotiating power and international respect. EU countries are very likely to comply with requests like these coming from US, and EU can and does request things from US. It has nothing to do with the issue of jurisdiction that you are so very keen on.
>> I don't have to give a damn about EU law while operating my US business in the US.
Again, if your US business does serve EU customers, then you kind of have to give a damn. Just like an EU business has to give a damn about US laws when doing business with US customers. It's really not a difficult concept to grasp.
> It's not an EU citizen coming to your US website - it's your US website choosing, willingly, to serve EU citizens.
Wrong, they're coming to my site; I have no way to know they're EU citizens or not, there's a thousand reasons I wouldn't know, it's not like IP is a reliable means. People use vpn's, or EU citizens travel. The burden is not and cannot logically be on me to know where my customers come from. It's impossible to know the citizenship of your customers.
Perfect example, according to the GDPR, an EU citizen travelling in the US who uses my site from the US is still protected by the GDPR; that's horseshit and a technical impossibility; I can't know they're an EU citizen. This law was written by technically illiterate morons.
Of course if your business doesn't collect our data, there is no issue either way.
Good luck with that champ
If I walk into a store, can they copy my drivers license and phone number without asking me, and then refuse to wipe my personal data from their systems?
I sincerely fail to see the downside with GDPR unless you think you have some assumed right to personal user information. Why does a site need info from me if I do not even have an account? Why do so many sites now insist that simply by visiting I agree to let them store cookies on my device?
> take upskirt shots of women walking over. That’s illegal at a federal level in the US
Only since 2004, and that's a specific exception that was made and only applies when there is a clear expectation of privacy, i.e. wearing clothes to cover your privates is a clear indication you expect that to be private. That doesn't stop anyone from taking pictures of you you don't like though and it only makes the area under your clothes a private space, it doesn't make the public space your in a private place.
- store as little data as needed - protect the data in state of the art ways - make transparent what you store and process and why - establish a process to delete data once it's not needed anymore
It is only complicated if you want to build a company around the abuse of data, as common in the ad world.
How about the duty to export user data on request?
How about player consent management? Consent updates, etc.
Those are not simple thing neither to implement nor to manage, especially if someone will accuse you and you need to prove that you are compliant.
Some things are too dangerous to the public to allow part-time hobbyists to do. We don't allow part-time hobby doctors, or lawyers, or banks, or toxic waste disposal services, and most of us think that's the correct tradeoff. GDPR puts processing people's personal data in the same category; given how much damage a careless processor of personal data can cause, that seems appropriate.
Like with almost every other Directive, the EU has made a huge mistake by not including de minimis exemptions in the regulation. In practice this isn't a problem in most countries because there isn't enforcement against tiny operators either, but the fear and confusion it creates is very real.
(On the other hand, without this kind of thing you get phone companies selling your real-time location to criminals. If only there were such a thing as a sense of proportion)
Proportionality in the GDPR is based on the scale and sensitivity of your data activities. The size of your organisation or your technical capability is irrelevant; if you're not competent to safeguard the data you handle in accordance with the law, the EU doesn't want you to handle it. It's exactly the same principle we'd apply to toxic waste - you're not allowed to dump it in the woods just because you're a small business or a hobbyist.
Some examples of why there is no de minimis exemption:
A small charity accidentally sent a newsletter using "to" rather than "bcc". In doing so, it accidentally revealed the identities of 56 people who are HIV positive. It was fined £250 by the Information Commissioner's Office, because of the small size of the organisation and because the ICO was satisfied with steps taken to prevent further breaches.
https://ico.org.uk/about-the-ico/news-and-events/news-and-bl...
A non-profit trade organisation with a single employee worked to facilitate information sharing between construction companies. That information consisted of files on trade unionists, political activists and advocates for health and safety, constituting an effective blacklist of "known troublemakers". The organisation's files were seized by the Information Commissioner's Office, leading to enforcement notices against 14 construction businesses; settlements under the Data Protection Act totalled over £50m.
The To/BCC one is both very important given the sensitivity of such data and a horrifyingly easy mistake for most organizations to make.
I'd put it as: the decentralised social web cannot be allowed to exist unless and until a way to do robust privacy enforcement on it can be found.
> and heading in the direction of "the public cannot be allowed general purpose computers"
Slippery slope fallacy. GDPR exists not out of some abstract desire to regulate but as a response to the massive privacy breaches that have directly affected the general public. If and when general purpose computers are shown to have a similar negative effect on society, we can have a conversation about whether regulating them is appropriate given the costs and benefits of doing so.
Rolling backups, e.g daily and weekly, are fairly common. When the request comes in, just acknowledge there will be a time period before the deletion is fully purged from system backups - as is still legal post-GDPR. The user data will still be removed from production data, which is of primary concern.
I understand that there's forums/websites run by people who have no idea what they're doing. And regulations like GDPR make sure that services they are using have baseline encryption and guarantees. Like, it should encrypt passwords and private data, don't store it if not necessary and have functionality to delete users.
It is not about people running the websites/forums, it is about software they are choosing to use. Baseline should not be "it works", but it should be "it works and provide reasonable level of security". I know it is some work on part of people who have no idea what they're doing, but ultimately it is up to developers to set up CMS and forum engines to comply.
Or just block EU traffic and ensure no seizable assets rest in the bloc.
But backups has to be stored securely, and the data within can't naturally be used if restored beyond exceptions.
For example, in the UK both of the above are law since 1998. And that only implements an EU Directive from 1995.
Sometimes I feel that the main effect of the publicity around the GDPR has been for many people to discover existing laws...
Perhaps some people will say "good, if you cannot run a site conforming to all laws of the land then you should shutdown". If you think that, consider this: as these laws pile up it will get more and more difficult to operate, leaving only the very tech/law savvy, and big business.
This is not the democratization of information that the web promised oh so many years ago.
On a semi-related note: if you are a small SASS operator wanting to comply with such requests, what are you meant to do about your DB backups that contain data that is meant to be forgotten?
[edits: punctuation/grammar]