The Register reports that Google collects and transmits Android user data, including hardware identifiers and location, to its servers even before a user opens any apps or completes device setup. This pre-setup data collection involves several Google services and occurs during the initial boot process, transmitting information like IMEI, hardware serial number, SIM serial number, and nearby Wi-Fi access point details. While Google claims this data is crucial for essential services like fraud prevention and software updates, the article raises privacy concerns, particularly because users are not informed of this data collection nor given the opportunity to opt out. This behavior raises questions about the balance between user privacy and Google's data collection practices.
Tim investigated the precision of location data used for targeted advertising by requesting his own data from ad networks. He found that location information shared with these networks, often through apps on his phone, was remarkably precise, pinpointing his location to within a few meters. He successfully identified his own apartment and even specific rooms within it based on the location polygons provided by the ad networks. This highlighted the potential privacy implications of sharing location data with apps, demonstrating how easily and accurately individuals can be tracked even without explicit consent for precise location sharing. The experiment revealed a lack of transparency and control over how this granular location data is collected, used, and shared by advertising ecosystems.
HN commenters generally agreed with the article's premise that location tracking through in-app advertising is pervasive and concerning. Some highlighted the irony of privacy policies that claim not to share precise location while effectively doing so through ad requests containing latitude/longitude. Several discussed technical details, including the surprising precision achievable even without GPS and the potential misuse of background location data. Others pointed to the broader ecosystem issue, emphasizing the difficulty in assigning blame to any single actor and the collective responsibility of ad networks, app developers, and device manufacturers. A few commenters suggested potential mitigations like VPNs or disabling location services entirely, while others expressed resignation to the current state of surveillance. The effectiveness of "Limit Ad Tracking" settings was also questioned.
Summary of Comments ( 22 )
https://news.ycombinator.com/item?id=43253167
HN commenters discuss the implications of Google's data collection on Android even before app usage. Some highlight the irony of Google's privacy claims contrasted with their extensive tracking. Several express resignation, suggesting this behavior is expected from Google and other large tech companies. One commenter mentions a study showing Google collecting data even when location services are disabled, and another points to the difficulty of truly opting out of this tracking without significant technical knowledge. The discussion also touches upon the limitations of using alternative Android ROMs or de-Googled phones, acknowledging their usability compromises. There's a general sense of pessimism about the ability of users to control their data in the Android ecosystem.
The Hacker News post discussing The Register's article about Google's Android tracking practices has generated a substantial discussion with various viewpoints and insights.
Several commenters express concerns about the extent of data collection occurring before users even interact with apps. They discuss the implications of pre-installed apps and system-level services sending data to Google, highlighting the potential privacy risks, especially for users unaware of this background activity. Some debate the necessity of this data collection for functionality versus Google's potential exploitation for advertising or other purposes. The discussion also touches upon the difficulty for users to opt out of this tracking, given its integration within the Android operating system itself.
One recurring theme is the comparison of Android's data collection practices to those of Apple's iOS. Commenters debate which operating system provides better privacy, with some arguing that Apple's approach is more transparent and user-centric. Others point out that both companies collect significant user data, albeit through different mechanisms.
A few commenters delve into the technical aspects of the data collection, discussing the role of Firebase Cloud Messaging (FCM) and other system-level components. They explain how these components facilitate communication between devices and Google servers, enabling features like push notifications but also potentially contributing to the pre-app usage data collection.
The discussion also extends to the broader issue of data privacy in the tech industry. Commenters express frustration with the lack of control users have over their data and the pervasive nature of tracking across various platforms and services. Some advocate for stronger regulations and greater transparency from tech companies regarding data collection practices.
There are also more skeptical comments questioning the novelty or significance of the findings in The Register's article. Some suggest that this type of background data transmission is inherent in modern mobile operating systems and necessary for basic functionality. They argue that the article might be overstating the privacy implications or presenting information already known within the tech community.
Finally, some commenters offer practical advice for users concerned about privacy, such as using alternative ROMs like LineageOS or exploring privacy-focused mobile operating systems like GrapheneOS. They discuss the trade-offs between functionality and privacy, acknowledging that more privacy-centric options may require technical expertise or involve sacrificing certain features.