Chatbots and KVKK in Turkey: customer data, privacy notice and retention in AI assistants

Chatbots under Turkey’s KVKK: personal data in chats, WhatsApp chatbot privacy notice, explicit consent, retention and deletion requests under Law No. 6698.

FUFerhat UğurluYazSis TeamPublished: November 20, 20269 min read
In short

Under Turkey’s personal data protection law (KVKK, Law No. 6698), the key point is this: the name, phone number, address and message content a customer writes in a chat are personal data; the business using the chatbot is usually the data controller and is responsible for the privacy notice, security, retention and data subject requests. Conversation history and an audit trail make this easier, but the business decides the privacy notice, retention period and deletion process.

A customer writes on WhatsApp: they share their name, phone number, a complaint about a product and perhaps a health condition. On the other side is a chatbot. Will the conversation be recorded, who will see it, how long will it be kept, and what happens if the customer asks for it to be deleted? These questions are often asked after the chatbot has been set up, yet the real decisions are made before setup. Below, we read the relevant articles of Turkey’s Personal Data Protection Law No. 6698 (KVKK) in the official text on mevzuat.gov.tr and applied them to chatbot conversations. The aim is not to give legal advice but to set out the questions a business in Turkey should ask about chatbots and KVKK before setup.

The relationship between chatbots and KVKK covers how personal data processed in a chatbot’s conversations with customers is collected, used, stored and deleted under Law No. 6698. We look at the topic through two products: the AI WhatsApp Assistant and the AI Sales and Welcome Assistant.

What personal data does a chatbot conversation create?

Article 3 of the Law defines personal data as any information relating to an identified or identifiable natural person. In a chatbot context, this is broader than it looks:

  • The name, surname, phone number, email and address the customer types.
  • Contact details arriving via WhatsApp or the website, and the date of the conversation.
  • The content of the message: orders, appointments, complaints, needs, budget and similar descriptions.
  • Summaries and qualification notes produced by the assistant; if they are linked to a person, they are personal data too.
  • Information such as health or religion that the customer writes of their own accord: Article 6 of the Law classifies these as special categories of personal data.

The last point needs care. A customer may write about their health of their own will; the assistant should never ask for such information, should hand the conversation over to a person or redirect it when such information is written, and the additional measures required for processing special categories of data must be assessed separately.

Chatbots and KVKK: what does each article mean for a chatbot?

ArticleWhat the Law says in briefWhat it means for a chatbot
3The data controller is the one who determines the purposes and means of processing; the data processor processes on its behalf.The business using the chatbot is usually the data controller, and the party providing the software may be the data processor. Clarify the roles in the contract.
4Data must be relevant, limited and proportionate to the purpose, and kept only as long as necessary.The assistant should ask only for information that is useful; the purpose and duration for keeping conversation history should be written down.
5Personal data cannot be processed without explicit consent; consent is not required if a condition such as the conclusion or performance of a contract or legitimate interest applies.Determine which condition each conversation relies on. Which condition applies depends on the specific situation; clarify it with your adviser.
6Processing special categories of data such as health data is prohibited as a rule; there are listed conditions and additional measures.The assistant should not ask for health information; if the customer writes it, the conversation should be handed over to a person.
10When data is obtained, information is given on identity, purpose, transfers, method, legal basis and rights.The privacy notice should be accessible in the first message or at the start of the conversation.
11 and 13The person has the right to learn about, correct and request deletion of their data and to object to the result of automated analysis; applications are concluded within thirty days at the latest.There should be a way to receive and track requests for access to and deletion of conversation records.
12The data controller must take technical and administrative measures for an appropriate level of security; it is jointly responsible with the data processor.Role-based access to conversation records, an audit trail and written security responsibilities with the provider.

How long are chatbot conversation records kept?

Article 4(2) of the Law requires personal data to be kept in line with this principle:

Being retained for the period stipulated in the relevant legislation or required for the purpose for which they are processed.

The text of the Law does not give a figure such as “chat records are kept for this long”; you set the period according to your purpose and the other legislation in your sector. Article 7 of the same Law states that once the reasons requiring processing no longer exist, personal data is to be erased, destroyed or anonymised, either ex officio or at the request of the data subject. In practice you need two things: a written purpose stating why the conversation record is kept, and a process that deletes or anonymises the record when that purpose ends.

How do you provide a KVKK privacy notice for a WhatsApp chatbot?

The duty to inform is defined in Article 10 of the Law as giving information at the time the data is obtained. In a chatbot, this is done at first contact with a link or a short text: the identity of the data controller, the purposes for which the data will be processed, to whom it may be transferred, the method of collection and the legal basis, and your rights. If the text is versioned, you can later show which customer saw which version. The message permission (opt-in) that Meta requires for WhatsApp and the privacy notice and explicit consent under KVKK are separate concepts; one does not replace the other.

