[abalone]

> No. Uber gets location data FROM Foursquare.

This doesn't make sense and contradicts the article. Don't apps have to send coordinates to Foursquare to get location names? Foursquare then holds onto that data and tracks you. Perhaps also matching it to other services with a unified ID.

Update to your edit: The article strongly implies that Foursquare has figured out how to associate location data from multiple services into a single view. Apps that use Foursquare are feeding Foursquare very detailed location data about you, even if they're only using it to look up location names. It means Foursquare is getting all your Uber destinations and all your geotagged social media posts. The article literally describes how they've taken this data and turned you into a "card" that tracks your ID across services:

He taps on one profile, called “Harry,” and a pie chart pops up that details the habits of the real person associated with that advertising ID. “Harry spends a lot of time in Midtown, sometimes goes to parks, and rides the subway,” Crowley says, looking over the data Foursquare has assembled from the person’s use of popular apps and geotagging services.

[secabeen]

If you're just using the Foursquare API, they don't. The search API call doesn't require anything more than Lat and Long: https://developer.foursquare.com/docs/api/venues/search

However, they also have their Pilgrim SDK, which you incorporate into your app to have constant, passive location data available:

> Welcome to the Pilgrim SDK—the always on, passive location detection engine by Foursquare. The Pilgrim SDK provides contextual awareness to mobile applications and connected devices to understand where and how your users are moving through the real world.

> By default, Pilgrim SDK runs in the background and pushes you visits when it detects a stop.

My guess is that the Pilgrim SDK includes the device Advertising ID in the data it sends back to Foursquare to implement this.

[bigdubs]

> The search API call doesn't require anything more than Lat and Long: https://developer.foursquare.com/docs/api/venues/search

That Lat+Long, the implied time of the venue search call, and some type of disambiguation user id is all you'd need to start building a location history for someone.

[sfifs]

A reasonably dense geo, timestamp and IP address event stream over time (ie. Multiple apps sending over time reasonably frequently) should have sufficient information to associate ids. However most ad tech companies including I believe Google and FB are very leery of doing this "Harry" type of stunt and arrange data pipelines in a way that this cannot be done at any aggregation less than a few hundred IDs and export anything beyond segment data to prevent re-identification. I'm very surprised these people are touting it

[mastazi]

> However most ad tech companies including I believe Google and FB are very leery of doing this "Harry" type of stunt and arrange data pipelines in a way that this cannot be done at any aggregation less than a few hundred IDs

I would be interested to see any sources about this (I’m not questioning what is said in the comment, just genuinely curious about this topic)

[kenneth]

Various apps use Foursquare's API to query what is at a specific coordinate. Foursquare knows what queries were made by a unique device. That's it. Not sure why this is so controversial.

[abalone]

Right? All they’d know about you is your home address, where you take Ubers to/from, where you like to eat, shop, places you post from, your habits over time, and anything else they could correlate across the myriad apps that send your precise, unique location to them. NBD.

[shereadsthenews]

This is why "home" is a few blocks away from home in my Uber profile and why I allow it location services only when the app is running.

[richardhod]

Everybody should do this as standard, and it should be in all the 'howto guides'!

[mgkimsal]

how would they know anything about my unique device if an app is just using their API? unless the API requires 'unique device id'? Or are they embedding a foursquare sdk, which grabs that info on API calls?