{"id":923,"date":"2009-02-13T18:19:00","date_gmt":"2009-02-14T02:19:00","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=923"},"modified":"2009-02-13T18:19:32","modified_gmt":"2009-02-14T02:19:32","slug":"current-event-privacy-is-a-joke","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/13\/current-event-privacy-is-a-joke\/","title":{"rendered":"Current Event : Privacy is a joke"},"content":{"rendered":"<p>How many of you have received letters from your banks about a &#8216;revised&#8217; privacy policy? Have you even bothered to read through this revised policy information? And the .000001% percent of you that have, have you ever found anything objectionable and done anything about it?<\/p>\n<p>Welcome to the new joke called &#8216;Privacy&#8217;. No, I&#8217;m not talking about the most intimate information that you already have on facebook (which by the way, facebook now owns and has the rights to share). I&#8217;m talking about the numerous merchants\/banks\/credit companies that you do business with but never really cared about what they do\/could do with your information. When you read phrases like &#8216;shared with affiliates&#8217; and &#8216;shared with third parties&#8217;, have you wondered what the difference between these two are? And besides, have you wondered why on earth, banks would need to share your information with other people in the first place?<\/p>\n<p><span style=\"text-decoration: line-through;\">Most of us<\/span> Almost all of us never think twice about how our information is freely passed around(for money of course) in the open market for &#8216;agencies&#8217; to analyze.  Such information is then sold by VISA to other marketing companies for &#8216;market analysis&#8217; and ad campaign management. I have a friend who works for VISA and he was able to pull up every purchase I&#8217;ve ever made on the credit card and all he needed was my credit card number which is easily available (how many of you shred your old credit cards?).<\/p>\n<p>And guess what!!?? you have no control over who they share it with because well, first of all, you never really read their privacy document. Even if you read it when you got the credit card, you never really read it the numerous times that they sent you the revised privacy policy. Now again, to the .00001% that read the document every time, you have no control over how VISA decides who their affiliates\/partners and third parties are.<\/p>\n<p>Concerned yet? Privacy in the current state is nothing but a big joke.<\/p>\n<p>The only viable solution seems to be a universal privacy declaration\/document issued by the government that the companies can be held responsible to. As much as we all hate a big brother state, trusting a bunch of greedy banks\/credit companies\/vendors is much worse.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How many of you have received letters from your banks about a &#8216;revised&#8217; privacy policy? Have you even bothered to read through this revised policy information? And the .000001% percent of you that have, have you ever found anything objectionable &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/13\/current-event-privacy-is-a-joke\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":96,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,9],"tags":[183,210,211],"class_list":["post-923","post","type-post","status-publish","format-standard","hentry","category-current-events","category-privacy","tag-credit-cards","tag-policy","tag-privacy"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/96"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=923"}],"version-history":[{"count":5,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/923\/revisions"}],"predecessor-version":[{"id":932,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/923\/revisions\/932"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}