app permissions

AppWizard
August 6, 2026
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.
AppWizard
August 6, 2026
A report from the Electronic Frontier Foundation (EFF) highlights concerns about third-party software development kits (SDKs) in mobile applications collecting and sharing user location data with advertising companies, often without user consent. Many developers use these advertising SDKs for monetization, but their default settings allow for location data collection. This data is sent to advertising companies and location data brokers, which can misuse it in sensitive contexts. Users may unknowingly expose their location data when granting permissions to apps, as third-party SDKs can access this information without clear user awareness. The EFF identified several advertising SDKs, including InMobi, BidMachine, Verve’s HyBid, and Huawei’s Petal Ads, that collect and share location data by default. Developers are encouraged to review SDK settings to protect user privacy, and the EFF calls for regulatory scrutiny of data harvesting practices.
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 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.
Winsage
July 18, 2026
Microsoft has acknowledged a bug in Windows 11 related to the Capability Access Manager (camsvc) that causes significant storage issues for users. The bug leads to an abnormal increase in the size of the CapabilityAccessManager.db-wal SQLite Write-Ahead Log file, which typically should be a few megabytes but has been reported to grow to 70-80 GB, and in some cases, over 200 GB or even up to 500 GB. This growth depletes available SSD space without any new files being added by users. The issue was highlighted by a user on the Microsoft Q&A forum, prompting others to check their disk space and find similar problems. Additionally, Windows Storage Settings misreported capacity usage. Microsoft confirmed the bug and released a hotfix in the KB5095093 update, urging users to install it to prevent further expansion of the log file.
Winsage
July 15, 2026
Microsoft's July Patch Tuesday update addressed a significant storage issue for Windows 11 users related to the CapabilityAccessManager.db-wal file, which had been consuming excessive storage space, with reports of usage reaching up to 500 GB. The bug originated from the Capability Access Manager service, which normally allows the file to occupy only a few megabytes. Update KB5101650 was released to fix this issue, improving disk space usage for the file. However, it is unclear if existing oversized WAL files will automatically resize. Users are advised to check the size of their WAL file using the Command Prompt or third-party tools, and if it remains large, to delete it following the update documentation.
Winsage
July 9, 2026
Microsoft has acknowledged a bug in Windows 11 that causes the Capability Access Manager's write-ahead log file to expand indefinitely, potentially exceeding 500GB of storage on affected devices. This issue is addressed in update KB5095093, which includes builds 26200.8737 and 26100.8737. Users can manually install this update via the optional updates section of Windows Update or wait for its automatic rollout during the July 2026 Patch Tuesday. The Capability Access Manager manages app permissions and logs usage of privacy-sensitive features, but the WAL file continues to grow unchecked on affected systems. The file can reach sizes from 70GB to over 513GB. To check if a system is affected, users can check storage settings or use Robocopy to verify the file size. The update is available through the Optional updates section and will be included in the cumulative update on July 8, 2026. The excessive size of the WAL file can lead to critical storage shortages and related issues, but it does not compromise the security or core functionality of the permission system. Microsoft has not confirmed if Windows 11 26H1 Insider builds are affected.
Search