Gemini Spark skips Europe. Gemini 3.7 Flash does not have to.
Google's own page excludes the EEA, UK, Switzerland and Nigeria from Gemini Spark. What that really blocks, and what Europeans can still run.
The footnote that decides what you get
Google's support page for Gemini Spark spends most of its length explaining how to hand the assistant a task and let it work in the background. Then, in the section that lists who is eligible, one sentence quietly removes a continent.
Available wherever Gemini Apps are supported, except in the European Economic Area, Nigeria, Switzerland, and the United Kingdom.
That is Google's own wording, on Google's own help site, still live as of 2 September 2026. Between the EEA, the UK and Switzerland it covers essentially all of Western Europe, plus Africa's most populous country for good measure. If you are reading this from Brussels, Berlin, Manchester or Zurich, Spark is not something you can turn on. There is no waitlist and no toggle. Your country is on a list.
That is the confirmed part, and it is worth being precise about, because the version of this story circulating since mid August is broader than what Google actually published. The restriction names Spark, the agent. It does not name Gemini 3.7 Flash, the model underneath it. We went looking for a Google page that puts the model itself behind the same wall and could not find one. The distinction sounds like pedantry for about ten seconds, and then it turns out to be the entire question of what a European reader can and cannot use this month.
So what is Spark, and what runs it?
Gemini 3.7 Flash arrived on 13 August 2026, three weeks after 3.6 Flash, which tells you something about the pace Google has settled into. Google's announcement calls it "our most intelligent workhorse model yet for coding and agents", and the gains it claims sit in long horizon software engineering and multi step planning.
Spark is the product built on top of it: an always on personal agent for Google AI Pro and Ultra subscribers, announced as live in more than 160 countries. Google's eligibility list is strict beyond geography. You must be 18 or over. You must sign in with a personal Google account, so work and school accounts are out. You must have Keep Activity enabled, meaning Google retains a record of what you do with it. And it runs only in the Gemini mobile app, the Gemini app on Mac, and the web app.
Read that list again with the exclusions in mind. An agent that acts on your behalf across your own account, that needs activity retention switched on to function, is precisely the shape of product that runs into the most friction in the jurisdictions named. Google does not say that. Google publishes the list of excluded countries and offers no reason at all, which is its right and also its habit.
Why those four names keep appearing together
The EEA, the UK and Switzerland form a familiar cluster in product footnotes, and the common thread there is regulatory. Nigeria is the one that surprises people, until you remember the Nigeria Data Protection Act 2023, the law that set up the country's data protection commission. So the grouping tracks something, though Google has admitted nothing and this remains an inference drawn from the shape of the list. What you can observe across the industry is that the markets with the most developed data protection regimes are the markets where agentic features arrive late, arrive limited, or do not arrive.
The asymmetry is what turns this from inconvenient into genuinely annoying. A European subscriber on Google AI Pro pays the same monthly amount as an American one and receives a smaller product. Nobody discounts for the missing agent. The bill is identical and the footnote is where the difference lives.
The pattern runs wider than one agent
Spark is the clearest current example. It is nowhere near the only one. Look at what Google shipped on 27 August, all inside a single announcement about AI Mode and travel. Flight price tracking went live in more than 180 countries. Viewing flight and hotel costs in loyalty points and miles went out globally. Hotel discovery and booking started rolling out in the United States, in English. One announcement, one day, three features, three completely different maps.
Nobody is doing this to annoy Europeans. Booking flows touch payments, consumer protection rules and partner contracts that differ per country, and the legal work genuinely takes longer than the engineering. But the effect on a reader in Lyon or Lisbon is the same either way: you read the announcement, you open the app, and one of the three things you just read about is missing.
It also cuts the other way, which is the part the frustration usually skips. The same summer that withheld an agent from Europe brought ChatGPT advertising to it. Reporting from late August put the European ad rollout at 24 August 2026, covering all 27 EU member states plus Iceland, Liechtenstein, Norway and Switzerland. We could not confirm that date on an OpenAI page directly, so treat it as reported and not as a company statement. Take the date loosely and the shape of it still holds across the two examples above: on this continent, a feature that acts on your data by itself clears legal review a great deal more slowly than a feature that sells space in front of you.
Which rules apply depends on how you arrive
One structural point does most of the work here, and it explains why the Spark restriction and the 3.7 Flash question have different answers.
A model and a consumer app built on that model are governed separately. The app has its own terms, its own compliance posture and its own country by country rollout schedule. The model, served over an API to other developers, sits under a different agreement with different constraints. A company can gate a feature inside its own app in your country while continuing to serve the underlying model to businesses operating there, and this happens constantly, because the risk profile of an agent acting inside your account is nothing like the risk profile of a text completion endpoint.
Which of those two regimes you are subject to depends entirely on how you reach the model. Open the Gemini app and you are a consumer in a specific country, and the app knows exactly which one. Use a third party app that calls the model over an API and the request originates from that app's servers instead of your device. Your location is not part of the call.
Where we come into this
We added Gemini 3.7 Flash to MultiChats on 14 August 2026, the day after Google announced it. Calls run against Google's API from our backend, so the request to Google leaves our infrastructure. It sits in the model picker for Pro and Pro+ subscribers alongside sixty models from eighteen providers, and it handles image, PDF, video and text attachments, web search and reasoning. In our app it carries a working context ceiling of 300,000 tokens, deliberately short of the provider's headline figure, because we cap effective windows to keep long conversations from degrading.
What we do not give you is Spark. There is no always on agent, and nothing runs in the background on your behalf. You get the model and the conversation around it. The product Google built on top of that model stays where Google put it. Anyone telling you a third party app can hand you Spark in Amsterdam is selling something, and while we are on the subject, no European cloud provider hosts Gemini either. It is Google's proprietary model, served by Google. Companies like Scaleway host open weight models, which is a different thing entirely. Pro is $20.99 a month, with the full breakdown on our pricing section.
Plan for the lag, because it is structural
If you take one operational habit from this, make it this one: when a US announcement excites you, go find the vendor's support page before you go find the news coverage. The exclusion list almost never appears in the blog post. It lives in a footnote on a help page, linked from a plans page, three clicks deep, and it is the only version that is actually authoritative. It also changes without announcement, in both directions.
The honest summary of where things stand is narrower than the headlines and slightly worse. Europeans have not been cut off from Gemini 3.7 Flash; no Google page says that, and repeating it makes the real problem harder to see. What Europeans have lost is Spark, and behind Spark, the whole category it belongs to. Agents arrive when the legal work is finished, which for the more ambitious ones may be a very long time, or never in their current form.
That gap is now a permanent feature of the rollout, and no subscription upgrade closes it. The sensible response is to stop waiting on any single provider's app to decide what you have access to. Keep a route to the models that does not depend on which country your phone thinks it is in. That is a smaller consolation than an autonomous assistant, and it is the one that is actually available.