Again though, all that needs to be done is to make sure that the liability for leaked data falls on the user. That's the other part of it right? You delegated a

Again though, all that needs to be done is to make sure that the liability for leaked data falls on the user. That's the other part of it right? You delegated access to your account, so InstaFaceTwitter is no longer responsible for what happens to the data on that account. They are only responsible for making sure they give anyone presenting the keys you authorized access to edit and read data on your account. I mean, there are obviously responsibilities that naturally come with having delegated that access. And word will get around. The first GDPR violations because some user delegated access to their account and the entity that was authorized slurped up all of that user's contacts' personally identifiable data without the contacts being notified, will undoubtedly set the tone. That's still likely a GDPR violation. This doesn't change any of that. The only thing that changes is that the consequences for the GDPR violations now fall on the entity that was authorized, or maybe on the user who authorized the entity? (Not sure which?) But it obviously would not fall on Twitter since it is only complying with the law. It's important that legal and criminal liability is matched to authorization or delegation. In practice, it will be the threat of legal liability that ensures data security and data privacy, so that needs to follow delegation to ensure incentives are always aligned properly.