Google sues the EU over search data: what changes for your Android phone

A fight about something very ordinary

Almost everyone reading this has typed a question into a search box today. That is exactly what this court case is about. The European Commission's argument is simple: if Google is the front door to the internet in Europe, rival search engines and rival AI assistants should be able to build products on comparable terms. Google's counter-argument is just as simple: handing over search and click data, and opening Android's deepest system functions to outside assistants, would damage user privacy and weaken the security of the phones in your pocket.

To understand why Brussels has this power at all, you have to look at the Digital Markets Act (DMA). It is not the AI Act. It is competition law aimed at "gatekeepers" — very large platforms that act as unavoidable intermediaries. Under the DMA, the Commission can not only fine a company up to 10% of its total worldwide annual turnover, it can also issue detailed, binding instructions about how a gatekeeper must behave. That is what happened in July 2026, and it is what Google is now challenging at the General Court, the EU's second-highest court.

Two orders, two deadlines

The first order concerns data. Google would have to give competing search engines and AI chatbot providers access to non-personal search and click data generated by European users, with the obligation to begin by January 2027. This is the part that matters most for AI. Building a competitive assistant requires enormous amounts of real queries — the messy, misspelled, half-finished questions people actually type. That data is precisely what Google has accumulated for two decades and what no European competitor can replicate from scratch.

The second order concerns Android. It would require Google to give rival AI assistants equal access to 11 system features that are currently available to its own Gemini assistant — features such as voice activation and the ability to execute actions inside other apps on your behalf. The Commission set deadlines of July and August 2027 for the operating-system changes to be completed.

The privacy argument, and a real tension

Google's stated objection is not mainly financial. The company argues that the Commission's requirements rest on an assumption of anonymisation that does not hold in practice, and that opening Android's system layer to third-party assistants would create new attack surfaces on devices used by hundreds of millions of Europeans.

There is a genuine legal knot here, and it is worth understanding because it will shape the case. Under the GDPR, truly anonymous data falls outside the regulation entirely — but data that can be re-linked to a person, even indirectly, remains personal data with all the accompanying obligations. Search logs sit uncomfortably in the middle: removing names and IP addresses is not the same as making a dataset genuinely unidentifiable, because query text itself often reveals who is asking. So the two EU frameworks pull in opposite directions. The DMA pushes for data sharing; the GDPR pushes for caution about exactly that sharing. Whoever loses in Luxembourg, that tension does not disappear.

Why OpenAI's name keeps appearing

The blunt way to put it: European AI companies and American rivals alike want access to the demand signal that Google owns. An assistant that can see what Europeans are actually searching for — and can be woken by voice on the phone they already own — starts from a very different position than one that cannot.

Google, meanwhile, has been building its own defence in product form. Gemini is deeply integrated into Android, and the Commission's order is essentially an attempt to make sure that integration is not a permanent advantage. Note that this is a fight about distribution, not about model quality. No court ruling will make anyone's model smarter.

What this could mean on a European phone in 2027

If the Commission's orders survive the appeal, the practical consequences for ordinary users are concrete rather than abstract. On an Android phone bought in Prague, Paris or Warsaw, you might be asked during setup which assistant should handle voice activation. A rival assistant could be allowed to perform actions inside apps — sending a message, booking a slot, adjusting a setting — rather than being restricted to a sandbox. And search alternatives could, in principle, return results informed by the same kind of click data that currently improves only Google's own ranking.

If Google wins, none of that happens, and the DMA's data-access model takes a serious hit — not just for search, but as a template for how Brussels intends to open up AI distribution in Europe. For broader context on how the EU's AI rules have matured, our magazine archive tracks the run-up to the mandatory phase.

Where the AI Act fits — and where it does not

It is easy to conflate the two regulations, so here is the short version. Since 2 August 2026, general-purpose AI obligations and the Article 50 transparency requirements of the EU AI Act are fully mandatory, enforced by the EU AI Office and national authorities. That law governs what AI systems must disclose and how they must behave. The DMA governs who gets access to platforms. Google's court case is about the second, not the first — which is why you will not see the AI Act cited in the appeal, even though the outcome will shape which AI assistants Europeans can realistically choose from.

What happens next

An appeal to the General Court does not automatically suspend an EU decision, which means the January 2027 and mid-2027 deadlines remain the working timeline unless Google separately requests and wins interim measures. Cases of this kind typically take well over a year, with a further possible appeal to the Court of Justice on points of law. In other words, the clock and the courtroom are now running in parallel — and for European phone users, the first tangible changes, if they come, will arrive before the judges have the final word.