Where customer data sits — in Uzbekistan, in Russia or in the EU — is decided not by speed but by law, regulator access and who you turn to in an incident. Storing in Russia or the EU adds regulatory risk and gives you no residency in Uzbekistan.
How storing data in Uzbekistan, Russia and the EU differs
The difference is not “where the server physically stands” but three things at once: whose law the data falls under, who can get access to it, and whether it satisfies the localisation requirement in Uzbekistan. Below is a comparison on the key criteria.
| Criterion | Uzbekistan | Russia | EU |
|---|---|---|---|
| ZRU-547 localisation (biometrics, voice) | Satisfied — data in country | Not satisfied | Not satisfied |
| Jurisdiction and state access | Uzbekistan | Russia | EU (GDPR) |
| Latency for users in Uzbekistan | Minimal | Higher | Highest |
| On-prem / private cloud for a CIS bank | Available | Usually not | Usually not |
| Who it usually suits | Business and banks in Uzbekistan | Companies with Russian operations | Companies with EU customers |
Classic cloud CRMs and foreign SaaS platforms, by their own published data-residency policies, keep data in EU, US or Russian data centres — and offer neither residency in Uzbekistan nor on-prem for a bank. That is a structural limitation of the platform, not a setting in the admin panel.
What a business in Uzbekistan should choose
For a company whose customers and regulator are in Uzbekistan the baseline answer is one: store the data in the country. It is the shortest path to compliance and the strongest argument with banks and large corporate customers.
- CIS banks and regulated companies — in-country storage plus on-prem only, regardless of how the law is relaxed.
- Businesses that record calls — recordings may contain voice biometrics, which is a mandatory-localisation category under ZRU-547.
- SMBs without biometrics — other data (name, phone number, orders) may lawfully be stored abroad with adequate protection, but residency still lowers risk and simplifies inspections.
Why Russian and EU jurisdiction is a risk
When data sits in Russia or the EU it falls under someone else’s law and someone else’s access mechanisms. For an Uzbek business that means: the ZRU-547 localisation requirement is not satisfied, cross-border transfer needs a separate basis (adequacy, SCCs or ISO 27001 / 27701), and subscriber data, biometrics and voice should not leave the country at all. On top of that comes technical latency — a server in Europe answers a user in Tashkent noticeably more slowly.
Where CRM data physically sits and what residency means is covered in detail in “Where your CRM data is stored”.
How Zukko.AI handles it
Zukko.AI stores data belonging to customers in Uzbekistan in the country, and on-prem / private cloud is available for CIS banks and regulated companies. Encryption is AES-256 at rest and TLS 1.3 in transit (the enterprise industry standard), with role-based access control (RBAC) and an audit trail. This is support for ZRU-547 compliance, not a legal guarantee — a legal assessment for your business is your lawyer’s job. How it works is set out on the Security page and under AI-CRM.
An honest word on certifications: we claim none — instead we name the controls in force: encryption, role-based access, an audit trail and deployment inside the customer’s perimeter. Launch for an SMB takes from 2 hours; for an enterprise environment with on-prem, up to 30 days.
What the business gets
- ZRU-547 compliance — biometrics and voice stay in the country.
- Less legal risk — the data sits under Uzbek jurisdiction, with no cross-border complications.
- An argument with banks — the first question at a security review is where the data physically sits.
- A faster response — minimal latency for users in Uzbekistan.
If the business records and analyses conversations, voice is added to the data perimeter — how that works is described under Call analysis. The full data-protection picture is in the CRM security guide.
Frequently asked questions
Where is it better for a business from Uzbekistan to store data?
In Uzbekistan: it satisfies the ZRU-547 localisation requirement for biometrics and voice, removes the risk of a foreign jurisdiction and makes on-prem for a bank possible.
Can data be stored in Russia or the EU?
Some data (name, phone number, orders) may be stored abroad with adequate protection, SCCs or ISO 27001 / 27701. But biometrics, genetic data and telecom subscriber data must stay in the country under ZRU-547.
Why are foreign CRMs unsuitable for banks?
They keep data in the EU, the US or Russia and usually offer neither residency in Uzbekistan nor on-prem — and CIS banks need both.
Does server location affect speed?
Yes — a server in Uzbekistan answers a user in Tashkent noticeably faster than a data centre in the EU.
Does Zukko.AI store data in Uzbekistan?
Yes — data belonging to customers in Uzbekistan is stored in the country; on-prem / private cloud is available for CIS banks.