Note

Cross-border transfers of personal data

When personal data may be sent abroad: Article 16 of the Law, how it interacts with the consent requirement in Article 7, sector-specific bans, and why the absence of a list of "safe" countries leaves much unclear.

Law stated as of
how it is checked
Updated
18 October 2026

Cross-border transfersKazakhstan and the GDPRData localisationTelecommunications

Provisions discussed

In short

A cross-border transfer is the transfer of personal data to the territory of foreign states (Art. 16(1)). The Law splits countries into two groups. Data may be transferred to countries that “ensure the protection of personal data” (Art. 16(2)). Transfers to other countries require one of the listed grounds, above all the data subject’s consent (Art. 16(3)). Separately, the Law states that cross-border transfer, “except in the cases provided for by Article 16”, takes place subject to the data subject’s consent (Art. 7(6)).

No official list of countries that ensure protection could be found in the Law or in secondary legislation. In practice, consent therefore remains the main ground.

What the Law says

Article 16 is structured as follows:

  1. Definition — transfer to the territory of foreign states (Art. 16(1)).
  2. Countries that ensure protection — transfers are permitted (Art. 16(2)).
  3. Other countries — transfers are possible with the consent of the data subject or their legal representative; in cases provided for by ratified international treaties; in cases provided for by laws where necessary to protect the constitutional order, public order, rights and freedoms, health and morals; or to protect constitutional rights and freedoms where consent cannot be obtained (Art. 16(3)).
  4. Bans and restrictions may be set by laws (Art. 16(4)).
  5. Subscriber service information in telecommunications is governed by the Communications Law (Art. 16(5)).

The consent rules work alongside this. The consent must state whether cross-border transfer takes place (Art. 8(4)(5)). The data subject may withdraw consent, including consent to cross-border transfer (Art. 24(1)(5)). The Collection and Processing Rules repeat Article 7(6) word for word (para 4-5). From 25 August 2026, information on cross-border transfers is also part of the notification to the regulator before processing starts (Art. 10-1(3)(5)).

Interpretation. Article 7(6) can be read in two ways. First reading: consent is needed for any cross-border transfer, except the cases in Article 16(3)(2)–(4), where the Law itself provides a ground without consent. Second reading: a transfer to a country that ensures protection (Article 16(2)) is also “a case provided for by Article 16”, so no consent is needed. The second reading fits the two-group logic better; the first is more cautious. As long as there is no list of countries, the difference is largely theoretical.

No list of “safe” countries

The Law does not say who determines the countries that ensure protection or by what criteria. Approving such a list is not among the regulator’s powers (Art. 27-1).

A common external benchmark is participation in Council of Europe Convention 108. Kazakhstan itself is not a party: as of 18 October 2026 it does not appear in the chart of ratifications. So the Convention cannot serve as a standard shared with the recipient country either.

Interpretation. Without a list, the company decides on its own whether the recipient country “ensures protection” and bears the risk of getting it wrong. Hence the widespread practice of always obtaining consent to cross-border transfer, even where the company believes the country does ensure protection.

Sector-specific bans

An example of a restriction under Article 16(4) is subscriber service information in telecommunications. Telecom operators store it in Kazakhstan; transferring it abroad is prohibited, except when providing services to Kazakhstan subscribers who are abroad (Communications Law, Art. 15). From 25 August 2026 the law lists what this information is: phone numbers, device identifiers, the subscriber’s IIN or BIN, billing data, device location, network addresses and more (Art. 23-1).

There is also a technical rule for restricted-access data: storage and transmission require cryptographic tools of at least security level 3 under ST RK 1073-2007, but this does not apply to cross-border transfers under Article 16 (Protection Rules, para 15(9)).

A transfer abroad does not lift the requirement to store data in Kazakhstan (Art. 12(2)). These are two parallel regimes: data must be stored in a database or digital object in Kazakhstan, and sending them abroad is assessed separately under Article 16. See the note “Personal data localisation in Kazakhstan”.

Comparison with the GDPR

QuestionKazakhstanGDPR
What counts as a transferTransfer to the territory of foreign states (Art. 16(1))Disclosure to an importer in a third country; criteria in Guidelines 05/2021
Countries with adequate protectionThe concept exists; no list or procedureCommission adequacy decisions (Art. 45)
Contractual mechanismsNoneStandard contractual clauses, binding corporate rules (Arts 46–47)
ConsentThe main practical toolOnly a derogation for specific situations; must be explicit (Art. 49)
In-country storageMandatory (Art. 12)Not required

Interpretation. Under the GDPR consent is a fallback, and the basis is an assessment of protection plus contractual safeguards. In Kazakhstan it is the other way round: with no list of countries and no contractual mechanisms, consent becomes the main ground. For a company used to SCCs, this means extra work on consent wording.

Open questions

Open question: who decides which countries ensure protection? Neither the Law nor secondary legislation names an authority or criteria. No official regulator guidance on this has been found so far.

Open question: remote access. If data are stored in Kazakhstan and an employee or contractor views them from abroad, is that a “transfer to the territory of a foreign state”? The definition in Article 16(1) does not answer this.

Open question: cloud and AI services. Sending a query containing personal data to a foreign API looks like a cross-border transfer even if the main database is in Kazakhstan. Practitioners take this view too (for example, the SOLIS Partners article), but there is no official guidance.

