Note

Consent to the collection and processing of personal data

In Kazakhstan consent is the main ground for processing, not one of many. This note covers the form of consent, its required content, when separate consent is needed, how the state and non-state services work, how consent is withdrawn, and why proving consent is harder than it seems.

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

ConsentData subject rightsKazakhstan and the GDPRProcessing without consent

Provisions discussed

In short

Personal data are collected and processed with the consent of the data subject or their legal representative. The exceptions are the cases in Article 9 and further use of published data under Article 7(5) (Art. 7(1)). The Digital Code repeats this rule (Art. 37(3)). Consent is given in writing, through the state or a non-state service, or in another way that allows confirmation that it was obtained (Art. 8(1)). It can be withdrawn at any time. The operator must stop processing within 15 working days unless the law requires processing to continue (Art. 8(7)).

  • General rule — in writing, through the state service, a non-state service, or in another way that allows confirmation that consent was obtained (Art. 8(1); Collection Rules, para 6).
  • Data in state digital objects — consent only through the state service (Art. 8(1)). An operator that interacts with such objects must integrate its systems with the state service, save for certain Article 9 cases (Art. 8-1(1)). The service handles giving and withdrawing consent, notifying the subject of actions with their data and showing who holds their consent (Art. 8-1(2)). The subject receives the request and responds via the 1414 SMS gateway or e-government (State Service Rules, para 3).
  • Non-state service — optional for the operator where there is no interaction with state objects. It is used to give consent and to receive notifications of actions with the data and of third-party access (Art. 8-2).

The Digital Code adds a general standard: relations in the digital environment rest on “the free, informed and expressed will of the person” (Art. 5(2)).

The Law lists the mandatory content (Art. 8(4)):

  1. name and BIN (IIN) of the owner and/or operator;
  2. full name of the data subject;
  3. the term or period of the consent;
  4. whether the owner or operator may transfer the data to third parties;
  5. whether cross-border transfer takes place;
  6. whether the data may be disseminated in public sources;
  7. the list of data collected;
  8. other information at the owner’s or operator’s discretion.

The consent may not last longer than needed to achieve the purposes, unless a law or contract provides otherwise (Art. 8(5)). If no term is stated, the consent is valid until the purposes of processing are achieved (Art. 8(6)).

The Law requires consent — separately or expressly stated in the consent — for:

  • dissemination in public sources (Art. 7(3));
  • transfer to third parties, cross-border transfer (except in the cases of Article 16) and dissemination in public sources (Art. 7(6); Collection Rules, para 4-5);
  • dissemination beyond the stated purposes (Art. 15(2));
  • biometric identification in public places, except to protect the constitutional order, public order, rights, health and morals (Art. 7(12)).

The data subject may withdraw consent to collection, processing, dissemination in public sources, transfer to third parties and cross-border transfer (Art. 24(1)(5)). Notifying the owner, operator or third party is enough. Within 15 working days they must stop processing, unless storage or processing is required by law, or give a reasoned refusal (Art. 8(7); Collection Rules, para 6-3).

Consent cannot be withdrawn where this would contradict the law or where there is an unfulfilled obligation (Art. 8(2)).

Interpretation. The “unfulfilled obligation” exception is broad: an outstanding loan or an incomplete delivery would qualify. It allows processing needed to perform the obligation to continue. But it presumably does not allow using the data for other purposes, such as marketing.

The owner and operator must provide proof that consent was obtained (Art. 25(2)(5)). Yet the Retention Schedule sets a retention period of 1 year for employees’ consent forms (item 467).

Interpretation. If an employee’s consent form is kept for only a year, there will be nothing to prove consent with by the end of an employment that may last decades. It is more sensible to keep consent for the whole processing period plus the limitation period, treating the one-year term as a minimum.

Comparison with the GDPR

QuestionKazakhstanGDPR
Role of consentThe main ground; without consent only under Art. 9One of six grounds (Art. 6(1))
FormIn writing, via a service, or another verifiable wayAny clear form, but the controller must be able to prove consent (Art. 7(1))
ContentClosed list of 8 items (Art. 8(4))Specific, informed, unambiguous (Art. 4(11))
WithdrawalStop processing within 15 working days; exceptions applyAt any time, as easily as given (Art. 7(3))
Freely givenNo express ban on bundling consentConsent must not be a condition of a contract unless necessary (Art. 7(4))
ChildrenThrough the legal representative; no age setFor online services from 16; Member States may lower to 13 (Art. 8)

Interpretation. Since Kazakhstan has almost no other grounds, consent is collected for nearly everything, including performance of contracts. Under the GDPR that approach would be considered a mistake; in Kazakhstan it is often the only option.

Open questions

Open question: freely given consent of employees. Employees depend on their employer. Is their consent free, and what happens if an employee refuses? The Labour Code provides no separate ground for processing employee data.

Open question: age. From what age can a child give consent alone, for example in an online service? The Law speaks only of the legal representative.

Open question: “another way that allows confirmation”. Is a tick box on a website or a button in an app enough? The Law does not say, and the burden of proof lies with the operator.

Still to research

  • Rules on the operation of non-state services and requirements for them.
  • Regulator guidance on the form of electronic consent.
  • Inspection practice under item 1 of the inspection checklist (collection and processing with 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 legislation144/НҚKazakhstan

Rules on the operation of the state access control service for personal data (Order No. 144/NK of 29 April 2022) (opens in a new tab)

How the state service for consent to access data in state digital objects works: requests answered via the 1414 SMS gateway or e-government, withdrawal, a list of who holds consent, and notifications of actions with the data (para 3).

Key provisions
paras 2 (opens in a new tab)–4 (opens in a new tab)

● Checked 26 October 2026in forceConsentData subject rights

Code255-VIIIKazakhstan

Digital Code of the Republic of Kazakhstan (opens in a new tab)

The new code on the digital environment. Key for data protection: the concept of a "digital object" (Art. 20), now used in the Personal Data Law, and the right to erasure, anonymisation and restriction (Art. 41). In force six months after publication on 10 January 2026.

Key provisions
Art. 20 (opens in a new tab), Art. 41 (opens in a new tab), Art. 106 (opens in a new tab)

● Checked 26 October 2026in forceData subject rightsDeletion and anonymisationScope and key terms

Secondary legislation279-НҚKazakhstan

List of standard documents of state and non-state organisations with retention periods (Order No. 279-NK of 17 June 2025) (opens in a new tab)

Retention periods for standard documents of any organisation. For HR: internal personal data policies — permanently; employment contracts and personnel files — 75 years; documents of rejected applicants — until no longer needed; employees' consent forms — 1 year.

Key provisions
items 460–467

● Checked 26 October 2026in forcePurpose, scope and retentionEmployment

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