Data Localization in Kazakhstan: Guide to Personal Data Storage Rules

This guide explains where personal data must be stored and processed under Kazakh law, how cross-border transfers fit in, and what changed in 2026. It focuses on commercial operators. For a broader overview of our data protection services, see Data Protection Lawyers in Kazakhstan.

  • Yes, Kazakhstan requires local storage. Article 12(2) of the Law on Personal Data and Its Protection (No. 94-V of 21 May 2013) requires personal data to be stored in a database and/or digital object located in Kazakhstan. There is no exemption by sector, data category or company size.
  • 2026 closed a loophole. Since 25 August 2026, the rule expressly covers “digital objects” (servers, systems, platforms), not just databases. Before that, the old wording referred only to a “database”, which on a literal reading was argued not to reach electronic systems.
  • Localisation and cross-border transfer are separate tests. Moving data abroad can be lawful under Article 16, but it does not cancel the duty to store it in Kazakhstan. Consent to a transfer does not satisfy localisation.
  • The Digital Code did not replace the Personal Data Law. The Digital Code (in force 12 July 2026) adds rights and obligations around the digital environment, but Law 94-V remains the principal statute.
  • Liberalisation is proposed, not confirmed. A draft presidential decree reported in May 2026 would relax storage requirements for most personal data. We could not confirm that it has been adopted, so plan for the current rule.
  • Enforcement is shifting toward administrative fines. The maximum administrative fine reported for a large business is KZT 8,650,000 (about US$19,500), but criminal liability and operational disruption are the bigger risks.

The short answer

Must personal data of people in Kazakhstan be stored in Kazakhstan?

Yes. The statute requires storage by the owner, the operator or a third party “in a database and/or digital object located in the territory of the Republic of Kazakhstan”. The implementing rules go further and speak of a server room or data centre in Kazakhstan.

Does that mean data can never leave the country?

No. Cross-border transfer is regulated separately in Article 16, and several commentators read the law as allowing a copy abroad as long as the primary storage is local. The point is contested, and we cover it in section 5.

Does it apply to foreign companies?

The law applies to anyone collecting and processing personal data of persons in Kazakhstan. Enforcement against entities with no local presence is harder in practice, but regulators have signalled an intention to pursue cross-border enforcement where they can.

How the rule evolved

DateDevelopment
21 May 2013Law No. 94-V on Personal Data and Its Protection adopted
1 January 2016Law No. 419-V of 24 November 2015 introduces the requirement to store personal data in a database located in Kazakhstan (Article 12)
21 October 2020Ministry order No. 395 on rules for collecting and processing personal data, which in places strengthened the localisation approach
12 June 2023Order No. 179 approves the rules on protective measures (clauses 13 and 14 address where restricted-access data is processed and stored)
18 January 2026Article 19-1 on automated processing and the AI Law take effect
12 July 2026Digital Code (Law No. 255-VIII of 9 January 2026) and its companion law No. 256-VIII take effect; protective-measures rules restated by order No. 338
25 August 2026Law No. 326-VIII of 24 June 2026 takes effect: localisation wording extended to digital objects; two new state registers; three-class size classification
May 2026 (draft)Draft decree on the data processing and storage ecosystem circulated, proposing to lift mandatory storage for most personal data (status unconfirmed, see section 9)

What the localisation rule actually requires

The statute

Article 12(2) of Law 94-V, as amended from 25 August 2026, requires storage of personal data in a database and/or digital object located in Kazakhstan. The retention period is set by the date the purposes of collection and processing are achieved, unless legislation says otherwise.

The 2026 amendment defines a “database” (baza) as an ordered set of personal data on paper, and introduces “digital object containing personal data” as the electronic counterpart. The practical effect is that the localisation duty now clearly reaches servers, platforms and cloud systems.

The implementing rules

