A SaaS company incorporated in Delaware sells subscriptions to Turkish users through a Turkish-language website; a Dutch marketplace ships to Istanbul and keeps the buyers’ data in Frankfurt; a Singaporean mobile game stores the profiles of a few hundred thousand Turkish players. None has an office in Türkiye, and all ask the same question: does the Turkish data protection law apply, and what does it require? This article sets out what the Personal Data Protection Law No. 6698 (Kişisel Verilerin Korunması Kanunu, KVKK) says about its own scope, what a controller established abroad must do about notice, security, registration and data subject requests, how cross-border transfers work under Article 9 as amended in 2024, and how the fines in Article 18 are structured.
Scope: what Article 2 says and what it does not say
Article 2(1) of the KVKK provides that the Law applies to natural persons whose personal data are processed and to natural and legal persons who process such data wholly or partly by automated means, or by non-automated means provided the data form part of a data recording system. That is the entire scope provision. It is framed around the processing activity and the persons involved, not around the place of establishment, and contains neither an establishment test nor an express rule about offering goods or services to persons in Türkiye: nothing in the text excludes a company established abroad, and nothing expressly captures it on the basis of where its users are. The Law does anticipate a controller acting through a representative: Articles 10(1)(a) and 16(3)(a) refer to the controller “and, if any, its representative”, and Article 22(1)(g) authorises the Board to regulate the duties of the controller and its representative. Applicability to a foreign company is therefore a matter of regulatory practice rather than a statutory formula, and a company that processes the data of people in Türkiye in a structured system is well advised to treat the Law as applicable. Under Article 3 the data controller (veri sorumlusu) determines the purposes and means of processing and is responsible for the data recording system, while the data processor (veri işleyen) processes data on the controller’s behalf.
Lawful basis and the notice duty: Articles 4, 5, 6 and 10
Article 4(2) sets the principles: lawful and fair processing, accuracy, specific and legitimate purposes, proportionality, and retention only as long as the law or the purpose requires. Article 5(1) makes explicit consent (açık rıza) the default basis, and Article 5(2) lists the alternatives: express provision in law, protection of life, necessity for a contract with the data subject, the controller’s legal obligation, data made public by the data subject, the establishment or protection of a right, and the controller’s legitimate interests where they do not harm the data subject’s fundamental rights. Article 3(1)(a) defines explicit consent as consent relating to a specific matter, based on information and freely given, so a pre-ticked box does not meet it. Special categories under Article 6(1), such as health, biometric and genetic data, may be processed only on the grounds listed in Article 6(3) as amended in 2024. Article 10(1) obliges the controller to inform data subjects, when the data are obtained, of its identity and that of its representative if any, the purposes, the recipients and purposes of transfer, the method and legal basis of collection, and the rights under Article 11. For a foreign company the notice (aydınlatma metni) is usually the first visible compliance step.
Security, breaches and data subject requests: Articles 11 to 14
Under Article 12(1) the controller must take all necessary technical and administrative measures to ensure an appropriate level of security in order to prevent unlawful processing of and unlawful access to personal data and to ensure their preservation. Article 12(2) makes the controller jointly responsible with its processors for those measures, which is the statutory reason for data processing agreements with hosting and analytics vendors, and Article 12(5) requires that, where data are obtained by others through unlawful means, the controller notify the data subject and the Board as soon as possible (en kısa sürede); the Law itself sets no hour count, but the Board’s Decision No. 2019/10 of 24 January 2019 reads “as soon as possible” as without delay and at the latest within 72 hours of the controller learning of the breach. Article 11(1) gives every data subject the right to learn whether his or her data are processed and for what purpose, to know the third parties in Türkiye or abroad to whom the data are transferred, to request rectification, erasure or destruction, to object to a result produced exclusively by automated analysis, and to claim compensation. Under Article 13 the controller must conclude a request free of charge at the latest within thirty days, accepting it or refusing it with reasons. If the request is refused, answered inadequately or not answered in time, Article 14 allows a complaint to the Board within thirty days of the answer and in any event within sixty days of the request; the route to the controller must be exhausted first. During an investigation the controller must provide documents within fifteen days (Article 15(3)), must remedy the breach the Board finds within thirty days (Article 15(5)), and may have processing or a cross-border transfer halted where there is a risk of irreparable harm and a manifest breach (Article 15(7)).
VERBİS registration and the Board’s exemption power: Article 16
Article 16(1) establishes the public Data Controllers’ Registry (Veri Sorumluları Sicili, VERBİS). Article 16(2) contains the rule and the exception in two sentences: natural and legal persons who process personal data must register before they begin processing, but the Board may exempt categories of controllers from the obligation on the basis of objective criteria such as the nature and number of the data processed, whether processing is required by law, and whether the data are transferred to third parties. The Board has used that power, but its size-based exemptions do not extend to controllers established abroad: under the Board’s Decision No. 2019/387 of 17 December 2019, a data controller resident abroad must register whatever its size, through a data controller representative in Türkiye. Where registration applies, Article 16(3) lists the content of the notification: identity and address of the controller and of its representative if any, purposes, data subject groups and data categories, recipients, the data intended to be transferred abroad, security measures, and the maximum retention period for each purpose; changes must be notified immediately (Article 16(4)). The entry therefore forces a company to draw up the inventory that the rest of the Law presupposes. The VERBİS registration checklist walks through that inventory step by step.
Cross-border transfers under Article 9 as amended
For a company established abroad almost every processing operation is also a transfer out of Türkiye, so Article 9 shapes the architecture. Law No. 7499 of 2 March 2024 rewrote it with effect from 1 June 2024, with the old first paragraph applicable in parallel until 1 September 2024 (Transitional Article 3). The new structure has three tiers. First, under Article 9(1) data may be transferred abroad where a condition of Articles 5 or 6 is met and an adequacy decision (yeterlilik kararı) exists for the destination country, a sector within it or an international organisation. Adequacy decisions are taken by the Board, published in the Official Gazette and reviewed at least every four years (Article 9(2)); Article 9(3) lists the criteria, starting with reciprocity, the destination’s legislation and practice and the existence of an independent supervisory authority and effective remedies. Second, absent an adequacy decision, Article 9(4) allows a transfer where a condition of Articles 5 or 6 is met, the data subject can exercise his or her rights and seek effective remedies in the destination, and one of four appropriate safeguards (uygun güvenceler) is provided: an agreement between public bodies with the Board’s permission; binding corporate rules (bağlayıcı şirket kuralları) approved by the Board within a group engaged in joint economic activity; a standard contract (standart sözleşme) in the form announced by the Board; or a written undertaking with adequate protection, with the Board’s permission. Article 9(5) attaches a deadline to the most commonly used instrument: the standard contract must be notified to the Authority by the controller or processor within five business days of its signature. Third, where neither is available, Article 9(6) permits a transfer only on an incidental basis (arızi olmak kaydıyla) in listed situations, including explicit consent given after the data subject is informed of the possible risks, necessity for a contract with the data subject, an overriding public interest and the establishment, exercise or defence of a right. Article 9(8) extends the same rules to onward transfers, and Article 9(11) leaves the procedure to a regulation. For a foreign SaaS provider the resulting model is a standard contract with the Turkish customer or Turkish-facing entity, notified within five business days, with consent reserved for genuinely occasional transfers.
| Route | Provision | Condition | Formality |
|---|---|---|---|
| Adequacy decision | Art. 9(1)-(3) | Board decision for the country, sector or organisation | None beyond the general rules |
| Standard contract | Art. 9(4)(c), 9(5) | Board-published template | Notify the Authority within five business days of signature |
| Binding corporate rules | Art. 9(4)(b) | Group engaged in joint economic activity | Board approval |
| Written undertaking | Art. 9(4)(ç) | Adequate protection in the text | Board permission for the transfer |
| Incidental transfer | Art. 9(6) | Occasional only; e.g. informed explicit consent | Cannot be the routine basis |
Sanctions: the structure of Article 18
Article 18(1) lists five administrative fines and Article 18(2) states who pays them. Breach of the notice duty of Article 10, the security duties of Article 12, a Board decision under Article 15 or the registry duties of Article 16 is fined, and these four fines fall on the controller. The fifth, added in 2024, punishes failure to notify a standard contract within the five business days of Article 9(5) and falls on the controller or the processor. The ranges written into the Law are the amounts as enacted (5,000 to 100,000 Turkish lira for the notice duty and up to 1,000,000 lira for the other four); they are revalued every year under the general rules on administrative fines, and the amounts announced by the Authority for 2026 are: notice duty 85,437 to 1,709,200 lira; security duties 256,357 to 17,092,242 lira; Board decisions 427,263 to 17,092,242 lira; registry duties 341,809 to 17,092,242 lira; standard contract notification 90,308 to 1,806,177 lira. Since 2024, fines imposed by the Board can be challenged before the administrative courts (Article 18(3)). Article 17 adds the criminal layer by referring to Articles 135 to 140 of the Turkish Criminal Code, and Article 14(3) preserves the data subject’s compensation claim. In practice the sanction to fear most is Article 15(7): an order halting processing or a cross-border transfer stops the product rather than the budget.
A compliance sequence for a foreign company
Start with the data inventory that Article 16(3) will require in any event. Decide the roles: whether the foreign entity is the controller towards Turkish users or a processor for a Turkish customer, because Articles 10, 12, 13 and 16 address the controller while Articles 9 and 18(1)(d) address both. Draft the Turkish notice under Article 10, and rely on consent only where it is the real basis, preferring the contract and legitimate-interest bases of Article 5(2) where they fit. Put the Article 12 measures in writing and sign processing agreements with vendors. Choose the Article 9 route for each flow out of Türkiye and diarise the five-business-day notification. Register with VERBİS through a data controller representative in Türkiye before processing begins, since the size-based exemptions do not cover controllers established abroad. Finally, build the thirty-day response process of Article 13 and the breach notification path of Article 12(5).
The company has no office in Türkiye. Does the KVKK apply?
Article 2 defines the scope by processing activity and the persons involved, without an establishment or location test, so the text neither excludes a foreign company nor expressly captures it. Because the Law contemplates a controller’s representative and leaves the question to regulatory practice, a company that systematically processes the data of people in Türkiye should plan on the basis that it applies.
Is a GDPR-style standard contractual clause enough to move data from Türkiye to the EU?
No. Article 9(4)(c) refers to the standard contract announced by the Board, not to the European Commission’s clauses, and Article 9(5) requires the signed contract to be notified within five business days, on pain of the fine in Article 18(1)(d). Absent an adequacy decision for the destination, the Turkish template or another Article 9(4) safeguard is needed.
Can explicit consent be used for all transfers abroad?
Only exceptionally. Under Article 9(6) informed explicit consent justifies a transfer only where it is incidental and no adequacy decision or appropriate safeguard is available. A product that routinely sends every user’s data abroad needs an Article 9(1) or 9(4) basis, in practice the standard contract.
Related: KVKK and GDPR compliance · VERBİS registration checklist · VERBİS · international desk.
Sources. Personal Data Protection Law No. 6698 (Articles 2-7, 9-18, 22, 28 and Transitional Article 3, as amended by Law No. 7499 of 2 March 2024). Statute links open the official Turkish texts on mevzuat.gov.tr.
This article is provided for general information only and does not constitute legal advice. Please seek legal support for an assessment of any specific matter.
Author
-
View all postsMümtaz is the Managing Partner of Vircon Legal, which he founded in 2016. He advises founders, investors and operators on financing rounds, M&A, cross-border incorporations and regulated verticals such as crypto-asset infrastructure, fintech and games, bringing a former startup founder's perspective to every engagement. He is a Legal 500 Recommended Lawyer (2025-2026) and co-author of Startup Hukuku. Canonical profile: https://mumtazhacipasaoglu.com · Open-access legal guides: https://github.com/mumtazhpo
More from Vircon Insights
Hiring Your First Employees in Türkiye as a Foreign-Owned Company: Labour Law No. 4857 and Severance (Law 1475 Art. 14)
November 11, 2026Entering Türkiye as a Foreign Company: Subsidiary, Branch or Liaison Office (TCC Art. 40, KVK Art. 3, Law 4875)
November 10, 2026Platform Liability for User Content in Türkiye: Law No. 5651 Hosting Duties, Blocking Routes and the EU DSA
November 13, 2026Foreign Parent Stock Options for Employees in Türkiye: GVK Art. 61 and 94, the Art. 17 Exemption, TCC Art. 463
November 9, 2026Protecting a Foreign Brand in Türkiye: First-to-File, Bad-Faith Filings and Non-Use under SMK Arts. 6, 9, 12, 18, 26
November 14, 2026Removing Content from Google, Meta and X from Türkiye: What a Turkish Order Achieves and Which Foreign Channels Work
November 13, 2026Related Practice Areas
Privacy & Cybersecurity
KVKK and GDPR compliance, breach response, cybersecurity governance.
View service →Corporate Law
Share transfers, capital increases, board structuring, governance.
View service →US Company Formations & Flip-Ups
Delaware C-Corp, flip-up structures, SAFE/convertible notes, 83(b).
View service →