TRENKO
Guide · KVKK & AI

AI runs on personal data. KVKK already applies to it.

Turkey has no standalone AI statute yet, but training and running AI on personal data already engages KVKK in full. Below, free of charge: a data-governance checklist covering lawful basis, special categories, profiling and transparency — built to sit alongside the prospective Turkish AI Act.

Download the template Reserve your spot for an online call
§ 01 — Why KVKK reaches AI

No AI Act yet — but the data law already binds.

A prospective Turkish AI Act is discussed but not in force. In the meantime, any AI that processes personal data — for training, inference or profiling — is squarely within KVKK. Four points do most of the work:

KVKK has no standalone "right not to be subject to automated decisions" like GDPR Art. 22, but its general principles constrain profiling — and aligning now with the prospective AI Act and the EU AI Act avoids re-papering later.

§ 02 — Governance map

Which KVKK duty attaches to which AI step.

ProvisionAI stepWhat it means in practice
KVKK Art. 4AllPurpose limitation, data minimisation and accuracy apply to datasets and outputs
KVKK Art. 5Training / inferenceA lawful basis is needed; public availability is not one by itself
KVKK Art. 6Sensitive dataSpecial categories usually require explicit consent
KVKK Art. 10DeploymentThe privacy notice must describe AI processing and profiling
KVKK Art. 11RightsAccess, correction and deletion cover inputs and outputs
KVKK Art. 12SecurityMeasures appropriate to the risk of the AI pipeline
Prospective AI Act / EU AI ActAlignmentMap high-risk use now to avoid re-papering later

Turkey has no standalone AI statute in force; alignment points are forward-looking. Confirm the current KVKK text.

§ 03 — Template

KVKK × AI data-governance checklist — blank.

Copy the text below or download it as markdown. No sign-up.

TR-KVKK-AI-01 · Version 1.0 · Free Download .md ↓
# KVKK × AI — DATA-GOVERNANCE CHECKLIST

Document code: TR-KVKK-AI-01 · Version 1.0 · Classification: Internal
Organisation: [NAME]   Prepared by: [NAME/ROLE]   Date: ……/……/20……
Reference: KVKK (Law 6698); prospective AI Act / EU AI Act alignment

SECTION 1 — AI SYSTEM & DATA MAP
System: [NAME]   Purpose: [……]
Training data source(s): [……]   Personal data? [ ] Y [ ] N
Inference inputs: [……]   Profiling produced? [ ] Y [ ] N

SECTION 2 — LAWFUL BASIS  (Art. 5 / Art. 6)
[ ] Basis identified for TRAINING: ……  (note: "public" is not a basis)
[ ] Basis identified for INFERENCE: ……
[ ] Special categories present? [ ] Y [ ] N → explicit consent / Art. 6 basis: ……

SECTION 3 — TRANSPARENCY & RIGHTS  (Art. 10 / Art. 11)
[ ] Privacy notice describes the AI processing and any profiling
[ ] Access / correction / deletion cover inputs AND outputs
[ ] Channel for data-subject requests defined

SECTION 4 — SECURITY & MINIMISATION  (Art. 4 / Art. 12)
[ ] Dataset minimised to purpose; retention set
[ ] Accuracy / bias check on outputs
[ ] Technical & organisational measures appropriate to risk

SECTION 5 — FORWARD ALIGNMENT
[ ] Use classified against prospective AI Act / EU AI Act risk tiers
[ ] High-risk uses flagged; human oversight defined
[ ] Cross-border transfers routed via KVKK Art. 9 (see TR-KVKK-09)

SECTION 6 — RECORDS
Retain the data map, basis analysis, notices and alignment assessment.

Owner: [ROLE]   Review cycle: [PERIOD]   Next review: ……/……/20……

This template is general and does not constitute legal advice.
§ 04 — Filling it in

Three things the checklist does not settle for you.

  1. The lawful basis for training. Whether legitimate interest, consent or another basis fits a given training set is a legal analysis, not a default.
  2. Special-category detection. Sensitive data can enter a model indirectly (e.g. inferred health signals); spotting it is the hard part.
  3. Profiling boundaries. How far a profiling output can drive a decision, and what notice it needs, depends on the use.
Note This checklist is a general framework. The lawful basis for training, special-category detection and the limits of profiling depend on your data and your use case; treating 'the data was public' as a basis, or missing inferred sensitive data, are the common failures. You can book a preliminary call to review your AI data flows and align them with the prospective AI Act.
§ 05 — Frequently asked

Questions.

Does Turkey have an AI law yet?

Not a standalone one in force. A prospective Turkish AI Act is discussed and would likely align with the EU AI Act, but AI that processes personal data is already fully within KVKK today.

Can we train on publicly available personal data?

Public availability does not, by itself, create a lawful basis under KVKK Art. 5. Training still needs a basis, and special categories under Art. 6 usually require explicit consent.

Does KVKK have a right against automated decisions like GDPR Art. 22?

KVKK has no standalone equivalent to GDPR Art. 22, but its general principles, transparency and data-subject rights constrain profiling and automated processing.

Why align with the AI Act if it's not in force?

Because mapping high-risk uses and documentation now is far cheaper than re-papering once a statute lands. The EU AI Act already sets the likely template through the 'Brussels effect'.

Related

Read next.

Let's govern your AI data flows.

In a twenty-minute call we walk your training and inference data, settle the lawful basis and special-category questions, and align the use with the prospective AI Act. If you're out of scope, we say so clearly.

Reserve your spot for an online call The call is online · the template is yours either way