Ddos 
The open-source cloud storage application Nextcloud has long relied on the highly critical “Full Files Access” permission to enable comprehensive data synchronization. However, beginning in September 2024, Google denied Nextcloud Files for Android the continued use of this permission, citing security concerns and recommending more privacy-oriented alternatives such as the Storage Access Framework or the MediaStore API.
Nextcloud found Google’s reasoning unconvincing, particularly since the company had already initiated discussions with Google about this permission in mid-2024 — discussions that received no response. Then, in September, Google abruptly revoked the permission and blocked Nextcloud Files from releasing further software updates.
As of May 2025, Nextcloud had yet to find a resolution. In response, the company published a sharply worded blog post outlining its frustrating struggle with Google. Nextcloud drew parallels with recent massive fines imposed by the European Union on Apple and Meta for violating the Digital Markets Act, suggesting that Google was engaging in similarly anti-competitive practices.
In the blog post, Nextcloud stated: “We suppose Google can’t get away with this versus Apple or Microsoft, as those companies would retaliate. But smaller companies, especially those building disruptive technologies like ours, are fair game for them. Big Tech is scared that small players like Nextcloud will disrupt them, like they once disrupted other companies. So they try to shut the door.”
As it turns out, public pressure still holds power. Despite a year of unsuccessful negotiations, just days after publishing its blog post, Google offered to reinstate file access permissions for Nextcloud Files — although it issued no public statement on the matter.
But why is this permission so vital for Nextcloud? While “Full Files Access” does raise legitimate privacy concerns, it is essential for Nextcloud to deliver a fully functional file synchronization experience. Google’s blanket requirement for apps to adopt its new file access frameworks undermines this capability, effectively crippling core features of the application.
Indeed, for developers, there are legitimate scenarios where the use of sensitive permissions is necessary and justified. Yet Google’s current approach leans toward blanket restrictions, resulting in a rigid approval process that often rejects even valid and compliant requests for sensitive access.
Donate