The rules on protective measures (order No. 179, restated with effect from 12 July 2026) add two requirements that are stricter than the statute:

  • Clause 13: collection and processing of restricted-access personal data must be carried out through digital objects located in Kazakhstan, not merely stored there.
  • Clause 14: storage is in a database located in a server room or data centre in Kazakhstan.

This creates a practical distinction. For publicly available personal data, processing outside Kazakhstan is not prohibited as long as storage is localised. For restricted-access data, the processing itself must stay in the country.

What counts as personal data

The definition is broad: information, or a set of information, about a data subject supplemented by one or more personal data identifiers. It is not limited to customer data. Employee payroll, HR files and attendance records are personal data, so a group-wide HR system hosted abroad can trigger the rule for the Kazakh workforce.

Who is caught

  • Operators and owners of data, whether or not they are incorporated in Kazakhstan.
  • Third parties processing on their behalf, including hosting and software providers, because the duty is addressed to the owner, the operator and the third party together.
  • Multinational groups with central HR, CRM, ERP or customer platforms hosted outside Kazakhstan.
  • Online services and platforms with Kazakh users, particularly where they interact with state digital systems.

A contractual promise by a foreign cloud provider to comply with Kazakh law does not move the server. The test is physical and legal location, not the provider’s assurances.

Businesses in the Astana International Financial Centre (AIFC) operate under AIFC data protection rules, which are closer to GDPR principles. How those rules interact with Law 94-V for a given group structure should be assessed case by case.

Localisation versus cross-border transfer

These are two different legal tests and companies routinely confuse them.

Article 16 on cross-border transfer permits transfer of personal data to states that ensure its protection. For states that do not, transfer is allowed only on limited grounds: the data subject’s consent, a ratified international treaty, specified public-interest statutory grounds, or protection of constitutional rights where consent cannot be obtained. Article 16 has not been amended since 2017 and Kazakhstan has not published a list of states it treats as adequate.

Practical consequence: adequacy of the destination is effectively self-assessed. The most defensible basis is documented consent from the data subject.

But consent does not displace localisation. Obtaining consent to send data abroad satisfies Article 16. It does not relieve you of storing the data in Kazakhstan under Article 12(2).

Can a copy be kept abroad?

Commentators disagree, and the statute does not address it directly:

  • Some law-firm and data-centre sources say the primary database must be in Kazakhstan but a copy or backup abroad is acceptable.
  • At least one regulatory monitor reports commentary that parallel storage in Kazakhstan and abroad would not be permitted.
  • The US Embassy-sourced Investment Climate Statement notes that transfer of certain non-sensitive data is possible if a local copy is stored in Kazakhstan, but that the Digital Code makes this difficult in practice for state and quasi-state users.

A cautious approach is to keep the system of record in Kazakhstan, document the legal basis for any outbound copy, and avoid architectures where the foreign database is the primary one.

Special rules for telecom and website operators

The Communications Law (No. 128-VI) reportedly requires telecommunications operators and website operators to store subscriber and user data in Kazakhstan and prohibits cross-border transfer of that data except for roaming. Companies in these categories should treat the transfer rule as stricter than the general one.

Other laws that push data into the country

Localisation is not only in the Personal Data Law. According to an AmCham issue brief (15 May 2026), several other instruments add to it:

  • Law on Informatization (No. 418-V): entrenches localisation for state, quasi-state and critical information infrastructure. The January 2026 amendments repealed its Article 36 on electronic resources containing personal data, but re-imposed Personal Data Law requirements on a wider range of “digital objects”.
  • Digital Code: requires owners of digital resources to comply with the Personal Data Law (Article 24) and restricts cross-border transfer of certain “digital data products” (Articles 30 and 31).
  • AI Law (No. 230-VIII): Articles 11 and 17 require adherence to personal data protection laws, which brings the localisation clause with them.
  • Draft Online Platforms Bill: would require foreign platforms to open local representative offices, and AmCham flags this as a further tightening.

