A voice channel into the state's registries
On July 15, 2026, Ukraine's Ministry of Digital Transformation switched on voice mode for Diia.AI, the chat assistant embedded in the Diia portal that already serves the country's 24-million-plus digital-ID users across 170-plus government services. Instead of typing, a citizen can now ask the assistant to explain a service, check their sole-proprietorship (FOP) status, verify insurance tenure, or order an income certificate — and hear the answer read back, according to Minfin's coverage of the launch. Ukrainian GovTech firm Kitsoft built the voice interface and permission workflow on top of the assistant it had already engineered on its Liquio platform; the underlying speech technology comes from ElevenLabs, the US voice-AI startup that Deputy Prime Minister Mykhailo Fedorov brought on as a partner at the WINWIN Summit, alongside plans to extend the same voice stack into the Mriia and Diia.Education platforms, per the Ministry's official announcement.
The case for building it this way
The accessibility argument here is genuinely strong, not a talking point. Ukraine has an aging population, a large cohort of soldiers with injuries that make typing difficult, and users with low digital literacy in rural areas — for all of them, a device that can be spoken to rather than typed into is a real reduction in friction, not a novelty. Building that capability in-house, from scratch, with production-grade multilingual voice models would have taken Ukraine's digital ministry years it doesn't have while fighting a war and running a state simultaneously. Partnering with a specialist vendor that already serves this exact use case elsewhere was the fast, competent path, and Fedorov has been explicit that the ambition is a full "agentic state" where interacting with government is as casual as a voice message — a goal that requires this kind of infrastructure now, not a homegrown alternative in 2029.
Where the argument gets harder
But the accessibility case doesn't answer the governance question, and that question is specific: a foreign commercial vendor is now an intermediary in the pipeline between a citizen's voice and their tax, insurance, and identity records inside a national digital-ID system. Voice is not like a typed query — it is biometric-adjacent data, and regulators in the EU and UK already treat voiceprints as special-category information requiring a distinct lawful basis to process. ElevenLabs' own enterprise documentation shows the company understands this: it advertises regional data-residency options across the US, EU, and India, plus an optional Zero Retention Mode that discards audio after processing. None of the launch materials from Kyiv or ElevenLabs specify which of those configurations, if any, apply to the Diia integration — not the announcement, not the ministry's own AI-news page, not the trade coverage. That is the gap: the accessibility win is documented in detail; the data-handling terms are not documented at all.
The law that hasn't caught up
That gap would matter less if Ukraine's data protection statute were current. It isn't. The country is still operating under its original 2010 personal data law, more than a decade before Ukraine's constitution committed it to EU accession and GDPR-equivalence. The replacement, draft law No. 8153 "On Personal Data Protection," passed only its first reading in the Verkhovna Rada on November 20, 2024, and by mid-2026 is still being reworked for a second reading, per Ukrainian outlet Glavcom's reporting on the bill, which also notes the fights already underway over the bill's fine structure (up to ₴150 million, roughly 8% of annual revenue, for corporate violators) and its vague definition of personal data. In other words, Ukraine is deploying voice-biometric processing through a foreign vendor into its flagship digital-identity platform at the exact moment its own rulebook for what counts as protected data, and what a company must do with it, is still being drafted.
The proportionate fix, not a ban
None of this argues for slowing down Diia.AI's voice rollout, let alone banning foreign vendors from government infrastructure — that would sacrifice a real accessibility gain to a hypothetical harm, and Ukraine's wartime context makes speed a legitimate value in itself. The proportionate response is disclosure, not prohibition: the ministry should publish which ElevenLabs data-residency and retention settings govern the Diia deployment, the same way it publishes the assistant's service list, and the Rada should treat finishing bill 8153's second reading as infrastructure work that keeps pace with infrastructure like this, rather than a separate legislative track. A government that is building an "agentic state" ahead of its own data law isn't necessarily building it badly — but it should be able to say, in one sentence, where a citizen's voice recording of their tax status actually goes.