sharing

AppWizard
August 5, 2026
Advertising companies provide software development kits (SDKs) for mobile app monetization, which often automatically transmit users' location data to ad systems and location data brokers, raising privacy concerns. Many developers and users may be unaware of this data sharing. When developers allow SDKs to collect location data, it poses risks beyond targeted ads, including potential misuse by agencies like ICE and global surveillance. Location data brokers harvest precise movements of individuals, often without their consent, through mobile applications. Some apps directly collaborate with data brokers, while others leak data through advertising SDKs during real-time bidding (RTB) auctions. An incident in 2025 revealed that many apps unknowingly contributed to a location data broker's database. Developers must understand their SDKs' location-sharing practices to mitigate risks. Advertising SDKs can collect location data automatically once users grant permission, without specific permissions for the SDKs themselves. Precise location data can be collected when apps have location permissions, leading to potential privacy violations. Several SDKs have been identified as collecting location data by default, increasing the risk of unintentional data leaks. The Electronic Frontier Foundation (EFF) found that four advertising SDKs collect users' location data by default when location permissions are granted. InMobi encourages location sharing for higher revenue, while BidMachine updated its documentation after EFF's inquiry, confirming precise location data collection. Verve's SDK also collects location data by default but presents a cautious narrative in its Play Store guidance. Huawei's SDK recommends obtaining location permissions to enhance revenue, with default location sharing occurring if permissions are granted. Location data can be shared without users' knowledge or meaningful consent, complicating informed consent issues. The focus on four SDKs does not imply that others adequately protect location data, as many have faced criticism for similar practices. Studies indicate that SDKs often encourage increased data collection through design and documentation, leading to minimal control for developers over data transmission. The EFF's analysis highlights that advertising SDKs incentivize location data sharing through default settings and unclear documentation. Developers should assess third-party SDKs and disable unnecessary data collection. Regulators must hold developers accountable for unlawful data sharing, while legislators should enact laws to protect location privacy and address online behavioral advertising, which drives data tracking.
AppWizard
August 5, 2026
Developers often rely on third-party software development kits (SDKs) for mobile app monetization, which can compromise user privacy due to invasive data-collection features. The Electronic Frontier Foundation (EFF) has raised concerns about these SDKs' default settings that collect sensitive location data without explicit user consent. Location data is valuable for advertisers, allowing targeted marketing, but permissions granted to apps often extend to SDKs, enabling data collection without informed consent. The EFF emphasizes that app-level location permissions do not signify meaningful consent for third-party SDKs. The location data collected has been used by intelligence agencies and law enforcement, raising ethical privacy concerns. The EFF recommends that developers prioritize user privacy, regulators hold app developers accountable for unlawful data sharing, and legislators consider enacting federal laws similar to the GDPR to protect user privacy and potentially ban behavioral advertising.
AppWizard
August 5, 2026
Recent findings from the Electronic Frontier Foundation (EFF) indicate that many applications on Android phones may unintentionally share users' location data with advertisers without explicit user knowledge. This issue arises from certain Software Development Kits (SDKs) used by app developers, which collect location data by default when users grant permission. The EFF report emphasizes that users likely do not expect their location data to be shared with third parties. Android users can manage their location sharing preferences through the device's Settings by reviewing app permissions or disabling location sharing entirely, though the latter may impact apps that require location access.
AppWizard
August 5, 2026
Cinder City is an open-world cinematic third-person shooter set in a dystopian near-future Seoul. The game's Steam page initially listed a requirement of 64GB of RAM, which was later corrected to a minimum of 32GB. A pre-alpha playtest is scheduled for August 14-16, available only to participants in the United States who are at least 16 years old and agree to a non-disclosure agreement. The publisher, NC, has indicated that final system requirements may be adjusted as optimization progresses. Additional playtests will be available in the future for a broader audience.
AppWizard
August 5, 2026
Recent research from the Electronic Frontier Foundation (EFF) has revealed that millions of Android users' location data are being inadvertently exposed to advertisers through third-party code libraries. This occurs when seemingly harmless applications, like weather services and fitness trackers, integrate third-party SDKs that collect user location information automatically upon permission approval, often without developers' awareness. Data brokers aggregate this location information to create detailed movement profiles sold to advertisers and government agencies. Despite privacy regulations like GDPR and CCPA, enforcement is inconsistent, and developers may claim ignorance regarding data practices they did not implement. Google has improved Android's privacy controls, but visibility into third-party libraries accessing data remains limited. Developers face challenges in auditing third-party code due to resource constraints, leading to a complex landscape where user information traverses multiple entities without clear accountability. Privacy advocates are calling for new technical standards to require SDKs to disclose their data practices.
AppWizard
August 4, 2026
Mobile apps often require precise location data for functionality, but there are concerns about the unintentional sharing of this sensitive information with third parties, such as advertisers and data brokers. The Electronic Frontier Foundation (EFF) found that third-party code in apps may collect location data without users' explicit consent due to default settings in software development kits (SDKs). Unless developers disable this feature, SDKs inherit app permissions, leading to the collection of users' location data. This raises privacy issues, as users' location histories can be sold to data brokers and potentially accessed by military and intelligence agencies. The EFF identified that certain Android apps, downloaded over 60 million times, were sharing location data without user awareness. Currently, there are no SDK-specific location permissions, meaning that consent to share location data with an app also extends to advertisers. The EFF calls for a change in industry standards to prevent default data sharing by advertising SDKs.
AppWizard
August 4, 2026
Security researchers found that several Samsung Smart TV applications, including Pac-Man, were embedding residential proxy SDKs from data brokers like Bright Data. In response, Samsung has banned the inclusion of residential proxy functionality in new app submissions and is working to remove existing apps with such software. The investigation by Norwegian cybersecurity firm Mnemonic revealed that the Bright Data SDK was integrated into various gaming applications, some promoted by Samsung. While Samsung TVs were not automatically sharing internet connections, the SDK could be activated remotely by developers, requiring user consent. Once consent was granted, the proxy service could operate in the background. Many Samsung TV applications were found to download most of their code from remote servers, complicating verification processes. The issue of residential proxy software is not limited to Samsung, as it has also been identified in various Android apps and devices. Following these findings, LG and Google have also taken measures to address the risks associated with residential proxy networks.
Search