The US Department of State’s 2026 Investment Climate Statement similarly says the Digital Code effectively imposes localisation that makes transfers difficult and hinders use of international cloud services in the state and quasi-state sector.

Other 2026 changes that sit alongside localisation

These do not change where you store data, but they affect how you operate it:

ChangeEffectiveWhat it means
Register of persons processing personal data (Article 10-1)25 Aug 2026Notification of the start and end of processing for the “large” class; details include database location and whether cross-border transfer occurs
Size classes (Article 25-1)25 Aug 2026Small (up to 10,000 unique subjects), medium (10,000 to 500,000), large (500,000 and above); processing restricted-access data moves you up one class
Breach register (Article 23-2)25 Aug 2026State register of breaches; notification to the authorised body is reported at one working day
Automated processing ban (Article 19-1)18 Jan 2026Automated processing with legal consequences prohibited without consent; objections must be handled within three working days

Because the register notification asks where the database is located, a company’s storage architecture will become visible to the regulator once the filing rules are published. The subordinate rules and filing channel for Article 10-1 had not been confirmed in the sources we reviewed.

Penalties

There is no dedicated administrative offence for breaching localisation. Reporting indicates that a breach of Article 12 is charged as a failure to take protective measures under Article 79 of the Code of Administrative Offences. Using the 2026 monthly calculation index of KZT 4,325, the reported figures for a large business are:

Offence (Article 79)Large business, MCIApprox. KZT
Part 1: unlawful collection or processing200865,000
Part 2: same, using official position6002,595,000
Part 3: failure to take protective measures6002,595,000
Part 4: part 3 act resulting in loss or unlawful processing2,0008,650,000

Criminal liability under Article 147 of the Criminal Code applies where failure to take protective measures causes substantial harm, with sanctions reaching up to two years’ imprisonment for the basic offence and up to seven years for the most serious dissemination offences.

The fine amounts come from a single secondary source that cites the Code and the 2025 amendments raising them. Verify against the current Code text before relying on exact figures.

The larger business risk is not the fine. It is the operational impact of being forced to migrate production systems, or of losing contracts with state and quasi-state customers who read the rules conservatively.

Is liberalisation coming?

In May 2026 the American Chamber of Commerce in Kazakhstan (members include Google, Meta, Microsoft, Apple and Oracle) published an issue brief on a draft presidential decree on the development of data processing and storage infrastructure. According to the brief, the draft would:

  • lift mandatory storage in Kazakhstan for most categories of personal data and allow cross-border transfer to jurisdictions with adequate protection, or where binding corporate rules, standard contractual clauses and recognised security certification are in place;
  • allow special categories of data in the cloud if a Kazakhstan-based entity keeps the encryption keys and control;
  • introduce a Cloud First principle for government data; and
  • relax security obligations for foreign-owned participants of the Data Center Valley project, provided they do not serve users in Kazakhstan.

We could not find confirmation that this decree has been signed or published. The Prime Minister’s office has reported separately that the first 50 MW facility at Data Center Valley in Pavlodar is scheduled to start operating in June 2027, and that a “Cloud First (Data Embassy)” concept for hosting foreign states’ data is being prepared. AmCham itself notes that implementing the decree would require amendments to several laws and bylaws.

Our advice: treat the draft as a signal of direction, not as law. Do not design architecture around a relaxation that has not been enacted.

Architecture options and how they score

OptionLikely compliant?Notes
Primary database in a Kazakh data centre (colocation or local cloud)YesThe safest approach; document the physical location
Regional hyperscaler cloud with a Kazakhstan region or point of presence hosting the Kazakh data segmentGenerally yes, if the data actually resides in KazakhstanConfirm where the data is stored, not just where the interface is served from
Kazakh primary plus foreign replica or analytics copyDefensible but contestedDocument legal basis for transfer (consent) and keep the system of record local
Foreign primary plus Kazakh backupLikely not compliantCommentators say the primary must be in Kazakhstan
Regional hub elsewhere in Central Asia or EuropeNot compliantA regional hub does not satisfy the rule
Fully offshore with consent to transferNot compliantConsent addresses Article 16, not Article 12

