{"id":77,"date":"2017-03-17T23:33:05","date_gmt":"2017-03-17T23:33:05","guid":{"rendered":"http:\/\/blogs.harvard.edu\/bkassembly\/?p=77"},"modified":"2017-03-17T23:36:27","modified_gmt":"2017-03-17T23:36:27","slug":"a-mid-way-update-so-what-have-we-really-been-up-to","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/2017\/03\/17\/a-mid-way-update-so-what-have-we-really-been-up-to\/","title":{"rendered":"A mid-way update: So what have we really been up to?!"},"content":{"rendered":"<p>Now that we\u2019re nearly\u00a06 weeks into the Assembly development sprint, we Assemblers thought it\u2019d be a good time to start revealing bits and pieces of our projects to our broader blog audience. Even if terms like \u201cdifferential privacy,\u201d \u201cinternet of things,\u201d and \u201cinformation fiduciary\u201d cause you to shrug or cringe, please keep reading. We promise we\u2019re about to give you a thrilling inside look into our projects using explanations already tested on and approved by our own mothers and fathers. And for those looking to get into the technical weeds, hang tight until we release code on GitHub in April.<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-size: 24pt\"><strong>Project #1: Clean Insights<\/strong><\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-82\" src=\"http:\/\/blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full-300x200.jpg\" alt=\"istock_000042545368_full\" width=\"551\" height=\"367\" srcset=\"https:\/\/archive.blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full-300x200.jpg 300w, https:\/\/archive.blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full-768x512.jpg 768w, https:\/\/archive.blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full-1024x683.jpg 1024w, https:\/\/archive.blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full-676x451.jpg 676w, https:\/\/archive.blogs.harvard.edu\/bkassembly\/files\/2017\/03\/iStock_000042545368_Full.jpg 1920w\" sizes=\"auto, (max-width: 551px) 100vw, 551px\" \/><\/p>\n<p>There\u2019s no doubt about it: when you navigate to a webpage or open an app on your phone, it\u2019s a magical, seamless experience. Remember those times you logged into Facebook and saw ads perfectly tailored to those gadgets you\u2019d just considered buying on Amazon? Or that time you opened your Uber app on a Saturday morning and it gave you a miraculous\u00a0suggestion to travel to your favorite coffee shop? Perhaps unbeknownst to you, you at some time provided enough packets of data to these corporations to make such scenarios possible. Data fuel insights, which in turn fuel a beautiful customer experience.<\/p>\n<p>But like most fuel, data generate harmful byproducts (think the car emissions of the 21st century), and irresponsible data collection threatens basic privacy rights, and in extreme cases, physical human lives. To highlight some recent news stories, 500 million people just lost control of their personal data in a major <a href=\"https:\/\/help.yahoo.com\/kb\/SLN27925.html\">Yahoo breach<\/a>, while another 11 million people learned that their <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2017\/02\/vizio-pay-22-million-ftc-state-new-jersey-settle-charges-it\">Vizio smart TVs<\/a> were spying on them. It might be difficult to put a clear price tag on privacy these days, but it\u2019s certainly not free, and the worst is yet to come.<\/p>\n<p>With these problems in mind, a group of Assemblers has set out to build the Tesla of data analytics, a \u201cclean\u201d statistical tool that enables companies to gather insights on users &#8212; like where they live, what they like, what device they use &#8212; without compromising their privacy. We\u2019re calling it <strong>Clean Insights<\/strong>, and we\u2019re psyched to start giving companies ways to reduce their data carbon footprint.<\/p>\n<p>This all sounds simple, right? We\u2019re going to build a tool to track users without actually tracking them. Yeah, it\u2019s not that simple. In fact, it\u2019s incredibly difficult from a technical standpoint, but we\u2019re lucky to have Professor Cynthia Dwork, the pioneer of a mathematical concept called differential privacy, on our board of advisors (joined by many other wonderful advisors). In a nutshell, differential privacy is like a game of \u201ctwo truths and a lie\u201d &#8212; you put three pieces of data through a magical machine (read: a mathematical formula), and two come out unchanged while one comes out completely jumbled. The key: you don\u2019t know which ones changed and which ones stayed the same, so you no longer trust any of them. With enough data at scale, you can lean on concepts like differential privacy to uncover statistically significant patterns about your users without having to collect and retain individual data points. Problem solved!<\/p>\n<p>As you can see, we have our work cut out for us. Thanks to Assembly, however, we\u2019ve got the combined brainpower of a seasoned privacy app developer at the Guardian Project, a software engineer at Apple, a former product manager at Square, and many, many others, so we\u2019re pretty psyched and hitting the ground running. Stay tuned to see what we put out at the end of our development period in April!<\/p>\n<p><em>In the meantime, if you\u2019re feeling all jazzed up about joining our efforts to clean up toxic data spills, we\u2019d love to hear from you: <a href=\"mailto:Info@cleaninsights.io\">Info@cleaninsights.io<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Now that we\u2019re nearly\u00a06 weeks into the Assembly development sprint, we Assemblers thought it\u2019d be a good time to start revealing bits and pieces of our projects to our broader blog audience. Even if terms like \u201cdifferential privacy,\u201d \u201cinternet of things,\u201d and \u201cinformation fiduciary\u201d cause you to shrug or cringe, please keep reading. We promise [&hellip;]<\/p>\n","protected":false},"author":8727,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-77","post","type-post","status-publish","format-standard","hentry","category-uncategorized","post-preview"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/posts\/77","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/users\/8727"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/comments?post=77"}],"version-history":[{"count":8,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/posts\/77\/revisions"}],"predecessor-version":[{"id":89,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/posts\/77\/revisions\/89"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/media?parent=77"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/categories?post=77"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/bkassembly\/wp-json\/wp\/v2\/tags?post=77"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}