Does the AI assistant store customer data? Questions to ask the provider

  • In which country and in which system are conversation records kept? If data is transferred abroad, how are the conditions in Article 9 of the Law met?
  • Who can access the conversation history; is there a separation of roles and permissions?
  • How long are records kept, and can you set the period yourself?
  • When a deletion or export request comes in, how many steps does it take?
  • Are customer chats used to train the AI model?
  • What does the assistant do when special categories of data are written?
  • Are the data controller and data processor roles set out in the contract?
  • How and when is the business informed of a security incident? Article 12 of the Law requires that, if data is obtained by others unlawfully, the data subject and the Personal Data Protection Board be notified as soon as possible.

Keeping customer data in Excel, WhatsApp groups and personal phones

For a business with few customers, a spreadsheet and a work phone are often enough. The problem starts when data grows: customer information is scattered across several phones, several spreadsheets and email attachments; nobody knows who accesses what; and when a deletion request arrives, finding every copy of the data becomes difficult. A chatbot can reduce this sprawl because it collects conversations in one record; but if it is not managed properly, that same record also becomes a large data pool in a single place. Centralisation requires permissions and retention periods to be centralised as well.

How do YazSis assistants handle the data side?

For the AI WhatsApp Assistant, the product page lists four controls: approved information sources, role- and team-based routing, conversation history and an audit trail, and a KVKK-focused data policy. For the AI Sales and Welcome Assistant, permitted data, secure transfer and a controlled handover to the human team are listed. These features make it easier to record conversations, manage permissions and hand over; however, the content of the privacy notice, the retention period and the deletion process need to be worked out with you for your own business. Outside customer chats, Fero, the Enterprise AI assistant designed for asking questions about internal sales and stock data, connects to the application database only with a read-only account; it cannot change the data.

For Super Randevu, the product page gives more concrete information: data and backups are kept on servers in Turkey, two-step verification is mandatory for every staff login, no medical records (diagnosis, treatment notes, prescriptions) are kept, the privacy notice and explicit consent are recorded with versions, and deletion and export are done in one step. This information applies to Super Randevu. For the AI WhatsApp Assistant and the AI Sales Assistant, details such as data location, retention period and model use are not on the product pages; we recommend clarifying them in writing at the start of the project.

Seven steps before setting up a chatbot

  1. Create a data inventory: which personal data does the chatbot collect, and where does it keep it?
  2. Write down the purpose and legal basis: for each type of data, determine why it is processed and which condition it relies on.
  3. Prepare the privacy notice: make it accessible at first contact and keep a record of its version.
  4. Define the retention period and deletion process: when the period ends, who deletes the record, and how?
  5. Define off-limits topics: write down what the assistant does with topics such as health information, ID numbers or card details, and when it hands over.
  6. Check permissions and logs: it must be possible to track who accesses the conversation history; roles with the provider must be written into the contract.
  7. Set up a request channel: who receives requests for access, correction and deletion, and within what time are they answered?

If you would like to design your chatbot’s conversation records, permission and handover rules together with us, you can request an initial meeting on the AI WhatsApp Assistant page.

Frequently asked questions

Does a chatbot fall under KVKK in Turkey?

If a chatbot processes personal data such as the customer’s name, phone number and message content, it falls under Turkish Law No. 6698. The business using the chatbot is usually the data controller; the privacy notice, security, retention and data subject requests are its responsibility.

Does a WhatsApp chatbot need a KVKK privacy notice?

Article 10 of the Law requires that, when data is obtained, the identity of the data controller, the purpose of processing, transfers, the collection method and legal basis, and the person’s rights be communicated. In a chatbot this is usually done at first contact with a text or a link; consult your adviser for details.

Does the AI assistant store customer data?

The AI WhatsApp Assistant keeps conversation history and an audit trail. Where, for how long and with what permissions the data is stored is not detailed on the product page; it should be clarified in writing at the start of the project. In Super Randevu, data is kept on servers in Turkey.

How long are chatbot conversation records kept?

The Law does not set a fixed period for chat records; it requires data to be kept for the period stipulated in the relevant legislation or required for the purpose of processing. Set the period according to your purpose and your sector’s legislation and put it in writing.

What happens if a customer asks for their conversation to be deleted?

Article 11 of the Law gives the person the right to request deletion of their data, and Article 13 states that applications are concluded within thirty days at the latest. You need to set up a process from the start that receives the request and finds and deletes or anonymises the record.

Sources

Last legal review: October 23, 2026

FU
Ferhat Uğurlu · YazSis Team

Builds enterprise software, AI and digital transformation products together with the YazSis team.