SoylentNews

realDonaldTrump writes:

https://www.pcmag.com/news/368350/oops-twitter-accidentally-shared-location-data-with-advertiser

It supposedly only affects those with more than one Twitter account on iOS who opted into using Twitter's precise location feature on one of those accounts, but I received the alert despite having only a single account.

Twitter on Monday alerted some iOS users that its app accidentally collected and shared location data with a third party. The bug has since been fixed.

Twitter didn't mention exactly how many people were affected. It claims that only those with more than one Twitter account on iOS who opted into using Twitter's precise location feature on one of those accounts had their data exposed, but I received the alert despite having only a single account.

That alert says the bug was related to Twitter's advertising business, where clients pay for their ads to appear on the app based on users' current location.

"We had intended to remove location data from the fields sent to a trusted partner during an advertising process known as real-time bidding," Twitter said. "This removal of location did not happen as planned."

Twitter didn't reveal the name of this trusted partner. But it said the location data it sent was "fuzzed," so it was no more precise than a 3-mile area. Actual Twitter handles and unique account IDs were not shared during the process.

From foxnews.com/tech/twitter-accidentally-shared-user-data-with-advertising-partner we get the following:

"We have discovered that we were inadvertently collecting and sharing iOS location data with one of our trusted partners in certain circumstances. Specifically, if you used more than one account on Twitter for iOS and opted into using the precise location feature in one account, we may have accidentally collected location data when you were using any other account(s) on that same device for which you had not turned on the precise location feature."

[...] "We have confirmed with our partner that the location data has not been retained and that it only existed in their systems for a short time, and was then deleted as part of their normal process," it said. "We have fixed this problem and are working hard to make sure it does not happen again. We have also communicated with the people whose accounts were impacted to let them know the bug has been fixed."

Original Submission