{"id":14872,"date":"2020-06-28T06:58:00","date_gmt":"2020-06-28T04:58:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=14872"},"modified":"2021-07-14T11:31:54","modified_gmt":"2021-07-14T09:31:54","slug":"datenschutzproblem-bei-twitter","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/06\/28\/datenschutzproblem-bei-twitter\/","title":{"rendered":"Privacy issues at Twitter"},"content":{"rendered":"

[German<\/a>]This week Twitter had to apologize to customers for a data leak where unauthorized persons gained access to business data (invoice data). Here are a few details known so far.<\/p>\n

<\/p>\n

\"\"I became aware of this issue through blog reader Tobias W. these days. He probably received the following mail from Twitter:<\/p>\n

Hello,<\/p>\n

We are writing to let you know of a data security incident that may have
\ninvolved your personal information on ads.twitter.com and
\nanalytics.twitter.com.<\/p>\n

We became aware of an issue that meant that prior to May 20, 2020, if
\nyou viewed your billing information on ads.twitter.com or
\nanalytics.twitter.com the billing information may have been stored in
\nthe browser's cache. Examples of that information include email address,
\nphone number, last four digits of your credit card number (not complete
\nnumbers, expiration dates or security codes), and billing address. If
\nyou used a shared computer, it is possible that if someone used the
\ncomputer after you they could have seen the information stored in the
\nbrowser's cache (most browsers generally store data in their cache by
\ndefault for a short period of time like 30 days).<\/p>\n

On May 20, 2020, we updated the instructions that Twitter sends to your
\nbrowser's cache to stop this from happening. While we have no evidence
\nthat your billing information was compromised, we want to make sure
\nyou're aware of the issue and how to protect yourself going forward. If
\nyou currently use a shared computer to access your Twitter Ads or
\nAnalytics billing information, we recommend clearing the browser cache
\nwhen you log out.<\/p>\n

We're very sorry this happened. We recognize and appreciate the trust
\nyou place in us, and are committed to earning that trust every day. If
\nyou have additional questions, you can write to our Office of Data
\nProtection here <zensiert><\/p>\n

Thank you.<\/p>\n

Twitter International Company
\nOne Cumberland Place, Fenian Street
\nDublin 2, D02 AX07 IRELAND<\/p><\/blockquote>\n

It has been found that users store confidential information about business transactions (name, e-mail, credit card number, etc.) in the local cache of the browser as they are entered. This bears the risk that unauthorized third parties can access sensitive data via the cache.<\/p>\n

On 20 May 2020, Twitter updated the instructions on how to use the browser cache to prevent the data from flowing out this way. Although people have no evidence that billing data has been compromised, Twitter officials want to make sure that users are aware of the problem and know how to protect themselves in the future.<\/p>\n

If you use a shared computer to access Twitter ads or retrieve billing information, Twitter people recommend that you clear your browser cache when you log out. The BBC has published an article about this here<\/a> – and here<\/a> you can find something about it.<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]This week Twitter had to apologize to customers for a data leak where unauthorized persons gained access to business data (invoice data). Here are a few details known so far.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[580],"tags":[69,2259],"class_list":["post-14872","post","type-post","status-publish","format-standard","hentry","category-security","tag-security","tag-twitter"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=14872"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14872\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=14872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=14872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=14872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}