New findings by the Electronic Frontier Foundation aim to warn app developers that some of the third-party code they place in their apps may also collect their users' location data…

For many apps, granting permission to access your device’s precise location makes sense. Your favorite weather app needs to know where you are to get the day’s forecast, or your go-to fitness app for tracking your running route. But some apps are also inadvertently sharing their users’ location data with third parties, including advertisers and data brokers, because the app developer may not know that this data-sharing setting is enabled by default. New findings by the Electronic Frontier Foundation aim to warn app developers that some of the third-party code they place in their apps may also collect their users’ location data when they grant permission to the app. Unless the developer actively switches off the collection, the code snippet (known as software development kits, or SDKs) will inherit the app’s permissions and collect the user’s precise location data. The EFF says many developers might not realize that they are sharing their users’ location data with third parties by default and urged app makers to disable unnecessary data collection whenever possible. While advertising SDKs are promoted as a way for developers to monetize their app, the trade-off is that the users’ location histories get fed to data brokers, who monetize that information, which then gets sold to militaries, governments, and intelligence agencies, like the FBI. The data is also a security and privacy risk if it gets hacked or stolen, which some data brokers have experienced. Among the Android apps that the EFF identified that were quietly sharing users’ location data included two that had been downloaded a combined 60 million times to date. The EFF ran its tests by analyzing the apps’ network traffic and seeing which services are receiving the users’ location data.