<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="margin: 0px 0px 0px 6px; line-height: normal; font-family: 'Helvetica Neue';" class=""><span style="font-family: Helvetica;" class="">Call for Workshop Papers: "Will Drones Deliver My Privacy Policy? Workshop</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">on the Future of Privacy Indicators" at the Symposium On Usable Privacy and</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Security -</span><br class="" style="font-family: Helvetica;"><a href="https://www.usenix.org/conference/soups2016/workshop-drones-deliver-privacy-policy" class="" style="font-family: Helvetica;">https://www.usenix.org/conference/soups2016/workshop-drones-deliver-privacy-policy</a><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Call for Papers ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">It is known that users do not read privacy policies. Research suggests that</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">the existing model of notice and consent is based on false assumptions. The</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">methods for providing privacy notice to users that do not work on desktop</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">computers have been even more challenging when implemented on mobile</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">devices. Where do we go from here? This question might be simple to answer</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">if technology stopped evolving, but in many ways the future has already</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">arrived, with smart appliances, Internet of Things (IoT), assistive robots,</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">and, even drones. All of these artifacts may collect or sense personal</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">data. Therefore, all of these various devices ought to provide a way for</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">users to learn about their privacy policies and set personal preferences,</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">as well as give users the means to understand what privacy-sensitive</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">information theses different devices collect.</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Goals ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">This half-day workshop will provide an opportunity for those currently</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">engaged in researching privacy policies, notices, indicators, and other</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">related topics to think creatively about the next evolution of notice and</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">consent.  How do we provide privacy policies, notices, tools, and</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">indicators with non-traditional computing interfaces and devices such as</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">IoT, drones, assistive robots, self-driving cars, and others? Must we</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">radically rethink the way in which we ask for consent? Is it even possible</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">for users to truly consent to uses of their data that they may not even</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">understand?</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Submissions (not by drone, please) ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Submissions can include ongoing or proposed research, position papers, and</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">creative assets (e.g., illustrations, animations, portfolios) as long as</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">they can be posted or linked to the workshop Web site. Successful</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">submissions will strike a balance between creativity and original thinking</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">while attempting to address the real-world concerns and goals of providing</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">end users with meaningful choice and consent.</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Written submissions should use the SOUPS 2-column formatting template</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">(available for MS Word or LaTeX). Short Papers should be 2 to 6 pages in</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">length, excluding references and appendices. The submission should be</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">self-contained without requiring readers to read the appendices. Please</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">check with the committee before submitting material in a non-written</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">format. Submissions should not be blinded.</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Email submissions to: </span><a href="mailto:soups16futurenoticesworkshop@gmail.com" class="" style="font-family: Helvetica;">soups16futurenoticesworkshop@gmail.com</a><span style="font-family: Helvetica;" class="">.</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Selection and Presentation ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Workshop papers will be selected by the workshop organizers and made</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">available on the USENIX website. Accepted workshop submissions will not be</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">considered peer-reviewed publications from the perspective of SOUPS and</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">would not preclude subsequent publication at another venue. Authors of</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">accepted submissions should be prepared to present their work at the</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">workshop.</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Important Dates ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Workshop paper submission deadline: Monday, May 16, 2016</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Notification of workshop paper acceptance: Friday, May 27, 2016</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Camera ready workshop papers due: Sunday, June 5, 2016</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Workshop date: Wednesday, June 22, 2016</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Organizers ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Patrick Gage Kelley, University of New Mexico</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Jennifer King, School of Information, University of California, Berkeley</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Sameer Patil, New York University</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Florian Schaub, School of Computer Science, Carnegie Mellon University</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Richmond Wong, School of Information, University of California, Berkeley</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">== Program Committee ==</span><br class="" style="font-family: Helvetica;"><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Ryan Calo, University of Washington School of Law</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Nick Doty, School of Information, University of California, Berkeley</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Chris Hoofnagle, School of Information and School of Law, University of</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">California, Berkeley</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Deirdre Mulligan, School of Information, University of California,</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">Berkeley</span><br class="" style="font-family: Helvetica;"><span style="font-family: Helvetica;" class="">* Luke Stark, Media, Culture, and Communication, New York University</span><div class="" style="font-family: Helvetica;"><br class=""></div><div class="" style="font-family: Helvetica;"><br class=""></div><div class="" style="font-family: Helvetica;"><br class=""></div><div class="" style="font-family: Helvetica;"><br class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">Florian Schaub</div><div class="">School of Computer Science</div><div class="">Carnegie Mellon University</div><div class=""><a href="http://cs.cmu.edu/~fschaub" class="">http://cs.cmu.edu/~fschaub</a></div></div></div></div></div></div></div></div><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>