Facebook's Privacy Policy, Terms, and Principles are actually written in very clear, plain language. I've read them. They're easy to understand. I was frustrat

Facebook's Privacy Policy, Terms, and Principles are actually written in very clear, plain language. I've read them. They're easy to understand. I was frustrated by Senator Graham's remarks because he absolutely could understand them, if he bothered to read them. (He said that he didn't understand them.) The problem though, isn't the Terms. It doesn't matter how plainly written they are. People won't read them. What matters is designing your product with correct privacy affordances. Put yourself on the shoes of the user, and make sure your app isn't sharing information in a way that would be jarring or unexpected. For example, Facebook made a mistake with its posting dialogue experience pre 2016. You could say that a post should only be shared "with friends" in a choice box next to your post. However, that post would also be shared with any apps your friend has installed. That's probably not what the posting user would have expected, so it's a poor experience. If you have inadequate privacy affordances, you shouldn't just hide behind your terms. That's the point. Edit: I don't understand why I'm being downvoted. If you disagree with something, please let me know. I'm designing our own privacy affordances in our app following the above thinking, after all...