Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Explicit consent under Turkish data protection law is freely given, informed, specific permission to process personal data, and it must be kept separate from the controller’s duty to inform.

What Is Explicit Consent Under KVKK?
Explicit consent is the permission a person gives for their personal data to be processed under Turkish Personal Data Protection Law No. 6698, known as KVKK. Article 3 defines it as consent on a particular subject, based on being informed, and expressed with free will. All three elements must hold; failing any one of them makes the consent invalid and the processing unlawful.
For a UK organisation with a Turkish subsidiary or supplier, the concept looks familiar but behaves differently in practice. Turkish compliance culture leans on consent far more heavily than UK practice does, and the duty to inform that accompanies it is a separate obligation with its own rules.
Turkish practice distinguishes sharply between the privacy notice and the consent.
The two must be presented separately. A document that merges the notice and the consent into a single signature block is a standard finding in Turkish enforcement decisions, because an individual cannot be said to have given informed, specific consent if they were agreeing to a notice at the same time.
Article 5(2) sets out the grounds that remove the need for consent: processing expressly permitted by law, protection of life or bodily integrity where consent cannot be obtained, processing necessary for a contract to which the person is a party, compliance with a legal obligation, data made public by the person themselves, establishment or exercise of a legal claim, and the legitimate interests of the controller provided fundamental rights are not harmed.
That list closely resembles the UK GDPR Article 6 grounds. The difference is cultural rather than textual: Turkish controllers historically defaulted to consent for processing that would comfortably rest on contract or legitimate interests in the UK, which creates a fragile compliance position because consent can be withdrawn at any time.
Special category data is governed by Article 6. Law No. 7499, in force from 1 June 2024, replaced the previously restrictive regime with a broader set of conditions closer to UK GDPR Article 9, so health and biometric data no longer depend almost exclusively on explicit consent.
Controllers must be able to demonstrate valid consent, which in practice means recording the version of the text shown, the timestamp, and the channel.
| Point | KVKK | UK GDPR |
|---|---|---|
| Regulator | Turkish Personal Data Protection Authority | Information Commissioner’s Office |
| Registration | Controllers above thresholds must register in the VERBIS system | No equivalent registration; a data protection fee is payable to the ICO |
| Transfers abroad | Adequacy decisions, standard contracts notified to the Authority within five business days, binding corporate rules, or explicit consent in limited cases | Adequacy regulations, the International Data Transfer Agreement or Addendum, binding corporate rules |
| Privacy notice | Separate statutory duty under Article 10, kept distinct from consent | Transparency obligations under Articles 13 and 14 |
The transfer rules changed materially in 2024. Before Law No. 7499, no adequacy decision had ever been issued and the undertaking route was slow, so Turkish controllers relied on explicit consent for international transfers. The standard contract mechanism introduced since is the route a UK group should now be using for intra-group transfers out of Turkey, alongside its own UK transfer paperwork for data moving the other way.
Map the Turkish entity’s processing to Article 5 grounds rather than assuming consent, because reducing consent dependence reduces fragility. Separate the Article 10 notice from any consent request in every channel, including web forms, paper, and call scripts. Keep granular consent records with evidence. Confirm the VERBIS registration position, which depends on employee numbers and financial thresholds. And treat KVKK breach notification as a separate workflow from ICO notification, because the thresholds and recipients differ.
For the wider framework, see our overview of KVKK and of UK GDPR. Where consent records and transfer documentation need technical evidence behind them, our regulation and compliance services can help you build it.
The legal test is close: freely given, informed, and specific to a defined purpose. The practical difference is how often it is relied upon. Turkish controllers have historically used consent for processing that UK organisations would base on contract or legitimate interests, which creates risk because consent is withdrawable at any moment and must then be honoured.
No. Turkish practice requires the Article 10 duty to inform and the explicit consent to be presented separately, and combined documents are a recurring enforcement finding. The individual must be informed first and then make a distinct, affirmative choice about the processing that genuinely requires consent. Keep separate texts, separate signatures, and separate records.
Usually not, and relying on it is risky. The Turkish authority treats employee consent as rarely freely given because of the power imbalance in the employment relationship. Most HR processing should rest on legal obligation, performance of the employment contract, or legitimate interests, with the privacy notice provided and documented at the point of collection.
Since the 2024 amendments, the routes are an adequacy decision, standard contracts notified to the Turkish Personal Data Protection Authority within five business days of signature, binding corporate rules, or the limited exceptional cases including explicit consent. Use the standard contract mechanism for routine intra-group transfers, and keep your separate UK paperwork for data moving into Turkey.
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.