{"id":130,"date":"2008-02-10T20:57:55","date_gmt":"2008-02-11T04:57:55","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/02\/10\/us-customs-seizes-electronics-at-borders\/"},"modified":"2008-02-10T20:57:55","modified_gmt":"2008-02-11T04:57:55","slug":"us-customs-seizes-electronics-at-borders","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/10\/us-customs-seizes-electronics-at-borders\/","title":{"rendered":"US Customs seizes Electronics at borders"},"content":{"rendered":"<p>The title says it all. According to the article linked below, Customs has been seizing electronics like cell phones and laptops on grounds of &#8220;suspected criminal activity.&#8221;\u00a0 Some travelers complained that their devices were taken for more than a week and copied by the agency during that time.\u00a0 This calls into question the jurisdiction of Customs, who said that it was similar to searching a briefcase and finding hard-copy evidence.\u00a0 While I understand the necessity of surprise, random searches like this, I think if notifying travelers would have been a better idea to mitigate travel stress.\u00a0 Many people subjected to this kind of search have complained already, and some have already gone to court in outrage. To help relieve concern and stress, I would suggest to Customs to submit a press release detailing the search procedure, as well as how the data is handled.<\/p>\n<p><a href=\"http:\/\/www.washingtonpost.com\/wp-dyn\/content\/article\/2008\/02\/06\/AR2008020604763.html\" title=\"The article\">The article<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The title says it all. According to the article linked below, Customs has been seizing electronics like cell phones and laptops on grounds of &#8220;suspected criminal activity.&#8221;\u00a0 Some travelers complained that their devices were taken for more than a week &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/10\/us-customs-seizes-electronics-at-borders\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":31,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-130","post","type-post","status-publish","format-standard","hentry","category-current-events"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/130","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\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=130"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/130\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}