Thread by @evanwolf

Will #eprivacy be the next expansion of #gdpr? MSFT #Skype, #Whatsapp, Facebook #Messenger would have to provide #privacy controls/consents/disclosures for tracking/logging realtime communication and messaging.
technologyreview.com/the-download/6…

This matters in a few ways. First, live chat and messaging are features of many kinds of products and services. So #ePrivacy jurisdiction may touch nearly every website, service, and gadget.

Second, #ePrivacy demands transparency for the middle part of a call, exactly where companies like @Amazon, @Google, @Skype and @SlackHQ create new value and new partner ecosystems. Translation, bots, commerce to enhance your conversation will need specific disclosures.

#ePrivacy continues the push for personal control of personal data, expanding the scope to include protections we expect of landline and mobile phone calls. But in our smart devices and cars that "call home" to their makers with usage data. nytimes.com/2018/05/27/tec…

reports that tech industry groups that profit from advertising are scared. They are lobbying to gut, stall, or kill #ePrivacy while it is being reviewed by the EU governing bodies. eur-lex.europa.eu/legal-content/…

For me, I like this new raft of protections. Where GDPR focuses on data at rest or being processed, #ePrivacy deals with data in motion. And where GDPR focused more on data living on servers, ePrivacy adds your phones, home devices, cars, and other "terminal equipment."

I'm still reading the #ePrivacy Proposal. You should start too if you're an #IoT technologist or maker, care about #AutonomousVehicle design, make mobile apps, or have talk as a feature in your product. A gram of architectural foresight may be worth a kilo of cure.

unroll