Open question: withdrawal of consent. The data subject may withdraw consent to cross-border transfer (Art. 24(1)(5)). The Law does not say what happens to data already transferred abroad.

Still to research

  • Regulator guidance on countries that ensure protection and on the form of consent to cross-border transfer.
  • Kazakhstan’s international treaties providing for transfers of personal data (Art. 16(3)(2)), for example within the EAEU and the CIS.
  • Sector-specific restrictions: banking secrecy, medical data.
  • Inspection and enforcement practice on cross-border transfers without consent.

All quotations of Kazakhstan legislation are unofficial translations from the Russian text published on Adilet.

Materials

Statute94-VKazakhstan

Law of the Republic of Kazakhstan "On Personal Data and Their Protection" (opens in a new tab)

The core statute: definitions, scope, the in-country storage rule (Art. 12) and cross-border transfers (Art. 16). Notification of processing (Art. 10-1) and operator size categories (Art. 25-1) apply from 25 August 2026.

Key provisions
Art. 1 (opens in a new tab), Art. 3 (opens in a new tab), Art. 10-1 (opens in a new tab), Art. 12 (opens in a new tab), Art. 16 (opens in a new tab), Art. 25-1 (opens in a new tab), Art. 29 (opens in a new tab)

● Checked 26 October 2026in forceAutomated processing and AIBreaches and notificationsConsentCross-border transfersTypes of personal dataData subject rightsDeletion and anonymisationDisclosure to third partiesLiabilityData localisationNotification and register of operatorsProcessing principlesProcessing without consentPurpose, scope and retentionRegulator and state supervisionResponsible person and internal policiesScope and key termsTelecommunicationsSecurity measures

Secondary legislation395/НҚKazakhstan

Rules on the collection and processing of personal data (Order No. 395/NK of 21 October 2020) (opens in a new tab)

Detailed rules on collection and processing: consent for public dissemination, disclosure and cross-border transfer (para 4-5), a three-working-day deadline to answer data subjects (para 16), irreversible de-identification (paras 20–21), blocking and deletion (para 25).

Key provisions
paras 4 (opens in a new tab)–4-5 (opens in a new tab), para 6-3 (opens in a new tab), para 11 (opens in a new tab), para 16 (opens in a new tab), paras 17 (opens in a new tab)–18 (opens in a new tab), paras 20 (opens in a new tab)–21 (opens in a new tab), para 25 (opens in a new tab)

● Checked 26 October 2026in forceConsentCross-border transfersData subject rightsDeletion and anonymisationDisclosure to third partiesPurpose, scope and retention

Secondary legislation179/НҚKazakhstan

Rules on personal data protection measures for owners, operators and third parties (Order No. 179/NK of 12 June 2023) (opens in a new tab)

The main secondary act on protection measures, restated in September 2026: notification, operator size categories and tiered measures, restricted-access data (incl. cryptography), local collection and storage in a server room or data centre in Kazakhstan, the responsible person, and breach notification within one working day.

Key provisions
paras 3 (opens in a new tab)–7 (opens in a new tab), paras 8 (opens in a new tab)–14 (opens in a new tab), para 15 (opens in a new tab), para 16 (opens in a new tab), para 18 (opens in a new tab), paras 19 (opens in a new tab)–20 (opens in a new tab), para 23 (opens in a new tab)
In force from
21 September 2026

● Checked 26 October 2026in forceBreaches and notificationsTypes of personal dataData localisationNotification and register of operatorsResponsible person and internal policiesSecurity measures

Statute567-IIKazakhstan

Law of the Republic of Kazakhstan "On Communications" (opens in a new tab)

Special regime for subscriber service information (numbers, device IDs, billing, location, IP addresses, Art. 23-1): it must be stored in Kazakhstan and may not be transferred abroad except to serve Kazakhstan subscribers roaming abroad (Art. 15(1)(2)).

Key provisions
Art. 15 (opens in a new tab), Art. 23-1 (opens in a new tab)

● Checked 26 October 2026in forceCross-border transfersData localisationTelecommunications

International instrumentETS 108International

Council of Europe Convention for the Protection of Individuals with regard to Automatic Processing of Personal Data (ETS No. 108) — chart of signatures and ratifications (opens in a new tab)

The only binding international treaty on data protection, open to non-member states. As of 18 October 2026 Kazakhstan is not a party, which matters when assessing which countries "ensure protection" for transfers.

● Checked 18 October 2026Cross-border transfers

EU law2016/679EU

Regulation (EU) 2016/679 (General Data Protection Regulation) (opens in a new tab)

Used for comparison. The GDPR has no general localisation duty: data move freely within the EU (Art. 1(3)), and exports outside the EEA are governed by Chapter V, with the transfer conditions in Arts 44–49.

Key provisions
Art. 1(3), Art. 44–49

● Checked 26 October 2026in forceCross-border transfersKazakhstan and the GDPRData localisation

ArticleKazakhstan

Ch. Oralbayev (SOLIS Partners). SaaS and foreign AI models: where to store data under Kazakhstan's personal data law (opens in a new tab)

A practical piece on localisation after the 2026 amendments. Distinguishes storage (Art. 12) from transfer (Art. 16) and argues, citing a 6 May 2024 regulator letter, that parallel storage abroad is acceptable if the primary database stays in Kazakhstan.

Cross-border transfersData localisation