Retrofitting GDPR Compliance onto Legacy Databases [pdf]
vldb.org
vldb.org
The places that really go to lengths implementing GDPR-deletion or use tools like this GDPRizer, are probably not the most nefarious to have your data, it's the ones who don't care and will sell it, abuse it and hide from it.
So you call company X and ask to be forgotten. Company X is one of the good ones, so they set their engineers on it (automatic or manual etc.), can you really be sure all traces are deleted? If not yea X can be fined, but does that really (truly) benefit you if the data was still present and leaked? What about company Y that you haven't even heard about that got the data from somewhere else, you wont call them.
What about the complications about GDPR and trading/using products from overseas, seems like everyone is breaking the law, because there are so many laws.
You are correct obviously, the hope is that Y will no longer get the data from "somewhere" as every X will no longer share it, but this is a naive though of course.
> What about the complications about GDPR and trading/using products from overseas, seems like everyone is breaking the law, because there are so many laws.
This is somewhat intentional. The EU is speculating that, because they are such a huge markets, manufacturers will either produce a EU version of their products or produce one version that complies with GDPR as it is cheaper than maintaining two different versions.
And to be completely honest, my personal opinion on this matter is that they probably don't mind too much. If companies now need to use European suppliers/Service Providers and you can fine them for using external ones? Sounds like an easy way to boost your economy.