This user experience is well known and understood in the desktop world. Leave it to internet adtech companies to disrespect user's expecations for privacy and personal data protection.
Google could be more honest and label the permission "this app will make your email public for all intents and purposes".
How is offering the worst case hypothetical of what the 3rd party might do with your data _more honest_ than refraining from hypothesizing?
Would it be that hard to raise the user's awareness right then and there? Bonus points for offering a sandboxing mode, where the app can only access certain network locations, like Google IMAP servers, and only Google IMAP servers. Extra bonus points for auditing traffic from sandoxed apps to catch them if they try something fishy.
The basic problem is that unlike with SMS, where what gets displayed is what you sent, with email what gets displayed to the user is probably best described as being vaguely 'inspired' by what the sender wrote. Email clients need to make tons of decisions on things like typography, threading, displaying metadata, handling attachments, sanitizing user input, unicode and emojis, phishing, etc.
Even within major email clients like Gmail, threads and messages regularly don't parse correctly. When a user reports that something is broken, or when an exception gets raised by the app because something doesn't parse properly, then it's not unreasonable for a developer to use that as fixture data to try to fix the issue, as long as this is explained in the privacy policy. In fact if you care about making / using good products, this is exactly what should happen.
E.g. in our privacy policy it says, "If you let us know that an email thread isn't being parsed correctly, we may retrieve and store that specific thread for testing and debugging purposes."
Leaving that out of the privacy policy would be legally and ethically problematic. You should also tell people at the point where data gets used (unless it’s obvious), but everything your site does needs to be in the privacy policy.
This works fine for HIPAA, FERPA, etc., and it works fine for email. No need for anything new, beyond more OAuth scopes.
Edit: I created tickets for more Gmail API scopes. If this is something you care about, star the tickets or whatever:
Privacy policies are not effective. Users don't have time to read all the privacy policies or to shop for apps that provide real privacy, if one exists. Users don't have the expertise to understand the systems, the policies, or the implications of surrendering their information.
The evidence seems strong that it is beyond most users. Usually in those situations there is regulation, as there is now in the EU. For example, banks can't charge variable interest rates that escalate to 50% and say 'it was in the agreement'. Airlines can't sell you a ticket to Oslo and then fly you to Rome, and say 'change of flight plan was in the agreement'.
> Technology can only limit access and use cases so much
If it was in Google's interests, I bet they could find a way.
Users can reasonably conclude that, because of the very poor state of user privacy knowledge, but they are still incorrect. It's rare the third party that can add something useful to a web application which doesn't also necessitate the same privileges that would allow data exfoliation, and which isn't usually added by the first party developer fairly quickly.
Education is needed here.
I wouldn't assume that. Software is written by humans so ultimately if data is out of Google's hands, then there is no control over who gets to read it.
Does that really qualify as an "it turns out"? Every technical person who saw this would understand that this was an obvious capability. No one was surprised. Be serious: were you surprised?
Note also that the article points out that this kind of storage is likely a violation of the developer's contract with Google, which contains the standard privacy requirements.
Make that part of API 29 or such to not break apps.
Very sneaky use can be partly detected too, but then we're talking specifically malicious apps.
The new permission would mean the app is allowed to send contacts or emails read from database over the network.
The article is saying that _humans_ employed with the 3rd party app development company are also able to see your email.
Users might reasonably conclude that When they grant consent, the app – the 3rd party computer software – would be able to read their email, but no human would be able to read their email. Well it turns out, once the app has consent, the app, if its designers make it so, could read your email and then save your email elsewhere. And then humans could read the contents of that email elsewhere.