{"id":1875,"date":"2013-05-21T10:04:50","date_gmt":"2013-05-21T14:04:50","guid":{"rendered":"http:\/\/www.kaspersky.co.in\/blog\/?p=1875"},"modified":"2020-02-26T20:26:27","modified_gmt":"2020-02-26T14:56:27","slug":"no-privacy-google","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/no-privacy-google\/1875\/","title":{"rendered":"No Privacy at Google I\/O"},"content":{"rendered":"<p><a href=\"https:\/\/www.kaspersky.co.in\/blog\/google-glasses-privacy\/\" target=\"_blank\" rel=\"noopener\">Google Glass<\/a> was among the main attractions at the Mountain View, California search giant\u2019s developer-centric I\/O conference in San Francisco last week. We had high hopes that Google would address the substantial and pervasive privacy implications of a head-mounted computer that sees everything its wearers see, but it remained the elephant in a convention center that hosted sessions on everything from \u201cAutoscaling Java\u201d (whatever that means) to indoor mapping. There was one mention of privacy on the Google I\/O Sessions page; it was a link to Google\u2019s privacy policy.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2013\/05\/05095711\/privacy_title.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1876\" alt=\"privacy\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2013\/05\/05095711\/privacy_title.jpg\" width=\"640\" height=\"420\"><\/a><\/p>\n<p>At the 2012 edition of Google I\/O, security and privacy got a whole hour in the \u201cSecurity and Privacy in Android Apps\u201d session, which seemed modest at the time, but looks fairly indulgent now that we\u2019re left digging through all the presentations to see if there was even a mention of privacy this year.<\/p>\n<p>Luckily, there were two telling mentions of privacy at the event: one <a href=\"https:\/\/developers.google.com\/events\/io\/sessions\/332695704\" target=\"_blank\" rel=\"noopener nofollow\">in a Google Glass fireside chat<\/a> and <a href=\"http:\/\/www.itworld.com\/legal\/356676\/larry-page-wants-see-your-medical-records\" target=\"_blank\" rel=\"noopener nofollow\">another anecdotal mention from Google\u2019s top brass<\/a>.<\/p>\n<p>Perhaps not surprisingly, the best privacy discussion was prompted by an audience member in a Google glass session. <a href=\"http:\/\/www.theverge.com\/2013\/5\/16\/4338418\/glass-privacy-fireside-chat-google-io-2013\" target=\"_blank\" rel=\"noopener nofollow\">According to our friends at the Verge<\/a>, when an audience member asked Google Glass\u2019s product director, Steve Lee, about the privacy implications of the wildly anticipated product, Lee downplayed concerns, claiming, not encouragingly, that it is easy to tell if someone is recording you with their Google Glasses and that the user-privacy was at the forefront of the product design team\u2019s thinking as they developed Google Glass.<\/p>\n<div class=\"pullquote\">It\u2019s possible that Google\u2019s new privacy strategy is to deflect, denigrate and downplay until no one cares about personal privacy anymore: a policy behooving to any organization attempting to build an empire upon data.<\/div>\n<p>In a truly shocking departure from the norm, the United States Congress seemed to mirror public sentiment when they <a href=\"http:\/\/joebarton.house.gov\/images\/GoogleGlassLtr_051613.pdf\" target=\"_blank\" rel=\"noopener nofollow\">penned a letter to Google CEO and co-founder, Mr. Larry Page<\/a>, expressing concerns about the new product\u2019s impact on user- and non-user-privacy, and demanding answers to some pretty tough questions. Page must provide answers to these questions by July 14, which will give us a far-clearer view into the real privacy implication of the yet-to-be-released computer-spectacles.<i><\/i><\/p>\n<p>It might be slightly unfair to say that Google scoffs at user-privacy just because they didn\u2019t host any privacy talks at a yearly conference that is really about teaching developers how to optimize Google\u2019s resources, tools, and gadgets in order to make better applications and other Web services. Also, in Google\u2019s defense, <a href=\"https:\/\/www.kaspersky.co.in\/blog\/eff-report\/\" target=\"_blank\" rel=\"noopener\">the tech company received very high marks in the Electronic Frontier Foundation\u2019s 2013 \u201cWho Has Your Back?\u201d report<\/a>. However, Page made it a whole heck of a lot easier to criticize Google on privacy, which is saying a lot, because privacy-hawks have been taking Google to task on its handling of user-data for years. The CEO and co-founder took the stage at I\/O, and seemed to suggest that because <a href=\"https:\/\/plus.google.com\/u\/0\/+LarryPage\/posts\" target=\"_blank\" rel=\"noopener nofollow\">he blogged about some nerve issue that paralyzed his left and later his right vocal cord<\/a> on his <a href=\"https:\/\/www.kaspersky.co.in\/blog\/10-ways-to-manage-privacy-in-google\/\" target=\"_blank\" rel=\"noopener\">Google Plus account<\/a>, that everyone needs to be less uptight about the privacy of their medical records.<\/p>\n<p>There is no way to know for certain if Page\u2019s views on medical privacy reflect his views on personal-data privacy, but it\u2019s no-less interesting to hear such a pivotal character in the privacy debate advocate for openness with regards to medical history. To his credit, he seemed to be trying to say something about the potential for technological and medical advances that would be achievable with such openness.<\/p>\n<p>Of course, it may have taken some courage for Page to come forward with this, but a billionaire publically talking about a non-life-threatening condition that affects the way he speaks is one thing, while allowing public access to the medical records detailing commonly stigmatized, communicable, or deadly conditions is another thing altogether.<\/p>\n<p>It absolutely rocked the world in 1991 when Magic Johnson publically announced his retirement after contracting HIV. In retrospect, Johnson\u2019s announcement was overwhelmingly good, but Magic Johnson was perhaps the greatest basketball player to have ever played the game to that point. The reaction to Johnson\u2019s announcement ranged from incredibly positive to equally negative, but the reality is that he never needed to work again. Not all of us have that kind of job security. Crippling post-traumatic stress or anxiety disorders or any number of other ailments aren\u2019t necessarily things you want a potential employer or school admissions officer to know about before you even get a chance at an interview.<\/p>\n<p>It\u2019s entirely possible that Google has the best of intentions for Google Glass (and Android for that matter) or that Larry Page means well when he says he wants us to be more open about or medical history, but it\u2019s also possible that Google\u2019s new privacy strategy is to deflect, denigrate and downplay until no one cares about personal privacy anymore: a policy behooving to any organization attempting to build an empire upon data.<\/p>\n<p>Tell us what you think this all says about <a href=\"http:\/\/support.kaspersky.com\/7819\" target=\"_blank\" rel=\"noopener\">privacy<\/a> in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google Glass was among the main attractions at the Mountain View, California search giant\u2019s developer-centric I\/O conference in San Francisco last week. We had high hopes that Google would address<\/p>\n","protected":false},"author":42,"featured_media":1877,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[22,43],"class_list":{"0":"post-1875","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-google","9":"tag-privacy"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/no-privacy-google\/1875\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/no-privacy-google\/1875\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/no-privacy-google\/1875\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/no-privacy-google\/1875\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/no-privacy-google\/1875\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/no-privacy-google\/861\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/no-privacy-google\/1875\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/no-privacy-google\/1875\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/1875","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=1875"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/1875\/revisions"}],"predecessor-version":[{"id":18791,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/1875\/revisions\/18791"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/1877"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=1875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=1875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=1875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}