Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
KVKK restricts sending personal data out of Turkey unless an adequacy decision, an approved safeguard such as a standard contract or binding corporate rules, or a narrow derogation applies.

What Are KVKK Cross-Border Data Transfer Rules?
Moving personal data out of Turkey is a regulated act. Article 9 of Personal Data Protection Law No. 6698, known as KVKK, sets out when a controller or processor may transfer personal data abroad, and the article was rewritten by Law No. 7499, which took effect on 1 June 2024. The rewrite matters because the previous regime was close to unworkable in practice and most organisations had fallen back on explicit consent; the new one gives them realistic alternatives and, with them, real obligations.
For a UK business this is an everyday concern rather than a legal curiosity. A Turkish subsidiary using a London-hosted HR platform, a UK insurer processing claims data from a Turkish broker, and a British software company providing support from Manchester to users in Istanbul are all making international transfers under Turkish law.
The Board published its standard contract templates in 2024, in four versions covering controller to controller, controller to processor, processor to controller, and processor to processor. They are closer to the European model than to the UK’s International Data Transfer Agreement, and they are intended to be used as issued.
The trap is procedural. A signed standard contract must be notified to the Board within five business days of signature, with the required supporting information. Missing that window is a separate breach carrying its own administrative fine, independent of whether the transfer itself was otherwise lawful. Organisations that sign group agreements centrally and file them later tend to discover this the hard way. Assign the notification to the Turkish entity, with a deadline shorter than the legal one.
| Question | Turkey, KVKK Article 9 | UK GDPR Chapter V |
|---|---|---|
| Adequacy | Possible in law, none issued so far | A published list of adequate countries, reviewed periodically |
| Contractual route | Board templates, used as issued | International Data Transfer Agreement, or the Addendum to the EU clauses |
| Filing | Notification to the Board within five business days | No filing; keep records and the transfer risk assessment |
| Risk assessment | Not a separate statutory step | Transfer risk assessment expected by the ICO |
| Group mechanism | Binding corporate rules approved by the Board | Binding corporate rules approved by the ICO |
Note what the table implies about direction. Turkey has not recognised the UK as adequate, and the UK has not recognised Turkey, so transfers both ways need a mechanism. A UK importer receiving data from Turkey signs the Turkish standard contract; the same relationship running in the other direction needs an IDTA or the Addendum. Two instruments, two sets of obligations, one data flow.
Where a transfer depends on controls at the receiving end, our cloud security services can evidence how the importing environment actually protects the data rather than how the contract says it should.
No. The Personal Data Protection Board has the power to issue adequacy decisions under Article 9 but has not issued any, for the UK or for anyone else. Every transfer from Turkey to the UK therefore needs an appropriate safeguard, normally one of the Board’s standard contracts, or must fall within one of the narrow exceptional cases in the law.
If data moves in both directions, yes. The Turkish standard contract governs the export from Turkey under KVKK, and the UK International Data Transfer Agreement or the Addendum to the EU clauses governs the export from the UK under the UK GDPR. They are separate instruments addressing separate legal obligations, and neither one substitutes for the other.
Yes. Making personal data available to someone outside Turkey counts as a transfer whether or not a copy is taken, so offshore support desks, administrators, and analysts all fall in scope. The usual fix is to bring those roles inside an approved mechanism rather than to argue that viewing is not transferring.
It is treated as a distinct breach with its own administrative fine, separate from any issue with the transfer itself. The practical defence is procedural: name an owner in the Turkish entity, build the notification into the contract signing workflow, and keep evidence of the filing with the executed agreement.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.