Personal data storage in Kazakhstan: servers, CRM, messengers and the 2026 amendments
Where customer data really lives: website, CRM, WhatsApp, analytics, e-mail. What Kazakhstan Law No. 94-V requires on local storage and what the 2026 law changed.

When people talk about personal data on a website, they usually think of the lead form and the consent checkbox. That is only the entrance. After that the lead lives a life of its own: it lands in an inbox and in the CRM, a manager carries on the conversation in WhatsApp, an analytics tag remembers the visit, the accountant exports the customer list to Excel, and at night all of it is copied into a backup. Under the law, each of these copies is storage of personal data, and each has a physical address: a server in a particular country.
This article looks at where customer data actually lives in a typical company, what Kazakhstan's Law No. 94-V "On Personal Data and Their Protection" says about storage, what the 2026 amendments changed and what to check in your own setup. It is also written for foreign companies selling in Kazakhstan, which often run their tools from abroad. How to build the form and the consent text is covered separately in our guide to personal data on a website. We read the provisions on adilet.zan.kz on 16 November 2026.
What the law says about storage
The core rule is short. The owner, the operator and any third party store personal data in a database and/or digital object located on the territory of the Republic of Kazakhstan (Article 12(2)). The storage period is set by the date on which the purposes of collection and processing are achieved, unless Kazakh law provides otherwise.
Three practical conclusions follow.
- The database you work from has to sit in Kazakhstan. Not "somewhere in the cloud", but with a hosting provider or in a data centre inside the country. This also applies to a contractor processing data on your behalf: the law names the third party alongside the owner and the operator.
- Storage is not forever. Once the purpose is achieved, for example the deal is closed and obligations are fulfilled, the data should be deleted, unless another law requires keeping it longer.
- The data must be protected the whole time. Protection duties start at collection and last until the data is destroyed, deleted, anonymised or depersonalised (Article 22(2)).
The law deals with transfers abroad separately. Cross-border transfer means transferring personal data to the territory of foreign states (Article 16(1)). It is allowed to states that ensure the protection of personal data. To states that do not, it is possible only in the cases listed in Article 16(3), the first of which is the data subject's consent. So a foreign service in the chain is not automatically forbidden, but it has to be named honestly in the consent text, and the primary database still stays in Kazakhstan.
For a foreign company this usually means a split: the working database for customers in Kazakhstan is hosted in Kazakhstan, and whatever goes to group systems abroad is a cross-border transfer covered by consent. How exactly the rules apply to your corporate structure is a question for a local lawyer.
Where customer data actually lives
Start with a simple exercise: follow one lead from the form to the archive and write down every stop. There are usually more stops than you expect.
Website and lead database
The form sends the lead to the website database. Where that database sits is decided by the hosting: a server in Kazakhstan, in a neighbouring country or in a large provider's cloud. If the site runs on a website builder, the leads are stored by the builder, and you need to ask the builder where. This is the first point to check and the easiest one to fix: leads are written to a database on a server in Kazakhstan, and only a notification goes out.
Many sites duplicate each lead by e-mail. A message with a name and a phone number sits in a mailbox, which means on the mail provider's servers. If the mail service is foreign, a copy of the lead is already abroad. The fix is simple: the e-mail says only "new lead received" with a link to the admin panel, and the data itself stays in the database.
CRM
Customer data lives longest in the CRM: contacts, deal history, conversations, amounts. With a cloud CRM, the storage location depends on the vendor and the plan. Do not rely on guesses or third-party articles: ask the vendor where your database physically sits and whether you can choose the data centre. An on-premise or custom CRM is installed on your server or with a hosting provider in Kazakhstan. How to choose a CRM with this in mind is covered in CRM for business in Kazakhstan, and when it is time to move to your own system, in when an off-the-shelf CRM is not enough.
WhatsApp and Telegram
Conversations with customers, their numbers and names are stored on the messenger's servers and on employees' phones. A bot on the WhatsApp Business API works through a provider: data passes through the provider's services and Meta's services. Ask the provider where it is stored and which countries it goes to, and state this in the consent text. Your own part, meaning the order history and the customer record, is best kept in your own database in Kazakhstan, not only in the chat.
Analytics and advertising
Visitor counters and advertising pixels collect data about the visitor's device and behaviour and send it to their companies' servers. These are almost always foreign services. We switch such tags on only after a separate consent in the cookie banner, not with the same checkbox as the lead form. This is practice rather than a literal requirement of the law, but it settles the cross-border transfer question.
Spreadsheets, phones and backups
A customer export in Excel on a cloud drive, a contact list on a manager's personal phone, a database backup in a foreign cloud: all of these are copies of personal data. Backups are the ones most often forgotten, even though they hold the entire database. Check where your hosting provider or contractor writes the backups.
What changed in 2026
Law No. 326-VIII of 24 June 2026 (text on adilet.zan.kz) added several new articles to the personal data law. It was published on 25 June 2026, and its personal data provisions enter into force sixty calendar days after the first official publication. The main points for business are below.
Operators are divided into small, medium and large
New Article 25-1 classifies owners, operators and third parties by data volume. Small ones process data of no more than ten thousand unique subjects, medium ones from ten thousand to five hundred thousand, large ones five hundred thousand or more. What counts is the total number of unique people across one or several digital objects: the website, the CRM and the app add up. If you process personal data with restricted access, your category goes up by one level. Protection measures for each category are set by the authorized body.
Notification before starting and stopping processing
New Article 10-1 requires notifying the authorized body before processing starts and before it stops. Small and medium operators may process data without notification (paragraph 2). The notification states, among other things, the protection measures, transfers to third parties, cross-border transfers, the list of data and the location of the database (paragraph 3). Even if you do not have to notify, this list is a good self-check: if you cannot say where your database sits, that is your first task.
A register of security breaches
New Article 23-2: the authorized body keeps a register of personal data security breaches based on information from public sources and from cybersecurity centres. A leak can be found without you reporting it.
A breach: one working day to report
The law requires notifying the authorized body within one working day from the moment a personal data security breach is detected, with the contact details of the person responsible for organising processing, if there is one (Article 25(2)(8)). One working day is too short to decide for the first time who handles this. So the plan is needed in advance: who spots the incident, who decides it is a breach, who reports it and through which channel, and where the responsible person's contacts are kept.
The same article lists the other duties of the owner and the operator (Article 25(2)): approve the list of personal data and the documents setting out the processing policy, take legal, organisational and technical protection measures, provide proof that consent was obtained, and destroy data once the purpose is achieved. A legal entity appoints a person responsible for organising the processing of personal data (subparagraph 10).
Data has to be deleted when the storage period expires, when the relationship with the subject ends, under a court decision and when collection without consent is discovered, except for the cases in Article 7(5) and Article 9 (Article 18). Deletion has to reach every copy: the CRM, the mailbox, the spreadsheets and the backups.
What to check in your own setup
- Data map. A list of every place that holds customer data: website, e-mail, CRM, messengers, analytics, spreadsheets, phones, backups.
- The address of each copy. For each place: which country the server is in. Where you do not know, ask the vendor in writing.
- Primary database in Kazakhstan. The database you work from sits on a server in Kazakhstan, not only with a foreign service.
- Honest consent. Every foreign service and every contractor on the map is named in the consent text. How to write it is covered in the personal data guide.
- Retention and deletion. The storage period is written down, there is a deletion procedure, and it reaches every copy.
- Your category. Count unique customers across all systems and check whether you need to notify under Article 10-1.
- Breach plan. A responsible person is appointed, their contacts are known, and the one-working-day reporting procedure is written down.
- Access. Which employees see the database and exports, and how access is revoked when someone leaves.
If you are just starting to sell online, it is easier to build this in from day one than to redo it later: the launch steps are covered in how to open an online store in Kazakhstan.
How we handle it on projects
We are developers, not lawyers, so we are responsible for the technical side. On websites, leads are written to a database on a server in Kazakhstan, consent is recorded with the date, time and version of the text, and e-mail and messengers receive a notification without extra data. A website with such a form starts from 540 000 ₸. We deploy a custom CRM on your server or with a hosting provider in Kazakhstan, starting from 800 000 ₸. The code and access stay with you. For foreign companies we can keep the working database in Kazakhstan and set up a controlled exchange with group systems. You can see how we drafted our own documents on the consent and privacy policy pages.
This is not legal advice. We have summarised the provisions as worded on 16 November 2026 and shown how we set up storage ourselves. The list of data, the policy and the consent text for your company are approved by your lawyer, and before launch it is worth checking the current wording of the law on adilet.zan.kz.
What we do on this topic
Short and to the point.
Can we keep customer data in a foreign CRM?
The law requires personal data to be stored in a database on the territory of Kazakhstan (Article 12(2) of Law No. 94-V). Sending it to a foreign service is a cross-border transfer (Article 16): to states without adequate protection it is possible, in particular, with the data subject's consent. Keep the primary database in Kazakhstan and ask the vendor where a specific CRM stores data.
Do we need our own server to store data in Kazakhstan?
No. The law speaks of a database or digital object on the territory of the country, not of your own hardware. Hosting or a data centre in Kazakhstan will do. Check in the contract where the server and the backups physically sit.
Do we have to notify the authorized body before processing?
Since the 2026 amendments, the authorized body is notified before processing starts and before it stops (Article 10-1). Small and medium operators, that is, those with data on fewer than five hundred thousand unique subjects, may work without notification. Restricted-access data raises the category by one level.
What should we do if customer data leaks?
Within one working day from detection, notify the authorized body and give the contacts of the person responsible for organising processing (Article 25(2)(8)). Then close the vulnerability and work out which data was affected. It is better to write the plan in advance.
How long should we keep customer data?
Until the purposes of collection and processing are achieved, unless another law requires keeping it longer (Article 12(2)). After that the data is deleted (Article 18), in every copy: the CRM, the mailbox, the spreadsheets and the backups. The period is worth stating in the consent and the policy.
Read also
CRM and ERP8 min readWhen off-the-shelf CRMs can't keep up: when a business needs its own CRMHow to tell that amoCRM or Bitrix24 no longer fit, and what a custom CRM built around your processes gives: data in Kazakhstan, licences, links to 1C and Kaspi.
Automation14 min readWhatsApp automation for business: a practical guideWhatsApp automation for business: what to automate, opt-in and template rules, how Meta charges for messages from October 2026, tools and how a rollout runs.
Websites12 min readWebsite for business: builder or custom, what to include and design examplesBuilder or custom website, the pages and features a business site in Kazakhstan needs, design examples by industry, common mistakes and a launch checklist.Shall we discuss your project?
We will tell you what it costs and how long it takes. The price is fixed in the contract.