4 ms·
Without some sort of feedback loop, its going to be difficult for Mapbox to cash in on my users data. It's not tied to an endpoint where they can sell advertisi
by ogre_codes 6y ago
Without some sort of feedback loop, its going to be difficult for Mapbox to cash in on my users data. It's not tied to an endpoint where they can sell advertising, nor is any of my use real-time.
It does allow offline use, so I should experiment with that. While offline use requires pre-loading tiles which reveals something about a person, it doesn't reveal more than a broad regional interest.
But in general, I agree. It's a murky situation. Any web request leaks information about the user.
- morelisp 6y ago> Without some sort of feedback loop, its going to be difficult for Mapbox to cash in on my users data. An IDFA also collected via any other service / broker provides such a feedback loop. Location data is reasonably valuable. Mapbox also offers a navigation API; this would be behavioral data from which companies like to try to derive interest and intent.
- codys 6y agoPresumably the author doesn't send the IDFA to mapbox, which makes linking profiles here more difficult/less reliable.
- ogre_codes 6y agoMy app is small small potatoes, I wouldn't use IDFA. I suspect Apples coming privacy tracking change will render most IDFA based cross app strategies irrelevant as developers scramble to eliminate that dreaded prompt.
- morelisp 6y agoThat depends on if the author has manually integrated Mapbox (via issuing their own HTTP requests) or just used their SDK in which case the SDK may do whatever the sandbox allows. And has been mentioned a few times in the thread - even if one app author goes out of their way to reimplement the API in a privacy-preserving way, all it takes is one that doesn't to reasonably link all the other requests based on other data points. (IP would be more than sufficient - but since it's a location service, even if all the apps run the requests through a proxy, location-at-time and location/destination pairs are also useful to help link.) In the end I don't think there's anything privacy-conscious app developers can do other than eschew external services as much as possible, clearly inform users when external services are used, and push for stronger regulation (from phone / OS manufacturers and the government) about data privacy.
- ogre_codes 6y ago> In the end I don't think there's anything privacy-conscious app developers can do other than eschew external services as much as possible, clearly inform users when external services are used, and push for stronger regulation (from phone / OS manufacturers and the government) about data privacy. This is the crux of it here. In particular, we seriously need regulations making the things Apple is pushing required by law, not something a company with its own vested interests pushes. Particularly since as many point out whenever this is discussed, there is a bit of opacity with regards to Apple's own apps.
- Nextgrid 6y ago> Without some sort of feedback loop, its going to be difficult for Mapbox to cash in on my users data Remember that every single request to them includes your device's IP, potentially user agent, and maybe even a unique identifier generated on first run which will correlate all those changing IPs together. Over time, IPs & user agents can very easily be connected together by a data broker with very high certainty.