3 ms·

Technical users or not, the implications need to be MORE CLEARLY spelled out. Putting it on the user to figure out the implications of some obscured click-thro

Technical users or not, the implications need to be MORE CLEARLY spelled out. Putting it on the user to figure out the implications of some obscured click-through garbage text isn't fair. There is a big difference between, say, a 3rd party application using a google API to work with anonymized keyword data from a gmail accounts VERSUS an actual person being able to browse someone else's gmail inbox. If Google makes it possible for some 3rd party asshole to peruse the gmail inboxes of whoever uses the service, that should be UPFRONT and VERY CLEARLY STATED.

Alex3917 8y ago
> If Google makes it possible for some 3rd party asshole to peruse the gmail inboxes of whoever uses the service, that should be UPFRONT and VERY CLEARLY STATED. Within the last year Google changed their OAuth policies so that you need approval from Google before you can publish an app that uses OAuth. One of the requirements for this is linking to your privacy policy, where you need to say how the data is going to be used.