Twitter apologises for sharing iOS location data

&Tab;&Tab;<div class&equals;"wpcnt">&NewLine;&Tab;&Tab;&Tab;<div class&equals;"wpa">&NewLine;&Tab;&Tab;&Tab;&Tab;<span class&equals;"wpa-about">Advertisements<&sol;span>&NewLine;&Tab;&Tab;&Tab;&Tab;<div class&equals;"u top&lowbar;amp">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;<amp-ad width&equals;"300" height&equals;"265"&NewLine;&Tab;&Tab; type&equals;"pubmine"&NewLine;&Tab;&Tab; data-siteid&equals;"111265417"&NewLine;&Tab;&Tab; data-section&equals;"2">&NewLine;&Tab;&Tab;<&sol;amp-ad>&NewLine;&Tab;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;<&sol;div><p>Twitter has apologised after a bug resulted in the sharing of location data from Apple mobile devices&period;<&sol;p>&NewLine;<p>The social media site said it discovered it was &OpenCurlyDoubleQuote;inadvertently collecting and sharing iOS location data with one of our trusted partners in certain circumstances”&period;<&sol;p>&NewLine;<p>Twitter said the location data has not been retained and has since been deleted&period;<&sol;p>&NewLine;<p><&excl;--Ads3--><&sol;p>&NewLine;<p>The company said&colon; &OpenCurlyDoubleQuote;Specifically&comma; if you used more than one account on Twitter for iOS and opted into using the precise location feature in one account&comma; we may have accidentally collected location data when you were using any other account&lpar;s&rpar; on that same device for which you had not turned on the precise location feature&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;Separately&comma; we had intended to remove location data from the fields sent to a trusted partner during an advertising process known as real-time bidding&period;<&sol;p>&NewLine;<blockquote class&equals;"twitter-tweet" data-width&equals;"550" data-dnt&equals;"true">&NewLine;<p lang&equals;"en" dir&equals;"ltr">Due to a bug in Twitter for iOS&comma; we inadvertently collected and shared location data &lpar;at the zip code or city level&rpar;&period; We have fixed the bug&comma; but we wanted to make sure we shared more of the context around this with you&period; More here&colon; <a href&equals;"https&colon;&sol;&sol;t&period;co&sol;n04LNt62Sa">https&colon;&sol;&sol;t&period;co&sol;n04LNt62Sa<&sol;a><&sol;p>&NewLine;<p>&mdash&semi; Twitter Support &lpar;&commat;TwitterSupport&rpar; <a href&equals;"https&colon;&sol;&sol;twitter&period;com&sol;TwitterSupport&sol;status&sol;1127988150125514753&quest;ref&lowbar;src&equals;twsrc&percnt;5Etfw">May 13&comma; 2019<&sol;a><&sol;p><&sol;blockquote>&NewLine;<p><script async src&equals;"https&colon;&sol;&sol;platform&period;twitter&period;com&sol;widgets&period;js" charset&equals;"utf-8"><&sol;script><&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;This removal of location did not happen as planned&period; However&comma; we had implemented technical measures to &OpenCurlyQuote;fuzz’ the data shared so that it was no more precise than zip code or city &lpar;5km squared&rpar;&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;This location data could not be used to determine an address or to map your precise movements&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;The partner did not receive data such as your Twitter handle or other unique account IDs that could have compromised your identity on Twitter&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;This means that for people using Twitter for iOS who we inadvertently collected location information from&comma; we may also have shared that information with a trusted advertising partner&period;”<&sol;p>&NewLine;<p>Twitter confirmed the information was not retained&comma; adding it &OpenCurlyDoubleQuote;only existed in their systems for a short time&comma; and was then deleted as part of their normal process”&period;<&sol;p>&NewLine;<p>The company said&colon; &OpenCurlyDoubleQuote;We have fixed this problem and are working hard to make sure it does not happen again&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;We have also communicated with the people whose accounts were impacted to let them know the bug has been fixed&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;We invite you to check your privacy settings to make sure you’re only sharing the data you want to with us&period;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;We’re very sorry this happened&period; We recognise and appreciate the trust you place in us and are committed to earning that trust every day&period;”<&sol;p>&NewLine;<p><&excl;--Ads4--><&sol;p>&NewLine;&Tab;&Tab;&Tab;<div style&equals;"padding-bottom&colon;15px&semi;" class&equals;"wordads-tag" data-slot-type&equals;"belowpost">&NewLine;&Tab;&Tab;&Tab;&Tab;<div id&equals;"atatags-dynamic-belowpost-68ed522f77c24">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;<script type&equals;"text&sol;javascript">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;getAdSnippetCallback &equals; function &lpar;&rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;if &lpar; false &equals;&equals;&equals; &lpar; window&period;isWatlV1 &quest;&quest; false &rpar; &rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&sol;&sol; Use Aditude scripts&period;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;tudeMappings &equals; window&period;tudeMappings &vert;&vert; &lbrack;&rsqb;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;tudeMappings&period;push&lpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;divId&colon; 'atatags-dynamic-belowpost-68ed522f77c24'&comma;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;format&colon; 'belowpost'&comma;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub; &rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;if &lpar; document&period;readyState &equals;&equals;&equals; 'loading' &rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;document&period;addEventListener&lpar; 'DOMContentLoaded'&comma; window&period;getAdSnippetCallback &rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub; else &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;getAdSnippetCallback&lpar;&rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;<&sol;script>&NewLine;&Tab;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;&Tab;<&sol;div>


Discover more from London Glossy Post

Subscribe to get the latest posts sent to your email.

- Advertisement -
Exit mobile version