A practical compliance roadmap

  1. Inventory every system that holds personal data of people in Kazakhstan: customers, employees, applicants, contractors.
  2. Map where each system physically stores and processes data, including SaaS vendors and sub-processors.
  3. Classify the data into publicly available and restricted-access, since processing location rules differ.
  4. Count unique data subjects (not records) to determine your Article 25-1 class.
  5. Decide the architecture using the options above and plan migration as a project, since moving a production database typically takes months.
  6. Fix the transfer basis for any data that leaves the country, and record it.
  7. Update vendor contracts to require storage in Kazakhstan and prohibit transfers without your approval.
  8. Appoint the responsible person for personal data processing and keep the order current.
  9. Prepare for the Article 10-1 notification if you are in the large class, and watch for the subordinate rules.
  10. Review incident response for a one-working-day notification clock.
  11. Keep evidence: server location confirmations, data-flow diagrams and the counting methodology.

Common mistakes

  • Assuming the Digital Code replaced Law 94-V. It did not; localisation, consent and transfer rules remain in the Personal Data Law.
  • Treating consent to transfer as a substitute for localisation. They are independent requirements.
  • Relying on a regional data hub or on a provider’s contractual assurance.
  • Forgetting employee and HR data. The rule is not limited to consumer data.
  • Counting records instead of unique subjects when determining the size class.
  • Building around the draft decree before it is enacted.
  • Underestimating migration time and cost. The remedy for a localisation breach is infrastructure, not paperwork.

Frequently asked questions

Does Kazakhstan require data localisation?

Yes. Article 12(2) of Law 94-V requires storage of personal data in a database and/or digital object located in Kazakhstan.

Can I use AWS, Azure or Google Cloud?

Only if the personal data of persons in Kazakhstan is actually stored in Kazakhstan. A provider’s nearest regional hub is not enough.

Can I transfer personal data abroad?

Yes, subject to Article 16, but this does not remove the duty to store the data in Kazakhstan. Consent of the data subject is the most reliable transfer basis because Kazakhstan publishes no list of adequate countries.

Is a backup abroad allowed?

The law does not address this directly. Some commentators accept a copy abroad if the primary database is local; others take a stricter view. Seek advice before relying on it.

Does the rule apply to employee data?

Yes. HR and payroll records are personal data.

What is the penalty for non-compliance?

Reported administrative fines reach KZT 8,650,000 for a large business under Article 79, Part 4, plus potential criminal liability where substantial harm is caused.

Will the rule be relaxed?

A draft decree proposes it, but we could not confirm adoption. Plan for the current rule.

Do I need to register with a regulator?

From 25 August 2026, businesses in the large class (500,000 or more unique data subjects, or one class up where restricted-access data is processed) must notify the start of processing for entry in a state register. Filing rules had not been confirmed in the sources we reviewed.

Syuzanna Li

Syuzanna Li

Partner (Central Asia Desk)

Syuzanna heads the Astana and Tashkent offices. She has advised financial investors and corporate clients on a wide range of matters, including M&A, joint ventures, restructuring. Syuzanna has also particular experience in the energy sector.

View LinkedIn Profile
Other blog posts
Cryptocurrency License in Kazakhstan: Requirements, Costs and the Application Process

Read Article

Read Article

Corporate Tax Rate in Kazakhstan : Rates, Deductions, Filing and Incentives

Read Article

Read Article

Company Registration in Kazakhstan for Foreign Investors

Read Article

Read Article

Section 55 of the Companies Act, 2013 Explained: Issue and Redemption of Preference Shares

Read Article

Read Article

Stay Ahead in Cross-Border Law

Concise updates on India, China, Russia & Central Asia — regulatory shifts, deal trends, and compliance alerts. No spam, unsubscribe anytime.