The EEA, UK and Switzerland Wait Continues: Regulation vs Rollout Speed

At launch, PYMNTS reported that ChatGPT Pro subscribers in the EEA, Switzerland, and the UK were excluded from dots' initial rollout, while Business Premium access extended across all currently supported ChatGPT regions. That was the state of things on September 29. Checking OpenAI's own release notes and the best third-party reporting available as of October 22, it's still the state of things now. Nothing in OpenAI's public changelog for October — not the Locked Chats expansion, not the Finances in ChatGPT rollout, not the GPT-Live-1.1 voice update — mentions a change to dots' regional availability for Pro subscribers in those markets.

Why this particular gap has drawn relatively little coverage

It's worth noting how little follow-up reporting this exclusion has generated compared to other dots-related stories. Pricing, the Grokipedia handoff, and Muse's download numbers have all drawn sustained coverage in the weeks since their respective announcements; the EEA/UK/Switzerland gap, reported once at launch by PYMNTS, has not been revisited by comparable outlets in the time since, at least in the sources checked for this piece. That's not evidence the gap doesn't matter — a persistent regional exclusion for one of the largest AI products launched this year is objectively newsworthy — but it may explain why the story reads as "unchanged" rather than "actively developing": there's comparatively little new reporting to develop it with, which puts more weight on OpenAI's own channels being the place any resolution would actually surface first.

What's actually known, and what's assumed

OpenAI has never published a stated reason for the EEA/UK/Switzerland exclusion. The obvious candidate — that an always-on agent with standing access to tools and accounts raises exactly the kind of questions the EU AI Act and UK/Swiss equivalents are built to ask about autonomous systems — is a reasonable inference from the regulatory environment those jurisdictions operate under. It is not something OpenAI has confirmed as the reason. Treating the inference as settled fact would be the kind of unsupported claim this series has tried to avoid throughout; the honest version is narrower: these are the markets where a cautious company would expect to spend longer on compliance work before a self-serve launch, and these are also the markets dots has not yet reached, and OpenAI has not explained the gap beyond the original PYMNTS-reported exclusion.

Why three specific markets, and not others

It's worth noting what links the EEA, UK, and Switzerland together as a group, separate from whether that link explains OpenAI's decision. All three operate under some of the most developed AI-specific and data-protection regulatory regimes in the world, with the EU AI Act in particular creating compliance obligations tied to how autonomous and consequential a system's actions are — exactly the profile a dot fits, given its standing tool access and ability to act without a prompt triggering each step. The UK and Switzerland, while outside the EU AI Act's direct jurisdiction, have both signaled their own AI-specific regulatory approaches and tend to track EU developments closely given the size of cross-border user bases. None of this is confirmation that regulatory exposure is why OpenAI excluded these three markets specifically — OpenAI has never said so — but it is the most coherent explanation available for why these three jurisdictions, rather than some other grouping, would be the ones held back.

Business Premium's different path

The one piece of nuance from launch that's worth restating: Business Premium access was reported as extending across all currently supported ChatGPT regions, which would include the EEA, UK, and Switzerland if those regions are already supported for Business Premium generally. That's a meaningfully different situation than the Pro-tier consumer exclusion — an enterprise product moving through what's presumably a more controlled, admin-gated rollout in markets where the self-serve consumer version is held back. It lines up with the broader pattern of enterprise access to dots moving more slowly and more deliberately than consumer access elsewhere, rather than being a separate story.

Three weeks of silence on a regional exclusion isn't itself evidence of anything sinister. It is evidence that the gap is taking longer to close than a typical feature rollout — which is exactly what you'd expect if the holdup is regulatory rather than technical.

How this compares to the rest of the industry's rollout choices

Meta's Muse and xAI's Grok Bot both launched with their own geographic limitations, though neither has published the kind of explicit regional carve-out PYMNTS reported for dots. That's a difference in how openly each company has described its own rollout boundaries, not necessarily a difference in how cautiously each is actually behaving in those markets — a company can be just as slow-walking a regulated-market rollout without anyone reporting a specific tier-level exclusion the way PYMNTS did for dots' Pro tier. Dots being the one product with a publicly reported exclusion by market and tier may simply reflect that OpenAI's rollout structure made the gap more visible, not that OpenAI is more cautious than its competitors.

What would resolve this

A dated OpenAI announcement — official availability in the EEA, UK, or Switzerland, or an explicit statement of what's being worked through — would settle this cleanly. Absent that, the responsible thing to do with this gap is track it rather than fill it with speculation about EU AI Act classification tiers or specific compliance requirements that haven't been confirmed. The exclusion existed at launch. It still exists three weeks later. That's the whole confirmed story, and it's worth saying plainly rather than dressing it up with regulatory detail nobody at OpenAI has actually put in writing.

The pattern this fits

This is one more entry in the running list of things OpenAI hasn't told dots users three weeks in — pricing, plugin support, and now regional availability all sitting in the same unresolved category. None of these gaps are disqualifying for a product this new. All of them are worth checking back on rather than assuming have quietly resolved.

Part 43 of 47 in the ChatGPT Dots series. Previously: Three Weeks In: What OpenAI Still Hasnt Told Dots Users. Next: Can a Dot Use a Third-Party Plugin Yet? The Unconfirmed Middle Ground. Browse more builder insights or explore AI skills at aiskill.market.