3 ms·
> Doesn’t mean I expect random engineers at Microsoft to be able to read my email. The basic problem is that unlike with SMS, where what gets displayed is what
by Alex3917 8y ago
> Doesn’t mean I expect random engineers at Microsoft to be able to read my email.
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."
- wpietri 8y agoA privacy policy that nobody ever reads is a poor place to put that. If you want informed consent, when they report an email thread parsing error specifically ask if including contents is ok.
- Alex3917 8y ago> A privacy policy that nobody ever reads is a poor place to put that. 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.
- AstralStorm 8y agoGDPR turns that should into must and has no "obvious" clause.
- Alex3917 8y agohttp://www.privacy-regulation.eu/en/recital-32-GDPR.htm http://www.privacy-regulation.eu/en/recital-32-GDPR.htm https://privacylawblog.fieldfisher.com/2016/the-ambiguity-of-unambiguous-consent-under-the-gdpr https://privacylawblog.fieldfisher.com/2016/the-ambiguity-of...
- wpietri 8y agoSure. I'm not saying it should be left out. Just that nobody should expect that users have read the privacy policy.
- deleted 8y ago[deleted]