NewApp Digest
search bot

data sharing

Android Apps Share Location Data With Advertisers by Default
AppWizard
August 6, 2026

Android Apps Share Location Data With Advertisers by Default

A recent investigation by the Electronic Frontier Foundation (EFF) revealed that many Android applications contain third-party code that automatically transmits users' precise location data to external companies, including advertisers and data brokers, once location permission is granted. There are no specific location permissions for Software Development Kits (SDKs) on Android, meaning that granting one app access allows all bundled components to access the same data. Developers may be unaware that their apps are configured to share location histories with external firms, as advertising SDKs often prioritize data collection for revenue generation. The EFF calls for advertising SDKs to stop making personal data sharing the default setting and urges developers to disable unnecessary data collection. Location data can reach data brokers, which may experience breaches, compromising user privacy and security. This situation poses hidden risks for investors in the mobile advertising sector, as legal challenges and reputational damage may arise from regulatory scrutiny of location data practices. The EFF emphasizes that app-level permissions do not provide meaningful consent for third-party data sharing, highlighting the value and risks associated with location data.
Developers: Beware of Ad Libraries that Betray Your Users’ Location
AppWizard
August 5, 2026

Developers: Beware of Ad Libraries that Betray Your Users’ Location

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.
Are your Android apps secretly sharing your location with advertisers? Some developers are accidentally leaving on this critical data-invading setting when using third-party SDKs
AppWizard
August 5, 2026

Are your Android apps secretly sharing your location with advertisers? Some developers are accidentally leaving on this critical data-invading setting when using third-party SDKs

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.
Android users, beware: Your location data might be being inadvertently shared
AppWizard
August 5, 2026

Android users, beware: Your location data might be being inadvertently shared

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.
Android app developers may be unwittingly sharing their users' location data with advertisers
AppWizard
August 4, 2026

Android app developers may be unwittingly sharing their users’ location data with advertisers

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.
E.U. Orders Google to Open Android Mic, Camera and Screen to Rival AI Assistants
AppWizard
July 17, 2026

E.U. Orders Google to Open Android Mic, Camera and Screen to Rival AI Assistants

The European Commission has mandated that Google must provide equal access to rival AI assistants within its Android ecosystem, allowing them to use the same functionalities as Google's Gemini assistant. This includes access to the camera, microphone, and on-screen content, as well as background operation capabilities. Google is required to implement these changes in the upcoming Android 18 release by August 1, 2027. The directive includes two binding specifications under the Digital Markets Act, one of which requires Google to share anonymized search query, click, and ranking data with competing search engines and AI chatbots for a fee. The Android decision involves 11 operating system features, with five classified as restricted, requiring certification for third-party applications. These restricted features include access to on-device data shared by apps, context-aware intelligence, structured on-device integration, screen automation, and system integration. The remaining six features do not require certification, allowing broader access to ambient data, always-on hotword detection, long-press invocation, system-level on-device models, third-party model implementation, and background execution capabilities. Google must establish a Qualified AI Assistant Programme to facilitate access to gated features, allowing third-party Trusted Certification Authorities to certify assistants at no cost. The certification process must be fair and non-discriminatory, and users can consent to bypass the certification requirement for specific services and devices. By August 2027, both certified and user-approved uncertified assistants will be able to interact with applications on a virtual display. Google is also required to anonymize search data before sharing, ensuring user privacy and limiting data access to recipients who meet specific criteria. Kent Walker, Google's president of global affairs, expressed concerns about the security implications of granting external apps access to sensitive device permissions and criticized the anonymization methods for search data. The final measures reflect significant changes from earlier drafts, introducing more stringent requirements regarding data sharing and certification processes.
Telegram Trolls France On World Cup 2026 Exit; The Reason Is Not Football At All
AppWizard
July 17, 2026

Telegram Trolls France On World Cup 2026 Exit; The Reason Is Not Football At All

Spain defeated France 2-0 in the semifinals of the FIFA World Cup 2026, advancing to the finals. Telegram Messenger expressed schadenfreude over France's exit, tweeting "BYE BYE" with a match result screenshot. Pavel Durov, Telegram's co-founder, faced legal issues in France, including a preliminary investigation into criminal activities involving Telegram, his detention in August 2024, indictment on 12 charges, and a subsequent policy change regarding user data sharing with authorities. Durov characterized his arrest as politically motivated, while Elon Musk criticized the situation, questioning the scrutiny faced by tech leaders.
Google swears (again) that data-sharing rules will help scammers, threaten your search history
AppWizard
June 30, 2026

Google swears (again) that data-sharing rules will help scammers, threaten your search history

Google is opposing the European Union's proposed amendments to the Digital Markets Act (DMA), warning that these changes could jeopardize user privacy and security. The DMA aims to reduce the dominance of major tech platforms by requiring gatekeepers like Google to share more data with competitors. Google is particularly concerned about the implications of sharing search data and granting third-party AI services access to sensitive Android features, fearing that this could lead to increased fraud and cyberattacks. The European Commission is pushing for Google to provide rival search engines with access to anonymized search data to enhance competition, but Google argues that once this data leaves its infrastructure, it becomes difficult to protect. DuckDuckGo and some researchers believe the Commission's proposals adequately address privacy risks, while others acknowledge the risks but suggest they should be balanced against technical protections. Additionally, EU regulators are advocating for deeper integration of competing AI assistants with Android, which Google warns could compromise existing security measures. Apple has shown support for some of Google's concerns regarding access to operating systems.
The database storage problem is solved. Here’s what comes next.
Tech Optimizer
June 25, 2026

The database storage problem is solved. Here’s what comes next.

Postgres has been a reliable transactional database for three decades, used for managing customer records and financial transactions. Innovations in the Postgres ecosystem are now focused on minimizing data movement rather than just data storage. The challenge of interoperability is becoming crucial, as organizations seek to share operational data seamlessly across various systems without creating additional copies or pipelines. Many organizations are spending as much effort on data movement as on data storage. Postgres is increasingly viewed as the authoritative system for critical information, and its role is evolving to facilitate better interaction with operational data. Technologies like logical replication and change data capture are enhancing Postgres's integration within data ecosystems. The rise of AI has highlighted the need for real-time access to operational data and has prompted organizations to reconsider the necessity of maintaining multiple copies of the same data. The database industry is shifting focus from optimizing storage to enabling effortless data sharing across systems. Postgres continues to adapt to new workloads and architectural patterns, maintaining its reputation as a stable foundation for operational data while expanding its capabilities through innovative extensions.
Search