Data Protection Monitor
Global Privacy & Data Protection Intelligence

Turkey Data Protection & Privacy Regulation

TR schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 92 claims · 64 sources in the cumulative register

Turkiye's data protection framework saw two material developments this cycle, both centred on the aftermath of the 2024 KVKK amendment.

Data collected Data published

AI-assembled from cited sources

Not covered: AdTech & Commercial Privacy. Not fully checked this cycle: Controller/Processor Duties, Enforcement & Redress (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 12 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix91 claims · 65 sources · machine-compiled
1 Confirmed71 Probable19 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Turkey's data protection authority, the KVKK Board, has published a clarification on how controllers must conclude a data subject's application under Law No. 6698. The announcement, dated 1 October 2026, confirms that the final response to an application must be notified to the applicant in writing or by electronic means; oral, telephone or face-to-face communication can be used only to seek clarification of the request and does not by itself discharge the controller's obligation to respond. The underlying thirty-day statutory deadline for responding to an application is unaffected by this clarification. This is a procedural tightening rather than a substantive change to the rights regime: it narrows the channels controllers may rely on to demonstrate compliance, closing off a practice of treating an oral exchange as a sufficient response.

Key regulatory facts for Turkey
Key regulatory facts for Turkey
Regulatory DimensionTurkey Standing Position
JurisdictionTurkey (TR)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 92 sourced findings)
Regulator & FrameworkComprehensive statute in force with an operational, actively enforcing regulator (KVKK) and a functioning registration system (VERBIS).
Lawful Processing & Special DataCore lawful-basis and special-category architecture is codified and enforced, but consent-thresholds guidance is comparatively thin relative to GDPR-level granularity, and some 2024 amendment detail was not independently verified this run.
Data Subject RightsAccess-right and erasure-adjacent mechanisms are confirmed and codified, but restriction/objection, portability, and precise response-deadline provisions could not be independently verified with primary citations this run.
Controller/Processor DutiesSecurity and breach-notification duties are well-evidenced and actively enforced; DPIA and formal DPO-independence requirements are absent relative to GDPR, which is a structural gap rather than a mere evidentiary one.
Primary Instruments CitedCMS Law, CBC Law, IAPP, DataGuidance, Turkey Official Instrument (legal500.com turkeys-2026347-principle-decisi)
Last Confirmed / Updated (64 sources in cumulative register)

#

Comprehensive statute in force with an operational, actively enforcing regulator (KVKK) and a functioning registration system (VERBIS).

Primary frameworkLaw No. 6698 on the Protection of Personal Data (LPPD), as amended by Law No. 7499 (2024)
Traffic-light rationale — GreenComprehensive statute in force with an operational, actively enforcing regulator (KVKK) and a functioning registration system (VERBIS).

Sub-modules (5)

Regulator and authorityGreen

KVKK is Turkey's dedicated personal-data-protection authority and Board, issuing binding decisions, guidance, and administrative fines.

Claims (5):

  • The Personal Data Protection Authority (KVKK) is Turkey's supervisory authority for the Law on the Protection of Personal Data No. 6698.
  • TBMM Decision No. 1513 (14 October 2026, published in the Official Gazette 16 October 2026) elected Recep Keskin and Cennet Alas Şekerbay to the two vacant KVKK Board seats.
  • Personal Data Protection Board (KVKK Kurumu) — Turkiye's independent supervisory authority for data protection, issuing decisions, guidelines and administrative fines
  • KVKK Authority — A public legal entity with administrative and financial autonomy, established under Law No. 6698 Article 19, headquartered in Ankara.
  • TBMM / KVKK Board membership — TBMM General Assembly elected Recep Keskin and Cennet Alas Şekerbay (both incumbents, re-elected) to fill two vacant Board seats allotted to the AK Parti group, under KVKK Law No. 6698 Art. 21; published in Official Gazette No. 33402 on 16 October 2026.

Act and instrumentsGreen

LPPD (Law 6698, 2016) is the primary instrument; Law 7499 (2024) amended Articles 6, 9 and 18.

Claims (5):

  • The Law on Protection of Personal Data No. 6698 (LPPD) was published in the Official Gazette on 7 April 2016 and entered into force as Turkey's first general data protection law.
  • Law No. 7499, amending the Code of Criminal Procedure and Certain Laws, introduced amendments to Articles 6, 9 and 18 of the LPPD, with the first segment published in the Official Gazette on 12 March 2024 and effective 1 June 2024.
  • The Article 9 cross-border transfer regime inserted by Law No. 7499 has been fully applicable since 1 September 2024.
  • Law No. 7499 — Amended KVKK to introduce GDPR-aligned legal bases and a revised cross-border transfer architecture
  • Kisisel Verileri Koruma Kurumu (KVKK) — Law No. 6698 on the Protection of Personal Data (2016), as amended by Law No. 7499 (June 2024) which overhauled cross-border transfer rules and special-category data provisions.

Material scopeGreen

Scope mirrors GDPR's automated-processing/filing-system test and shares comparable definitions of 'processing' and 'personal data'.

Claims (1):

  • The LPPD and GDPR provide comparable definitions of 'processing', 'personal data' and 'sensitive data', and both apply to automated or filing-system-based processing.

Territorial scopeAmber

The LPPD is textually silent on extraterritorial scope but VERBIS registration is applied to foreign controllers processing data collected from Turkey.

Claims (1):

  • VERBIS registration requirements extend extraterritorially to foreign (non-Turkey-established) data controllers that collect or process personal data originating in Turkey.

Regulator registration and filingGreen

VERBIS registration is mandatory for qualifying controllers (Turkish controllers with ≥50 employees or ≥TRY 25m turnover, and foreign controllers), and KVKK continues to issue clarifying announcements (e.g., on partnership structures in March 2026).

Claims (2):

  • Turkish data controllers with 50 or more employees, or annual turnover of TRY 25,000,000 or more, must register with VERBIS; failure to register can trigger fines up to TRY 1,802,000 plus a second fine for non-compliance with Board decisions.
  • In a March 2026 public announcement, KVKK clarified that partners in business partnerships, consortiums and ordinary partnerships must incorporate partnership-related personal data processing into their own individual VERBİS registrations rather than creating separate registrations.

Key findings (3)

  • KVKK-enforced LPPD (2016, amended 2024 by Law 7499) with VERBIS registration; March 2026 partnership clarification; VERBIS thresholds/fines corrected via challenger fold to Board Decision 2023/1154 and 2026-revalued figures. — source on file
  • KVKK-enforced LPPD (2016, amended 2024 by Law 7499) with VERBIS registration; March 2026 partnership clarification; VERBIS thresholds/fines corrected via challenger fold to Board Decision 2023/1154 and 2026-revalued figures. — source on file
  • KVKK-enforced LPPD (2016, amended 2024 by Law 7499) with VERBIS registration; March 2026 partnership clarification; VERBIS thresholds/fines corrected via challenger fold to Board Decision 2023/1154 and 2026-revalued figures. — source on file
Category narrative 100 words

Turkey operates a comprehensive omnibus regime under Law No. 6698 on the Protection of Personal Data (LPPD/KVKK Law), enforced by the Personal Data Protection Authority (KVKK/Kurul). The law was modelled on the pre-GDPR EU Data Protection Directive 95/46/EC and has been progressively amended (most recently by Law No. 7499 in 2024) to narrow the gap with the GDPR, particularly on special-category processing and cross-border transfers. Material and territorial scope closely track the GDPR's automated/filing-system test, and the LPPD has a recognised (if textually silent) extraterritorial reach implemented administratively through the VERBIS data-controller registry, which also functions as Turkey's registration/filing mechanism.

Periodic update · new data 2026-10-18

Two developments mark this cycle for the regulator-and-framework module in Turkey. First, the Turkish Grand National Assembly (TBMM) General Assembly elected Recep Keskin and Cennet Alas Şekerbay, both incumbents being re-elected, to fill two Board seats allotted to the AK Parti parliamentary group on the Personal Data Protection Board, acting under Article 21 of KVKK Law No. 6698. The election was published in the Official Gazette, No. 33402, dated 16 October 2026. This is a procedural renewal of the Board's composition rather than a change to its statutory powers, mandate, or institutional structure; the Board continues to operate under the same enabling law.

Second, the Board issued Principle Decision No. 2026/2035, dated 16 September 2026 and published 8 October 2026, under its general rule-making power in Article 15(6) of KVKK Law No. 6698. The decision followed a pattern of complaints that the Board found reflected a widespread practice: employers monitoring corporate email accounts assigned to staff and accessing correspondence content within those channels without employees being adequately, clearly and concretely informed that this was occurring. The Board used the decision to set out sixteen specific rules employers must follow going forward, addressing notice standards, the appropriate legal basis for monitoring, and the point at which reading message content becomes permissible. This Principle Decision sits at a sub-statutory, regulator-guidance level, issued pursuant to the Board's statutory rule-making power rather than through legislative amendment, and takes immediate effect from its stated date.

Together these two items show the regulator operating along its ordinary institutional channels this cycle: membership renewal proceeding as scheduled under Article 21, and substantive guidance issued under the Board's existing Article 15(6) authority in response to a pattern identified through its complaints process, rather than through any new primary legislation.

Outlook

With Board composition now settled following the 16 October 2026 Gazette publication, the near-term question for the regulator-and-framework module is less about institutional continuity and more about how Principle Decision 2026/2035 will be applied and enforced in practice. No enforcement fine arising specifically from the new principle decision has been identified within this window, and whether one is issued in a subsequent cycle would be the clearest signal of the Board's intent to act on the standard it has now articulated.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (14)
  1. Confirmed DataGuidance — The Personal Data Protection Authority (KVKK) is Turkey's supervisory authority for the Law on the Protection of Personal Data No. 6698. observed
  2. Confirmed DataGuidance / Esin Attorney Partnership — The Law on Protection of Personal Data No. 6698 (LPPD) was published in the Official Gazette on 7 April 2016 and entered into force as Turkey's first general data protection law. observed
  3. Confirmed IAPP — Law No. 7499, amending the Code of Criminal Procedure and Certain Laws, introduced amendments to Articles 6, 9 and 18 of the LPPD, with the first segment published in the Official Gazette on 12 March 2024 and effective 1 June 2024. observed
  4. Confirmed DataGuidance / Esin Attorney Partnership — The LPPD and GDPR provide comparable definitions of 'processing', 'personal data' and 'sensitive data', and both apply to automated or filing-system-based processing. observed
  5. Confirmed IAPP — VERBIS registration requirements extend extraterritorially to foreign (non-Turkey-established) data controllers that collect or process personal data originating in Turkey. observed
  6. Confirmed IAPP — Turkish data controllers with 50 or more employees, or annual turnover of TRY 25,000,000 or more, must register with VERBIS; failure to register can trigger fines up to TRY 1,802,000 plus a second fine for non-compliance with Board decisions. observed
  7. Confirmed DataGuidance — In a March 2026 public announcement, KVKK clarified that partners in business partnerships, consortiums and ordinary partnerships must incorporate partnership-related personal data processing into their own individual VERBİS registrations rather than creating separate registrations. observed
  8. Probable Wikipedia — TBMM Decision No. 1513 (14 October 2026, published in the Official Gazette 16 October 2026) elected Recep Keskin and Cennet Alas Şekerbay to the two vacant KVKK Board seats. observed
  9. Probable ASY Legal — The Article 9 cross-border transfer regime inserted by Law No. 7499 has been fully applicable since 1 September 2024. observed
  10. High Sadaret Hukuk — Personal Data Protection Board (KVKK Kurumu) — Turkiye's independent supervisory authority for data protection, issuing decisions, guidelines and administrative fines observed
  11. High Istanbul Attorneys — Law No. 7499 — Amended KVKK to introduce GDPR-aligned legal bases and a revised cross-border transfer architecture observed
  12. Probable Wikipedia — KVKK Authority — A public legal entity with administrative and financial autonomy, established under Law No. 6698 Article 19, headquartered in Ankara. observed
  13. Probable Memurlar.net — TBMM / KVKK Board membership — TBMM General Assembly elected Recep Keskin and Cennet Alas Şekerbay (both incumbents, re-elected) to fill two vacant Board seats allotted to the AK Parti group, under KVKK Law No. 6698 Art. 21; published in Official Gazette No. 33402 on 16 October 2026. observed
  14. Probable Wikipedia — Kisisel Verileri Koruma Kurumu (KVKK) — Law No. 6698 on the Protection of Personal Data (2016), as amended by Law No. 7499 (June 2024) which overhauled cross-border transfer rules and special-category data provisions. observed

#

Core lawful-basis and special-category architecture is codified and enforced, but consent-thresholds guidance is comparatively thin relative to GDPR-level granularity, and some 2024 amendment detail was not independently verified this run.

Primary frameworkLaw No. 6698 (LPPD), Articles 5-6, as amended by Law No. 7499 (2024)
Supervisory authorityKVKK
Traffic-light rationale — Not assessedCore lawful-basis and special-category architecture is codified and enforced, but consent-thresholds guidance is comparatively thin relative to GDPR-level granularity, and some 2024 amendment detail was not independently verified this run.

Sub-modules (4)

Lawful basesAmber

Article 5 LPPD sets out the legal grounds for processing (paralleling GDPR Art 6), referenced also as the general-ground gateway for cross-border transfer analysis.

Claims (1):

  • Personal data may be transferred and otherwise processed on legal grounds set out under Article 5 of the LPPD, which operates as the general lawful-basis gateway analogous to GDPR Article 6.

Special categoriesGreen

Article 6 LPPD enumerates special categories of personal data and was amended by Law 7499 in 2024.

Claims (3):

  • Article 6 of the LPPD regulates special categories of personal data, covering race, ethnicity, political opinion, philosophical belief, religion, sect or other belief, association/foundation/trade-union membership, health and sexual life, among other attributes.
  • Law No. 7499 (2024) amended Article 6 of the LPPD concerning the processing of special categories of personal data, effective 1 June 2024.
  • KVKK Board — Principle Decision No. 2026/921 (published 2 June 2026) finds that processing biometric data solely to track employee working time generally cannot be justified by Article 6 lawful-basis conditions, and that consent does not cure a system failing the proportionality test where less intrusive alternatives exist.

Pseudonymisation and anonymisationGreen

A dedicated KVKK Regulation governs deletion, destruction and anonymisation, requiring retention/destruction policies and time periods.

Claims (1):

  • KVKK's Regulation on the deletion, destruction and anonymisation of personal data requires data controllers to prepare retention and destruction policies with applicable time periods, and to delete, destroy or anonymise data once the processing purpose ceases to exist.

Key findings (3)

  • Article 5 lawful bases and Article 6 special categories (amended 2024); pre-2024 transfer-consent framing corrected to reflect two available routes. — source on file
  • Article 5 lawful bases and Article 6 special categories (amended 2024); pre-2024 transfer-consent framing corrected to reflect two available routes. — source on file
  • Article 5 lawful bases and Article 6 special categories (amended 2024); pre-2024 transfer-consent framing corrected to reflect two available routes. — source on file
Category narrative 93 words

The LPPD's Article 5 sets out lawful-processing grounds broadly analogous to GDPR Art 6, while Article 6 enumerates special/sensitive categories (race, ethnicity, political opinion, philosophical belief, religion/sect, association/union membership, health, sexual life, and related attributes), amended by Law 7499 (2024). Explicit consent remains central in practice given persistent gaps in secondary guidance on alternative grounds. A dedicated Regulation on the Deletion, Destruction and Anonymisation of Personal Data obliges controllers to destroy, delete or anonymise data once the processing purpose lapses, and KVKK biometric-data guidance (2021) further conditions special-category biometric processing on necessity/proportionality principles.

Sources and claims (8)
  1. Confirmed IAPP — Personal data may be transferred and otherwise processed on legal grounds set out under Article 5 of the LPPD, which operates as the general lawful-basis gateway analogous to GDPR Article 6. observed
  2. Confirmed IAPP — Article 6 of the LPPD regulates special categories of personal data, covering race, ethnicity, political opinion, philosophical belief, religion, sect or other belief, association/foundation/trade-union membership, health and sexual life, among other attributes. observed
  3. Probable IAPP — Law No. 7499 (2024) amended Article 6 of the LPPD concerning the processing of special categories of personal data, effective 1 June 2024. observed
  4. Confirmed DataGuidance — KVKK's Regulation on the deletion, destruction and anonymisation of personal data requires data controllers to prepare retention and destruction policies with applicable time periods, and to delete, destroy or anonymise data once the processing purpose ceases to exist. observed
  5. Probable IAPP — In the absence of a KVKK-issued safe-country list, obtaining the data subject's explicit consent has been, in practice, the only readily viable method to legalize cross-border personal data transfers under the pre-2024 regime. observed
  6. Probable https://www.legal500.com/intelligence/turkey/privacy/turkeys-2026347-principle-decision-on-consent-and-privacy-notices — Board Principle Decision No. 2026/347 (18 February 2026) holds that the privacy/information notice and an explicit-consent declaration are legally different instruments and must be presented separately, under Arts. 12 and 18 of Law No. 6698.
  7. Probable ASY Legal — KVKK Board — Principle Decision No. 2026/347 holds that the information/privacy notice and explicit-consent text are legally distinct instruments that must be presented separately, as an administrative/technical measure under Article 12(1) of Law No. 6698. observed
  8. Probable https://www.dataguidance.com/news/turkey-kvkk-issues-clarification-principle-decision — KVKK Board — Principle Decision No. 2026/921 (published 2 June 2026) finds that processing biometric data solely to track employee working time generally cannot be justified by Article 6 lawful-basis conditions, and that consent does not cure a system failing the proportionality test where less intrusive alternatives exist.

#

Access-right and erasure-adjacent mechanisms are confirmed and codified, but restriction/objection, portability, and precise response-deadline provisions could not be independently verified with primary citations this run.

Primary frameworkLaw No. 6698 (LPPD), Article 11
Supervisory authorityKVKK
Traffic-light rationale — AmberAccess-right and erasure-adjacent mechanisms are confirmed and codified, but restriction/objection, portability, and precise response-deadline provisions could not be independently verified with primary citations this run.

Sub-modules (5)

Access rightGreen

Article 11 LPPD grants data subjects rights including access to their processed data; KVKK issued a 2018 Regulation consolidating subject-access-request (SAR) procedures.

Claims (1):

  • KVKK published a supplementary Regulation on 10 March 2018 consolidating the procedure to be followed by data subjects and controllers with respect to subject access requests under Article 11 of the LPPD.

Rectification and erasureAmber

Erasure/destruction obligations are anchored in the Deletion, Destruction and Anonymisation Regulation, which requires controllers to delete or anonymise data once the processing purpose lapses.

Claims (1):

  • Data controllers must delete, destroy or anonymise personal data once the legal reasons for its processing cease to exist, per KVKK's regulation on deletion, destruction and anonymisation.

Restriction and objectionRed

No primary-source detail on a distinct restriction-of-processing or objection-to-profiling mechanism was retrieved this run.

Data portabilityRed

No confirmed evidence of a GDPR Article 20-style portability right was retrieved this run.

Deadlines and response windowsAmber

Retrieved sources confirm a subject-access-request procedural regulation exists, but the precise statutory response-window (day-count) was not confirmed via primary-text excerpt this run.

Claims (2):

  • KVKK Board — Final responses to data-subject applications must be notified in writing or electronically; oral/telephone/face-to-face communication may be used only for clarification and does not discharge the response obligation; the 30-day statutory deadline under Art 13 is unaffected
  • Law No. 6698 on the Protection of Personal Data (KVKK), Article 13 — A data controller must conclude an Article 11 data-subject rights application as soon as possible depending on its nature, and at the latest within 30 days, free of charge (a fee per the Board's tariff may apply only where the process entails an additional cost).

Key findings (3)

  • Article 11 access right consolidated by 2018 SAR Regulation; erasure via Deletion/Destruction/Anonymisation Regulation; portability, restriction/objection and response-window specifics unconfirmed. — source on file
  • Article 11 access right consolidated by 2018 SAR Regulation; erasure via Deletion/Destruction/Anonymisation Regulation; portability, restriction/objection and response-window specifics unconfirmed. — source on file
  • Article 11 access right consolidated by 2018 SAR Regulation; erasure via Deletion/Destruction/Anonymisation Regulation; portability, restriction/objection and response-window specifics unconfirmed. — source on file
Category narrative 64 words

Article 11 of the LPPD provides an access-right framework comparable to GDPR subject-access rights, consolidated procedurally by a 2018 KVKK Regulation. Erasure is operationalised primarily through the Deletion/Destruction/Anonymisation Regulation rather than a standalone Article-17-style 'right to be forgotten' clause. Direct primary-source confirmation of exact statutory response-window day-counts, and of restriction/objection and portability mechanics, was not obtained this run and is flagged as a gap.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (4)
  1. Confirmed DataGuidance — KVKK published a supplementary Regulation on 10 March 2018 consolidating the procedure to be followed by data subjects and controllers with respect to subject access requests under Article 11 of the LPPD. observed
  2. Confirmed DataGuidance — Data controllers must delete, destroy or anonymise personal data once the legal reasons for its processing cease to exist, per KVKK's regulation on deletion, destruction and anonymisation. observed
  3. Probable Erdem & Erdem — KVKK Board — Final responses to data-subject applications must be notified in writing or electronically; oral/telephone/face-to-face communication may be used only for clarification and does not discharge the response obligation; the 30-day statutory deadline under Art 13 is unaffected observed
  4. Probable Kişisel Verileri Koruma Kurumu (KVKK) — Law No. 6698 on the Protection of Personal Data (KVKK), Article 13 — A data controller must conclude an Article 11 data-subject rights application as soon as possible depending on its nature, and at the latest within 30 days, free of charge (a fee per the Board's tariff may apply only where the process entails an additional cost). observed

#

Security and breach-notification duties are well-evidenced and actively enforced; DPIA and formal DPO-independence requirements are absent relative to GDPR, which is a structural gap rather than a mere evidentiary one.

Primary frameworkLaw No. 6698 (LPPD), Articles 12, 16, 18; KVKK secondary regulations/communiqués
Supervisory authorityKVKK
Traffic-light rationale — AmberSecurity and breach-notification duties are well-evidenced and actively enforced; DPIA and formal DPO-independence requirements are absent relative to GDPR, which is a structural gap rather than a mere evidentiary one.

Sub-modules (7)

Accountability & DPIARed

The LPPD contains no express DPIA obligation or equivalent risk-evaluation requirement, unlike GDPR Article 35.

Claims (2):

  • Unlike the GDPR, the LPPD does not include any requirement to undertake a Data Protection Impact Assessment or any similar formal obligation to evaluate the risk of personal data processing.
  • KVKK Principle Decision No. 2026/2035 — Sets sixteen rules for employer monitoring of staff-assigned corporate email accounts: contractual clause alone is insufficient notice, explicit consent should not ordinarily be the legal basis, reading message content is a last resort, lawful basis for continued access to a departed employee's mailbox must be separately assessed.

DPO requirementsAmber

DPO appointment is not mandatory; KVKK's 2021 Communiqué established a voluntary personnel-certification mechanism rather than a binding appointment threshold.

Claims (2):

  • KVKK introduced the concept of a data protection officer via the Communiqué on the Procedures and Principles Regarding the Personnel Certification Mechanism (6 December 2021); however, appointment of a DPO is not a mandatory requirement under the LPPD.
  • KVKK DPO appointment requirement — Turkish law (KVKK, Law No. 6698) does not mandate appointment of a Data Protection Officer; data controllers instead have a registration obligation under the Data Controllers Registry (VERBİS) By-Law, which requires designation of a contact person (irtibat kişisi) rather than a DPO.

Ropa requirementsAmber

VERBIS, maintained by KVKK, serves as the functional equivalent of a records-of-processing registry, though it is structurally different from controller-held GDPR Article 30 records.

Claims (1):

  • VERBIS is principally kept and maintained by KVKK and is fundamentally different from GDPR Article 30 records kept directly by controllers, though it requires controllers to submit a data-processing inventory.

Joint controller arrangementsGreen

Controllers processing via processors remain jointly responsible with data processors, and processors are barred from using data for purposes beyond the original processing purpose.

Claims (1):

  • Where personal data is processed by a natural or legal person on behalf of a data controller, the controller is jointly responsible with data processors, who are in turn prohibited from disclosing or using data obtained from the controller for purposes other than the original processing purpose.

Security measuresGreen

Article 18(b) imposes the highest fine tier for security-of-processing failures, and KVKK has issued technical/administrative measures guidance; enforcement precedent (e.g., against tourism, banking, and e-commerce controllers) confirms active application.

Claims (4):

  • Article 18 of the LPPD imposes fines for failure to fulfil data-security provisions (historically ranging roughly TRY 15,000 to TRY 1,000,000, revalued annually), and this security-violation category has produced the highest observed fines in KVKK enforcement practice.
  • Board Principle Decision No. 2026/2035 sets sixteen procedural rules an employer must follow before monitoring staff-assigned corporate email and other work-communication channels, under Art. 15(6) of Law No. 6698.
  • KVKK Principle Decision No. 2026/2035 — Employers monitoring corporate e-mail/communication channels must restrict access to monitoring output to a limited number of personnel defined by job description, maintain access records, place accessors under confidentiality obligation; covert monitoring is prohibited
  • KVKK (Kişisel Verileri Koruma Kurumu) — Public Announcement on Matters to Consider in the Use of Security Camera Systems in Workplaces, published 8 June 2026, setting out core principles and obligations for workplace CCTV personal-data processing, including a prohibition on camera use in private areas such as toilets, changing rooms, prayer rooms and rest areas.

Breach notificationGreen

KVKK Board principle-decision interprets the Article 12(5) breach-notification deadline as 72 hours, requiring standard forms, incident logs and a breach response plan; multiple controllers have been fined for late notification.

Claims (4):

  • KVKK's Board issued a principle decision interpreting the Article 12(5) breach-notification deadline as 72 hours, requiring controllers to report delay reasons, use a standard breach notification form, log breach information, and prepare a data breach response plan.
  • KVKK Board Decision No. 2026/2203 (7 October 2026) ordered public announcement of a ransomware-related data breach affecting Yıldız Technical University's virtualisation infrastructure, first detected 1 October 2026, affecting students, personnel and visitors.
  • KVKK Decision 2019/271 — Data controllers must notify the KVKK Board and affected individuals of a personal-data breach within 72 hours of becoming aware of it
  • KVKK Board — Article 12(5) breach-notification deadline of Law No. 6698 interpreted as 72 hours, requiring a standard notification form, delay-reason reporting, breach logging and a response plan.

Retention and disposalGreen

Retention limits and disposal duties are set by the Deletion, Destruction and Anonymisation Regulation.

Claims (2):

  • KVKK's Regulation on deletion, destruction and anonymisation requires data controllers to prepare data retention and destruction policies specifying applicable time periods.
  • KVKK Board — Principle Decision No. 2026/2035 (dated 16 Sept 2026, published 8 Oct 2026) requires informed, proportionate, purpose-limited employer monitoring of corporate email and prompt closure of leavers' mailboxes, with Article 18 administrative-fine exposure for non-compliance.

Key findings (3)

  • 72-hour breach-notification Board interpretation and Article 18 security fines are strong; no DPIA requirement exists; DPO appointment remains voluntary. — source on file
  • 72-hour breach-notification Board interpretation and Article 18 security fines are strong; no DPIA requirement exists; DPO appointment remains voluntary. — source on file
  • 72-hour breach-notification Board interpretation and Article 18 security fines are strong; no DPIA requirement exists; DPO appointment remains voluntary. — source on file
Category narrative 86 words

The LPPD imposes accountability-adjacent duties (VERBIS registration/inventory, security-of-processing obligations, breach notification) but -- unlike the GDPR -- contains no express DPIA requirement, and DPO appointment remains voluntary notwithstanding a 2021 KVKK Communiqué establishing a personnel-certification mechanism. Breach notification is interpreted by Board principle-decision as a 72-hour standard, reinforced by real enforcement precedent (Clickbus, Marriott, Cathay Pacific fines for late notification). Security-of-processing failures attract the highest fine tier under Article 18(b). VERBIS functions as Turkey's de facto records-of-processing (ROPA) mechanism, though structurally distinct from GDPR Article 30.

Periodic update · new data 2026-10-18

The Personal Data Protection Board's Principle Decision No. 2026/2035, issued 16 September 2026 and published 8 October 2026 under Article 15(6) of KVKK Law No. 6698, is this cycle's material development for controller duties in Turkey. The decision responds to complaints that the Board found reflected a widespread employer practice: corporate email accounts and work-communication channels assigned to staff were being monitored, and correspondence content within those channels was being accessed, without employees being adequately, clearly and concretely informed that this monitoring was occurring or how it would be conducted.

The Board set out sixteen rules controllers acting as employers must now meet. A contractual clause referencing monitoring, standing alone, is treated as insufficient notice; the Board expects adequate, clear and concrete information to be given to employees independent of any standard employment-contract boilerplate. Explicit consent is identified as a basis that should not ordinarily be relied upon for this kind of monitoring, reflecting the structural imbalance between employer and employee that generally makes consent an unsuitable lawful basis in an employment relationship. Reading the actual content of a message is treated as a measure of last resort, meaning employers are expected to exhaust less intrusive means of oversight, such as metadata or access logs, before resorting to content review. Finally, the decision addresses a point not previously settled with this degree of specificity: a departed employee's mailbox cannot simply continue to be accessed indefinitely on the basis of whatever authority justified access during employment; the employer must separately assess and establish a lawful basis for any continued access following the end of the employment relationship.

This is a tightening development. The decision operates underneath the primary statute, as regulator-level guidance issued pursuant to the Board's existing rule-making power, rather than as a legislative amendment, but it materially narrows what counted as adequate practice under the general principles of KVKK Law No. 6698 by making explicit standards that employers could previously treat as satisfied by generic contractual language or blanket consent clauses.

Outlook

Employers relying on the older standard of contractual-clause notice or consent-based monitoring now face a compliance gap the Board has made explicit rather than merely implicit in general principles. Whether the Board issues an enforcement fine against a specific employer under this new standard within a subsequent window would be the clearest indicator of how actively the principle decision will be applied in practice; no such fine was identified within this cycle's evidence.

Sources and claims (16)
  1. Confirmed DataGuidance — Unlike the GDPR, the LPPD does not include any requirement to undertake a Data Protection Impact Assessment or any similar formal obligation to evaluate the risk of personal data processing. observed
  2. Confirmed DataGuidance — KVKK introduced the concept of a data protection officer via the Communiqué on the Procedures and Principles Regarding the Personnel Certification Mechanism (6 December 2021); however, appointment of a DPO is not a mandatory requirement under the LPPD. observed
  3. Confirmed DataGuidance / Esin Attorney Partnership — VERBIS is principally kept and maintained by KVKK and is fundamentally different from GDPR Article 30 records kept directly by controllers, though it requires controllers to submit a data-processing inventory. observed
  4. Confirmed DataGuidance / Esin Attorney Partnership — Where personal data is processed by a natural or legal person on behalf of a data controller, the controller is jointly responsible with data processors, who are in turn prohibited from disclosing or using data obtained from the controller for purposes other than the original processing purpose. observed
  5. Confirmed IAPP — Article 18 of the LPPD imposes fines for failure to fulfil data-security provisions (historically ranging roughly TRY 15,000 to TRY 1,000,000, revalued annually), and this security-violation category has produced the highest observed fines in KVKK enforcement practice. observed
  6. Confirmed IAPP — KVKK's Board issued a principle decision interpreting the Article 12(5) breach-notification deadline as 72 hours, requiring controllers to report delay reasons, use a standard breach notification form, log breach information, and prepare a data breach response plan. observed
  7. Confirmed DataGuidance — KVKK's Regulation on deletion, destruction and anonymisation requires data controllers to prepare data retention and destruction policies specifying applicable time periods. observed
  8. Probable CMS Law — Board Principle Decision No. 2026/2035 sets sixteen procedural rules an employer must follow before monitoring staff-assigned corporate email and other work-communication channels, under Art. 15(6) of Law No. 6698. observed
  9. Confirmed Sectona — KVKK Board Decision No. 2026/2203 (7 October 2026) ordered public announcement of a ransomware-related data breach affecting Yıldız Technical University's virtualisation infrastructure, first detected 1 October 2026, affecting students, personnel and visitors. observed
  10. Confirmed KVKK (official) — KVKK Principle Decision No. 2026/2035 — Sets sixteen rules for employer monitoring of staff-assigned corporate email accounts: contractual clause alone is insufficient notice, explicit consent should not ordinarily be the legal basis, reading message content is a last resort, lawful basis for continued access to a departed employee's mailbox must be separately assessed. observed
  11. Probable CBC Law — KVKK Principle Decision No. 2026/2035 — Employers monitoring corporate e-mail/communication channels must restrict access to monitoring output to a limited number of personnel defined by job description, maintain access records, place accessors under confidentiality obligation; covert monitoring is prohibited observed
  12. Probable cookieyes.com — KVKK Decision 2019/271 — Data controllers must notify the KVKK Board and affected individuals of a personal-data breach within 72 hours of becoming aware of it
  13. Probable Erdem & Erdem Law Firm — KVKK (Kişisel Verileri Koruma Kurumu) — Public Announcement on Matters to Consider in the Use of Security Camera Systems in Workplaces, published 8 June 2026, setting out core principles and obligations for workplace CCTV personal-data processing, including a prohibition on camera use in private areas such as toilets, changing rooms, prayer rooms and rest areas. observed
  14. Probable Mondaq (Turkonfed contributor) — KVKK DPO appointment requirement — Turkish law (KVKK, Law No. 6698) does not mandate appointment of a Data Protection Officer; data controllers instead have a registration obligation under the Data Controllers Registry (VERBİS) By-Law, which requires designation of a contact person (irtibat kişisi) rather than a DPO. observed
  15. Probable Pandectes — KVKK Board — Article 12(5) breach-notification deadline of Law No. 6698 interpreted as 72 hours, requiring a standard notification form, delay-reason reporting, breach logging and a response plan. observed
  16. Probable Istanbul Attorneys — KVKK Board — Principle Decision No. 2026/2035 (dated 16 Sept 2026, published 8 Oct 2026) requires informed, proportionate, purpose-limited employer monitoring of corporate email and prompt closure of leavers' mailboxes, with Article 18 administrative-fine exposure for non-compliance. observed

#

A GDPR-aligned SCC/BCR framework is now codified and operative (2024), representing significant convergence, but no safe-country/adequacy list has been published and no reciprocal adequacy status with the EU/UK was confirmed.

Primary frameworkLPPD Article 9, as amended by Law No. 7499 (2024); By-Law on Procedures and Principles for the Transfer of Personal Data Abroad (July 2024)
Supervisory authorityKVKK
Traffic-light rationale — AmberA GDPR-aligned SCC/BCR framework is now codified and operative (2024), representing significant convergence, but no safe-country/adequacy list has been published and no reciprocal adequacy status with the EU/UK was confirmed.

Sub-modules (6)

Transfer mechanismsAmber

Pre-2024, transfer mechanisms were limited to explicit consent, an undertaking-plus-KVKK-permit route, or approved BCRs; the 2024 reform added a standardized-undertaking notification route and formalized SCCs/BCRs.

Claims (8):

  • Under the pre-2024 regime, in the absence of a KVKK adequacy decision, data could be transferred abroad via notification to KVKK with a standard undertaking, submission of a written agreement with protective measures and obtaining a permit, approval of BCRs, or agreement between compatible public entities.
  • The By-Law on the Procedures and Principles for the Transfer of Personal Data Abroad, implementing amended Article 9 of the LPPD, was published and entered into force in July 2024, alongside KVKK's publication of Turkish standard contract and BCR documents.
  • Law No. 7499 replaced KVKK's rigid explicit-consent-based cross-border transfer model with a GDPR-aligned architecture using adequacy decisions, SCCs and BCRs; explicit consent is now limited to incidental, non-recurring transfers.
  • Since the Regulation on the Procedures and Principles for Transferring Personal Data Abroad took effect 10 July 2024, explicit consent alone is no longer a sufficient basis for cross-border transfer.
  • Law No. 6698 Art 9 (as amended by Law No. 7499) — Cross-border personal-data transfer requires a Board adequacy decision, a Board-approved appropriate safeguard, or a narrow Art 9(6) exception; the pre-2024 consent/one-off-permission model was replaced
  • Law No. 6698, Art 9 (as amended by Law No. 7499) — Ongoing/systematic cross-border transfers must rest on a KVKK adequacy decision, Board-approved appropriate safeguards (SCCs/BCRs/written undertaking), or a narrow set of incidental exceptions; the Board has not published a finalised country adequacy list, so the adequacy route is not yet operative
  • KVKK Law No. 6698 Art. 9 (as amended by Law No. 7499) — Since 1 June 2024, a cross-border transfer requires either a Board adequacy decision (none published for any country as of the most recent check) or a Board-form standard contract notified within 5 business days of signature; failure to notify carries a 2026 fine band of TRY90,308 to TRY1,806,377.
  • Law No. 7499 — Three-tier cross-border transfer framework (adequacy decisions, appropriate safeguards including KVKK-model SCCs, and derogations), effective since 1 June 2024.

Adequacy receivedRed

No confirmation was found this run that Turkey has received an adequacy decision from the EU or UK; this is treated as an open gap requiring EDPB/EU-Commission primary-source confirmation.

Claims (2):

  • KVKK Board — No finalised adequacy decision published for any country, sector or international organisation as of this cycle; Tier 1 (adequacy) unavailable for any destination
  • No EU adequacy decision; transfers of personal data from the EU/EEA to Turkiye require Standard Contractual Clauses or another GDPR Chapter V mechanism

Adequacy grantedRed

KVKK has not issued a 'safe country' or adequacy list of its own, meaning the adequacy-based transfer ground under Article 9 remains practically unavailable.

Claims (4):

  • As KVKK has not issued a safe-country list, the adequacy-based transfer ground under Article 9 of the LPPD has not been practically available.
  • Türkiye's KVKK Board has not published any adequacy decision for a country, sector, or international organisation as of recent 2026 reporting.
  • KVKK cross-border transfer regime (Law 7499 / Art 9, July 2024 Transfer By-Law) — As at the research date, the Personal Data Protection Board has not issued any adequacy decision (yeterlilik kararı) for outbound international personal-data transfers under the Art 9 regime; the Board's own cross-border transfer guidance states no such determination has yet been made, making standard contractual clauses/undertakings the dominant practical transfer mechanism.
  • KVKK Board — As of early 2026, no finalised list of adequate countries or sectors under the Tier-1 adequacy mechanism; organisations cannot yet rely on an adequacy decision for most transfer destinations.

SCCs and BCRsGreen

Turkish SCCs (bilateral) and BCRs now require KVKK notification/approval, with wet-ink or secure e-signature execution and further KVKK guidance expected on SCC validity.

Claims (5):

  • Turkish Standard Contractual Clauses are bilateral, require careful data-flow analysis and KVKK notification, and must be executed with wet-ink or secure e-signatures; BCRs also require KVKK approval.
  • KVKK-model Standard Contractual Clauses — Data exporters using KVKK-model SCCs for cross-border transfers must notify the Board within five business days of signature; failure has been the most common trigger for 2026 enforcement penalties
  • KVKK Decision 2024/959 — Four standard-contract templates for cross-border transfer; executed SCCs must be notified to the Authority within five business days, with a dedicated fine band under Art 18(1)(d) for failure
  • Standard contractual clauses (Tier 2 safeguard) — SCCs must be adopted without modification and notified to the Authority within five business days of signature; failure carries its own fine band under Art 18(1)(d)
  • KVKK-model Standard Contractual Clauses regime — Exporters relying on KVKK-model SCCs must notify the Personal Data Protection Board within five business days of signature; failure to meet this window is the most common trigger for 2026 KVKK enforcement penalties under Article 18(1)(d).

Transfer impact assessmentRed

No TIA-equivalent requirement was identified in the sources reviewed this run.

Data localisationAmber

No general/absolute data-localisation mandate was identified; VERBIS imposes registration/administrative obligations rather than a data-residency requirement.

Key findings (3)

  • July 2024 By-Law operationalises Turkish SCCs and BCRs; no EU/UK adequacy decision or KVKK safe-country list confirmed. — source on file
  • July 2024 By-Law operationalises Turkish SCCs and BCRs; no EU/UK adequacy decision or KVKK safe-country list confirmed. — source on file
  • July 2024 By-Law operationalises Turkish SCCs and BCRs; no EU/UK adequacy decision or KVKK safe-country list confirmed. — source on file
Category narrative 111 words

Turkey substantially overhauled its cross-border transfer regime via the March 2024 Law 7499 amendments to LPPD Article 9 and the implementing By-Law on Procedures and Principles for the Transfer of Personal Data Abroad (entered into force July 2024). The reform introduced Turkish Standard Contractual Clauses (bilateral, requiring KVKK notification and wet-ink/secure e-signature) and Binding Corporate Rules requiring KVKK approval, moving away from the pre-2024 regime under which -- absent any KVKK-issued adequacy/safe-country list -- explicit consent or an undertaking-plus-permit process were the only practical transfer routes. KVKK has not issued an EU-style adequacy decision covering Turkey, nor is Turkey confirmed to have received an adequacy decision from the EU or UK.

Periodic update · new data 2026-09-29

Law No. 7499 is understood to have replaced the KVKK's previously rigid, explicit-consent-based model for cross-border personal-data transfers with a GDPR-aligned architecture. Under this modernised structure, transfers may proceed on the basis of adequacy decisions, standard contractual clauses or binding corporate rules, with explicit data-subject consent now limited to incidental, non-recurring transfers rather than functioning as the default legal basis it previously was. This represents a material liberalisation of the transfer mechanism available to controllers moving personal data out of Turkey, bringing the regime structurally closer to the EU's own adequacy-and-safeguards model rather than relying on a consent-heavy approach that had been criticised as impractical for routine international data flows. The practical operation of the new adequacy and SCC mechanisms, including which jurisdictions may in due course receive an adequacy determination from Turkish authorities, has not yet been evidenced this cycle; this remains an open question for future monitoring.

Outlook

Watch for the first adequacy determinations or officially published standard contractual clause templates issued under the Law No. 7499 architecture, and for any KVKK guidance clarifying the boundary between incidental transfers still permitted on a consent basis and recurring transfers now requiring an adequacy or SCC/BCR mechanism.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (19)
  1. Confirmed IAPP — Under the pre-2024 regime, in the absence of a KVKK adequacy decision, data could be transferred abroad via notification to KVKK with a standard undertaking, submission of a written agreement with protective measures and obtaining a permit, approval of BCRs, or agreement between compatible public entities. observed
  2. Confirmed DataGuidance — The By-Law on the Procedures and Principles for the Transfer of Personal Data Abroad, implementing amended Article 9 of the LPPD, was published and entered into force in July 2024, alongside KVKK's publication of Turkish standard contract and BCR documents. observed
  3. Confirmed IAPP — As KVKK has not issued a safe-country list, the adequacy-based transfer ground under Article 9 of the LPPD has not been practically available. observed
  4. Confirmed DataGuidance — Turkish Standard Contractual Clauses are bilateral, require careful data-flow analysis and KVKK notification, and must be executed with wet-ink or secure e-signatures; BCRs also require KVKK approval. observed
  5. High Istanbul Attorneys — KVKK-model Standard Contractual Clauses — Data exporters using KVKK-model SCCs for cross-border transfers must notify the Board within five business days of signature; failure has been the most common trigger for 2026 enforcement penalties observed
  6. Probable Istanbul Attorneys — Law No. 7499 replaced KVKK's rigid explicit-consent-based cross-border transfer model with a GDPR-aligned architecture using adequacy decisions, SCCs and BCRs; explicit consent is now limited to incidental, non-recurring transfers. observed
  7. Probable DataProtection.gi — Since the Regulation on the Procedures and Principles for Transferring Personal Data Abroad took effect 10 July 2024, explicit consent alone is no longer a sufficient basis for cross-border transfer. observed
  8. Probable Rona Legal — KVKK Decision 2024/959 — Four standard-contract templates for cross-border transfer; executed SCCs must be notified to the Authority within five business days, with a dedicated fine band under Art 18(1)(d) for failure observed
  9. Probable Istanbul Attorneys — Law No. 6698 Art 9 (as amended by Law No. 7499) — Cross-border personal-data transfer requires a Board adequacy decision, a Board-approved appropriate safeguard, or a narrow Art 9(6) exception; the pre-2024 consent/one-off-permission model was replaced observed
  10. Probable RecordingLaw — KVKK Board — No finalised adequacy decision published for any country, sector or international organisation as of this cycle; Tier 1 (adequacy) unavailable for any destination observed
  11. Probable Sadaret Hukuk — Standard contractual clauses (Tier 2 safeguard) — SCCs must be adopted without modification and notified to the Authority within five business days of signature; failure carries its own fine band under Art 18(1)(d) observed
  12. Probable Vircon Legal — Law No. 6698, Art 9 (as amended by Law No. 7499) — Ongoing/systematic cross-border transfers must rest on a KVKK adequacy decision, Board-approved appropriate safeguards (SCCs/BCRs/written undertaking), or a narrow set of incidental exceptions; the Board has not published a finalised country adequacy list, so the adequacy route is not yet operative observed
  13. Probable PrivacyChecker — No EU adequacy decision; transfers of personal data from the EU/EEA to Turkiye require Standard Contractual Clauses or another GDPR Chapter V mechanism observed
  14. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/turkey-data-privacy-laws/ — KVKK Law No. 6698 Art. 9 (as amended by Law No. 7499) — Since 1 June 2024, a cross-border transfer requires either a Board adequacy decision (none published for any country as of the most recent check) or a Board-form standard contract notified within 5 business days of signature; failure to notify carries a 2026 fine band of TRY90,308 to TRY1,806,377.
  15. Uncertain https://www.ronalegal.com/en/blog/turkey-data-protection-law-6698-kvkk-foreign-companies-verbis-transfers-fines-2026 — Türkiye's KVKK Board has not published any adequacy decision for a country, sector, or international organisation as of recent 2026 reporting.
  16. Confirmed Sheltron — KVKK cross-border transfer regime (Law 7499 / Art 9, July 2024 Transfer By-Law) — As at the research date, the Personal Data Protection Board has not issued any adequacy decision (yeterlilik kararı) for outbound international personal-data transfers under the Art 9 regime; the Board's own cross-border transfer guidance states no such determination has yet been made, making standard contractual clauses/undertakings the dominant practical transfer mechanism. observed
  17. Probable CMS Law — Law No. 7499 — Three-tier cross-border transfer framework (adequacy decisions, appropriate safeguards including KVKK-model SCCs, and derogations), effective since 1 June 2024. observed
  18. Probable Sectona — KVKK Board — As of early 2026, no finalised list of adequate countries or sectors under the Tier-1 adequacy mechanism; organisations cannot yet rely on an adequacy decision for most transfer destinations. observed
  19. Probable DataProtection.gi — KVKK-model Standard Contractual Clauses regime — Exporters relying on KVKK-model SCCs must notify the Personal Data Protection Board within five business days of signature; failure to meet this window is the most common trigger for 2026 KVKK enforcement penalties under Article 18(1)(d). observed

#

Only the Employment data sub-module has direct, substantive evidentiary support this run; the remaining six sub-modules lack confirmed sector-specific overlay findings.

Supervisory authorityKVKK
Traffic-light rationale — RedOnly the Employment data sub-module has direct, substantive evidentiary support this run; the remaining six sub-modules lack confirmed sector-specific overlay findings.

Sub-modules (7)

Financial sector overlayRed

No financial-sector-specific DP overlay (e.g., Banking Law secrecy provisions vs. LPPD) was substantively retrieved this run.

Health sector overlayRed

No health-sector-specific overlay statute content was retrieved this run.

Telecoms and eprivacyRed

No substantive content on Electronic Communications Law No. 5809 or an ePrivacy-style overlay was retrieved this run.

Employment dataAmber

KVKK issued a public announcement (June 2026) on considerations for CCTV/security-camera use in workplaces, requiring employers to establish a legal basis under Article 5 and comply with core LPPD principles.

Claims (1):

  • KVKK's June 2026 announcement on workplace security cameras requires employers to ensure that data processing via CCTV has a legal basis under Article 5 of the LPPD and adheres to fundamental processing principles.

Credit and scoringRed

No credit-scoring-specific overlay content was retrieved this run.

educationRed

No education-sector-specific overlay content was retrieved this run.

insuranceRed

No insurance-sector-specific overlay content was retrieved this run.

Key findings (3)

  • Only Employment data (workplace CCTV, June 2026) substantively evidenced; banking, health, telecoms, credit, education and insurance overlays unresearched. — source on file
  • Only Employment data (workplace CCTV, June 2026) substantively evidenced; banking, health, telecoms, credit, education and insurance overlays unresearched. — source on file
  • Only Employment data (workplace CCTV, June 2026) substantively evidenced; banking, health, telecoms, credit, education and insurance overlays unresearched. — source on file
Category narrative 57 words

Direct sector-specific overlay statutes (banking secrecy, health-sector regulation, telecoms/ePrivacy, credit scoring, education, insurance) were not substantively retrieved this run beyond general LPPD application and one workplace-specific KVKK guidance document on CCTV/surveillance in employment settings. This module is materially thin and requires dedicated follow-up research into Turkey's Banking Law, Electronic Communications Law No. 5809, and health-data-specific secondary legislation.

Sources and claims (2)
  1. Confirmed DataGuidance — KVKK's June 2026 announcement on workplace security cameras requires employers to ensure that data processing via CCTV has a legal basis under Article 5 of the LPPD and adheres to fundamental processing principles. observed
  2. Uncertain Istanbul Attorneys — EU Data Act (Regulation (EU) 2023/2854) — Does not apply to Turkey as a non-EU/non-EEA jurisdiction; no local equivalent data-access/smart-data scheme located this cycle observed

#

No sub-module in this module reached a substantive, citable evidentiary threshold this run; all six sub-modules carry explicit absent_field_provenance.

Supervisory authorityKVKK
Traffic-light rationale — RedNo sub-module in this module reached a substantive, citable evidentiary threshold this run; all six sub-modules carry explicit absent_field_provenance.

Sub-modules (6)

Cookies and trackersRed

KVKK has published draft/guidance material on cookies, but substantive content was not retrieved this run beyond titles.

Dark patternsRed

No Turkey-specific dark-pattern prohibition content was located.

Opt out signalsRed

No GPC/DAA-equivalent opt-out-signal recognition was located for Turkey.

Clean rooms and dcrRed

No clean-room/data-collaboration-room-specific KVKK rule was located.

Cross context advertisingRed

No CPRA-style 'sale'/'share' analogue was located for Turkey.

Direct marketingRed

Turkey separately regulates commercial electronic messages and KVKK has issued at least one no-violation finding on SMS marketing, but substantive detail was not retrieved this run.

Claims (1):

  • KVKK Decision No. 2026/1183 — TRY 1 million administrative fine on a savings-finance company for processing third-party contact numbers via a 'brand ambassador' programme without explicit consent and failing the Art 10 information obligation (Art 12(1)(a) violation)

Key findings (3)

  • No substantive citable findings; cookie guidance and commercial e-messaging regulation located at title level only. — source on file
  • No substantive citable findings; cookie guidance and commercial e-messaging regulation located at title level only. — source on file
  • No substantive citable findings; cookie guidance and commercial e-messaging regulation located at title level only. — source on file
Category narrative 62 words

KVKK has issued cookie-related guidance and Turkey separately regulates commercial electronic messaging, but this run only retrieved title-level references (draft cookie guidelines, Commercial Electronic Message Management Regulation, an SMS-marketing no-violation finding) without substantive body content sufficient for citable claims. Dark patterns, opt-out signals (GPC/DAA), clean-room/data-collaboration rules, and cross-context advertising concepts akin to CPRA's 'sale'/'share' were not located in Turkish-specific sources this run.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Probable DataGuidance — KVKK Decision No. 2026/1183 — TRY 1 million administrative fine on a savings-finance company for processing third-party contact numbers via a 'brand ambassador' programme without explicit consent and failing the Art 10 information obligation (Art 12(1)(a) violation) observed

#

Biometric-data guidance is well-evidenced; AI-specific and ADM-transparency findings rest on title-level sources only and are marked Uncertain pending primary-text confirmation.

Primary frameworkLaw No. 6698 (LPPD), Articles 4 and 6; KVKK biometric-data guidance (2021)
Supervisory authorityKVKK
Traffic-light rationale — AmberBiometric-data guidance is well-evidenced; AI-specific and ADM-transparency findings rest on title-level sources only and are marked Uncertain pending primary-text confirmation.

Sub-modules (6)

Profiling restrictionsRed

No Turkey-specific Article 22-equivalent profiling restriction was confirmed this run.

Automated decision making transparencyRed

No ADM-transparency-specific KVKK rule was confirmed this run.

Claims (1):

  • KVKK AI guidance (March 2026) — Gives operational form to the Art 11 right to object to fully-automated adverse decisions: explainable reasoning, evidenceable human oversight, and a visible objection workflow

AI risk assessmentsAmber

A parliamentary AI bill and a KVKK generative-AI guide were reported to exist (late 2025), but detail was not retrieved beyond titles.

Claims (4):

  • A parliamentary bill to regulate artificial intelligence in Turkey was reported as introduced around November 2025, alongside a KVKK guide addressing generative AI and personal data protection.
  • Draft Law amending Law No. 6698, Art. 18 — Direct administrative liability (5% of prior-year turnover per infringing communication) on digital platforms permitting unconsented sharing of AI-generated content depicting an individual.
  • Draft Law (submitted 9 January 2026) amending KVKK Law No. 6698 — Proposes platform liability for unauthorised generation/dissemination of AI-generated audio, visual and written content; current legislative stage not re-verified against a TBMM tracking source this cycle.
  • KVKK AI guidance (March 2026) — Flags hiring, credit scoring, healthcare triage and public-space biometric identification as 'high risk', mandating a DPIA and audit trail; external LLM providers require purpose-specific explicit consent

Biometric regimeGreen

KVKK's September 2021 guidance defines biometric data and sets processing principles under Articles 4 and 6 of the LPPD.

Claims (3):

  • KVKK published guidance on 16 September 2021 on the considerations for processing biometric data, defining biometric data and requiring that processing methods be suitable for and proportionate to the purpose, that data be retained only as long as necessary, and that data subjects be informed in accordance with Article 10.
  • KVKK Biyometrik Verilerin İşlenmesinde Dikkat Edilmesi Gereken Hususlara İlişkin Rehber — KVKK published its Guide on Matters to Consider When Processing Biometric Data on 17 September 2021, addressing processing of biometric data as a special category of personal data.
  • KVKK Board — Turkish legislation does not mandate biometric identification systems for attendance tracking; such processing must independently satisfy proportionality. Biometric data defined to include fingerprints, vein patterns and palm prints used for identification/authentication, with a security-purpose exception for critical areas that must itself be justified and limited.

Genetic dataRed

No genetic-data-specific regime distinct from the general 'health' special category was confirmed this run.

State surveillance carveoutsAmber

The LPPD excludes processing of personal data for public-security or law-enforcement purposes from its general application, functioning as a national-security carve-out comparable to GDPR Art 2(2)/23 exemptions.

Claims (1):

  • Both the GDPR and the LPPD provide similar exclusions from their application, including for processing of personal data in the context of public security or law enforcement.

Key findings (3)

  • 2021 biometric guidance confirmed; November 2025 AI bill and generative-AI guide remain title-level only; public-security/law-enforcement carve-out confirmed. — source on file
  • 2021 biometric guidance confirmed; November 2025 AI bill and generative-AI guide remain title-level only; public-security/law-enforcement carve-out confirmed. — source on file
  • 2021 biometric guidance confirmed; November 2025 AI bill and generative-AI guide remain title-level only; public-security/law-enforcement carve-out confirmed. — source on file
Category narrative 87 words

KVKK issued dedicated guidance on biometric data processing (September 2021), grounding biometric processing in Articles 4 and 6 principles (necessity, proportionality, minimal retention, transparency). A parliamentary bill to regulate artificial intelligence was reportedly introduced (November 2025) and KVKK reportedly published a guide on generative AI and personal data protection (November 2025), though substantive text of both was not retrieved this run. The LPPD generally excludes processing for public-security/law-enforcement purposes from its scope, functioning as a national-security carve-out. No Turkey-specific ADM-transparency (Article 22-equivalent) or genetic-data-specific regime was confirmed.

No periodic updates recorded in this cycle

Sources and claims (9)
  1. Confirmed DataGuidance — KVKK published guidance on 16 September 2021 on the considerations for processing biometric data, defining biometric data and requiring that processing methods be suitable for and proportionate to the purpose, that data be retained only as long as necessary, and that data subjects be informed in accordance with Article 10. observed
  2. Confirmed DataGuidance / Esin Attorney Partnership — Both the GDPR and the LPPD provide similar exclusions from their application, including for processing of personal data in the context of public security or law enforcement. observed
  3. Uncertain DataGuidance — A parliamentary bill to regulate artificial intelligence in Turkey was reported as introduced around November 2025, alongside a KVKK guide addressing generative AI and personal data protection. observed
  4. Probable CMS Law — Draft Law amending Law No. 6698, Art. 18 — Direct administrative liability (5% of prior-year turnover per infringing communication) on digital platforms permitting unconsented sharing of AI-generated content depicting an individual. observed
  5. Uncertain CMS Law — Draft Law (submitted 9 January 2026) amending KVKK Law No. 6698 — Proposes platform liability for unauthorised generation/dissemination of AI-generated audio, visual and written content; current legislative stage not re-verified against a TBMM tracking source this cycle. observed
  6. Uncertain BIART — KVKK AI guidance (March 2026) — Gives operational form to the Art 11 right to object to fully-automated adverse decisions: explainable reasoning, evidenceable human oversight, and a visible objection workflow observed
  7. Uncertain BIART — KVKK AI guidance (March 2026) — Flags hiring, credit scoring, healthcare triage and public-space biometric identification as 'high risk', mandating a DPIA and audit trail; external LLM providers require purpose-specific explicit consent observed
  8. Probable Mondaq — KVKK Biyometrik Verilerin İşlenmesinde Dikkat Edilmesi Gereken Hususlara İlişkin Rehber — KVKK published its Guide on Matters to Consider When Processing Biometric Data on 17 September 2021, addressing processing of biometric data as a special category of personal data. observed
  9. Probable DataGuidance — KVKK Board — Turkish legislation does not mandate biometric identification systems for attendance tracking; such processing must independently satisfy proportionality. Biometric data defined to include fingerprints, vein patterns and palm prints used for identification/authentication, with a security-purpose exception for critical areas that must itself be justified and limited. observed

#

This is a confirmed statutory gap: the LPPD contains no children-specific consent, age-verification, or profiling-ban regime, and no dependent-adult-specific regime was found.

Primary frameworkLaw No. 6698 (LPPD) -- no children-specific provisions
Supervisory authorityKVKK
Traffic-light rationale — RedThis is a confirmed statutory gap: the LPPD contains no children-specific consent, age-verification, or profiling-ban regime, and no dependent-adult-specific regime was found.

Sub-modules (5)

Age verificationRed

The LPPD does not set an age limit for consent or for the notification requirement.

Claims (2):

  • The LPPD does not set an age limit for consent, and there is no age limit set for the notification requirement.
  • Regulation on the Provision of Child-Specific, Segregated Services by Social Media Providers and Age Verification — Social-media accounts for under-15s from 1 November 2026; requires age-verification and segregated child-specific services from social-media providers; issued by the Presidency of Cybersecurity, not KVKK

Minor profiling bansRed

No minor-specific profiling ban was identified; KVKK's only children-data output located is a non-binding 2020 brochure.

Claims (2):

  • KVKK's only substantive output addressing children's data is a 23 April 2020 brochure bearing similarities with GDPR protective measures, rather than a binding profiling ban.
  • KVKK Çocukların Kişisel Verilerinin Korunması Duyurusu (2020) — KVKK's only dedicated non-binding guidance specifically on children's personal data is the 23 April 2020 announcement of 8 brochures aimed separately at children, adults, and product/service developers, with no later superseding guidance identified.

Education settingsRed

No education-setting-specific children's-data rule was identified this run.

Dependent adultsRed

No dependent-adult (elderly/incapacitated)-specific protection was identified this run.

Key findings (3)

  • Confirmed structural gap: no age-verification, parental-consent, or minor-profiling-ban regime; only a non-binding 2020 brochure exists. — source on file
  • Confirmed structural gap: no age-verification, parental-consent, or minor-profiling-ban regime; only a non-binding 2020 brochure exists. — source on file
  • Confirmed structural gap: no age-verification, parental-consent, or minor-profiling-ban regime; only a non-binding 2020 brochure exists. — source on file
Category narrative 66 words

Unlike the GDPR (Article 8), the LPPD does not grant special statutory protection to children's personal data, does not set an age of consent, and does not specify whether parental/guardian consent is required for information-society services directed at minors. KVKK has issued only soft, non-binding awareness material (a 2020 brochure on children's data) rather than binding age-verification, parental-consent, or minor-profiling-ban provisions. Dependent-adult-specific protections were not identified.

No periodic updates recorded in this cycle

Sources and claims (5)
  1. Confirmed DataGuidance — The LPPD does not set an age limit for consent, and there is no age limit set for the notification requirement. observed
  2. Confirmed DataGuidance — Unlike the GDPR, the LPPD does not grant special protection to children's personal data, nor does it specify whether the consent of a parent or guardian is needed when processing children's data or providing information-society services to a child. observed
  3. Confirmed DataGuidance — KVKK's only substantive output addressing children's data is a 23 April 2020 brochure bearing similarities with GDPR protective measures, rather than a binding profiling ban. observed
  4. Probable PPC Land — Regulation on the Provision of Child-Specific, Segregated Services by Social Media Providers and Age Verification — Social-media accounts for under-15s from 1 November 2026; requires age-verification and segregated child-specific services from social-media providers; issued by the Presidency of Cybersecurity, not KVKK observed
  5. Probable Lexology — KVKK Çocukların Kişisel Verilerinin Korunması Duyurusu (2020) — KVKK's only dedicated non-binding guidance specifically on children's personal data is the 23 April 2020 announcement of 8 brochures aimed separately at children, adults, and product/service developers, with no later superseding guidance identified. observed

#

Powers, penalty tiers, and enforcement-activity evidence are strong; funding/capacity, collective-redress, and private-right-of-action sub-modules remain evidentiary gaps.

Primary frameworkLaw No. 6698 (LPPD), Article 18 (administrative fines) and Article 15 (investigative powers)
Supervisory authorityKVKK
Traffic-light rationale — AmberPowers, penalty tiers, and enforcement-activity evidence are strong; funding/capacity, collective-redress, and private-right-of-action sub-modules remain evidentiary gaps.

Sub-modules (6)

Regulator powers and penaltiesGreen

Article 18 sets four fine tiers, revalued annually; VERBIS non-registration alone can trigger fines up to TRY 1,802,000 plus a second fine for non-compliance with Board decisions.

Claims (10):

  • Article 18 of the LPPD defines four administrative fine categories: failure to fulfil the obligation to inform, failure to fulfil data-security provisions, failure to fulfil Board decisions, and failure to fulfil VERBIS registration/notification obligations, with amounts revalued annually.
  • Failure to register in time with VERBIS may result in an administrative fine of up to TRY 1,802,000, plus a second administrative fine of up to TRY 1,802,000 for non-compliance with KVKK's decisions, and KVKK may restrict the controller's data-processing activities in Turkey.
  • KVKK Article 18 — Administrative fine limits for 2026 updated based on a 25.49% revaluation rate published in Official Gazette No. 33090 pursuant to Tax Procedure Law General Communiqué No. 585.
  • KVKK Law No. 6698 Art. 18 — As revalued for 2026 at 25.49% (per RG No. 33090, 27 November 2025), administrative fines range from TRY85,437 (minimum, disclosure-obligation breach) to TRY17,092,242 (maximum, for data-security breach, non-compliance with Board decisions, or VERBİS breach).
  • For 2026, the data-security administrative fine under Law No. 6698 Art. 18(1)(b) runs from TRY 256,357 to TRY 17,092,242.
  • Law No. 6698, Art 18 (2026 revaluation) — Administrative fines range from TRY 85,437 (minimum, information-obligation breach) to TRY 17,092,242 (maximum), with a TRY 90,308-1,806,177 band for failure to notify a standard cross-border-transfer contract within five business days under Art 18(1)(d)
  • Law No. 6698 Art 18(1) — 2026 administrative fine bands up to approximately TRY 17,092,242 for data-security/VERBİS failures; TRY 85,437-1,709,200 for information-obligation failures
  • The 2026 KVKK administrative fine ceiling for non-compliance with a Board decision is TRY 17,092,242.
  • KVKK Article 18 administrative fine bands — KVKK Article 18(1)(b) fines are revalued annually by the Personal Data Protection Authority; the maximum fixed fine band for 2026 is TRY 17,092,242, applied per breach. Entities fined under this regime include Clickbus Seyahat Hizmetleri A.Ş. (TRY 550,000, Board Decision 2019/141, 16 May 2019), Marriott International (approximately TRY 1.45 million) and Cathay Pacific Airway Limited (TRY 550,000), for breach-notification and data-security failures.
  • KVKK — Article 18 administrative fine bands revalued for 2026 by 25.49% (Official Gazette No. 33090, 27 Nov 2025); data-security-obligation fine band (Art 18(1)(b)) now TRY 256,357 to TRY 17,092,242; Board-decision non-compliance band (Art 18(1)(c)) TRY 427,263 to TRY 17,092,242.

Enforcement activity indexGreen

KVKK has fined multiple international controllers for late breach notification and security-of-processing failures.

Claims (1):

  • KVKK has fined controllers for late breach notification, including Clickbus Travel Services (TRY 100,000 for notifying two months late), Marriott International (TRY 350,000 for late notification to the DPA and data subjects), and Cathay Pacific Airways (TRY 100,000 for a five-month delay).

Regulator funding and capacityRed

No funding or headcount data for KVKK was retrieved this run.

Collective redress and class actionsRed

No Turkey-specific collective-redress or class-action mechanism for data-protection claims was confirmed this run.

Private right of actionRed

No specific confirmation of a standalone private right of direct court access (distinct from KVKK complaint channels) was retrieved this run.

Recent developments 180dGreen

Within the 180 days preceding this run (roughly February-August 2026), KVKK issued a VERBİS business-partnership clarification (March 2026) and two CCTV/security-camera guidance announcements for workplaces and residential complexes (June 2026).

Claims (5):

  • In a March 2026 public announcement, KVKK clarified that partners in business partnerships, consortiums and ordinary partnerships must incorporate partnership-related personal data processing into their own individual VERBİS registrations rather than creating separate registrations.
  • KVKK's June 2026 announcement on workplace security cameras requires employers to ensure that data processing via CCTV has a legal basis under Article 5 of the LPPD and adheres to fundamental processing principles.
  • On 31 December 2025, KVKK announced updated administrative fine amounts under Article 18 of the LPPD, reflecting the revaluation rate for 2017-2026.
  • KVKK 2026 fine-band revaluation — KVKK's 2026 administrative fine bands increased by 25.49% over 2025 figures effective 1 January 2026, with maximum fines of approximately TRY 17,092,242 for data-security, VERBIS-registration and Board-decision non-compliance violations
  • The KVKK's most recently surfaced decision-summary batch is dated 10 August 2026.

Key findings (3)

  • Four-tier Article 18 fine architecture and active enforcement (Clickbus, Marriott, Cathay Pacific); VERBIS fine ceiling corrected via challenger fold; funding, collective redress and private right of action unconfirmed. — source on file
  • Four-tier Article 18 fine architecture and active enforcement (Clickbus, Marriott, Cathay Pacific); VERBIS fine ceiling corrected via challenger fold; funding, collective redress and private right of action unconfirmed. — source on file
  • Four-tier Article 18 fine architecture and active enforcement (Clickbus, Marriott, Cathay Pacific); VERBIS fine ceiling corrected via challenger fold; funding, collective redress and private right of action unconfirmed. — source on file
Category narrative 98 words

KVKK has broad investigative and sanctioning powers under Article 18 of the LPPD, with four fine tiers (failure to inform; data-security failures; non-compliance with Board decisions; VERBIS registration failures), annually revalued and reaching over TRY 1.8 million per violation category by the 2020s. Enforcement activity includes real fines for late breach notification (Clickbus, Marriott, Cathay Pacific) and for security-of-processing failures. Recent (within-180-day) developments include KVKK's March 2026 VERBİS partnership clarification and June 2026 CCTV/workplace and residential guidance. Regulator funding/headcount signals, collective-redress mechanisms, and a distinct private right of action were not confirmed with citable primary sources this run.

Periodic update · new data 2026-09-29

KVKK Article 18's administrative fine bands were revalued for 2026, applying a 25.49% uplift published in Official Gazette No. 33090 pursuant to Tax Procedure Law General Communiqué No. 585. This is understood to be a routine, inflation-indexed annual adjustment to the existing fine-band structure rather than a substantive expansion of the regulator's enforcement powers, investigative authority, or the categories of conduct subject to administrative fines. The adjustment took effect from 1 January 2026. Considered alongside the proposed KVKK Article 18 amendment on AI-generated-content platform liability, the enforcement and redress landscape in Turkey shows two distinct tracks moving at different speeds: the existing fine-band structure is being maintained and adjusted for inflation on its normal annual cycle, while a separate and more consequential proposed liability mechanism specific to AI-generated content remains at the draft stage before the legislature.

Outlook

Watch for the KVKK's enforcement activity and decision publications through the remainder of 2026 to assess whether the revalued fine bands are being applied in practice, and for how the proposed AI-generated-content liability provision, if enacted, would integrate with or sit alongside the existing Article 18 fine structure.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (14)
  1. Confirmed IAPP — Article 18 of the LPPD defines four administrative fine categories: failure to fulfil the obligation to inform, failure to fulfil data-security provisions, failure to fulfil Board decisions, and failure to fulfil VERBIS registration/notification obligations, with amounts revalued annually. observed
  2. Confirmed IAPP — Failure to register in time with VERBIS may result in an administrative fine of up to TRY 1,802,000, plus a second administrative fine of up to TRY 1,802,000 for non-compliance with KVKK's decisions, and KVKK may restrict the controller's data-processing activities in Turkey. observed
  3. Confirmed IAPP — KVKK has fined controllers for late breach notification, including Clickbus Travel Services (TRY 100,000 for notifying two months late), Marriott International (TRY 350,000 for late notification to the DPA and data subjects), and Cathay Pacific Airways (TRY 100,000 for a five-month delay). observed
  4. Confirmed DataGuidance — On 31 December 2025, KVKK announced updated administrative fine amounts under Article 18 of the LPPD, reflecting the revaluation rate for 2017-2026. observed
  5. High Recording Law — KVKK 2026 fine-band revaluation — KVKK's 2026 administrative fine bands increased by 25.49% over 2025 figures effective 1 January 2026, with maximum fines of approximately TRY 17,092,242 for data-security, VERBIS-registration and Board-decision non-compliance violations observed
  6. Probable Sectona — KVKK Article 18 — Administrative fine limits for 2026 updated based on a 25.49% revaluation rate published in Official Gazette No. 33090 pursuant to Tax Procedure Law General Communiqué No. 585. observed
  7. Probable COTT Group — KVKK Law No. 6698 Art. 18 — As revalued for 2026 at 25.49% (per RG No. 33090, 27 November 2025), administrative fines range from TRY85,437 (minimum, disclosure-obligation breach) to TRY17,092,242 (maximum, for data-security breach, non-compliance with Board decisions, or VERBİS breach). observed
  8. Probable DataGuidance — For 2026, the data-security administrative fine under Law No. 6698 Art. 18(1)(b) runs from TRY 256,357 to TRY 17,092,242. observed
  9. Probable Data Protection Turkey — Law No. 6698, Art 18 (2026 revaluation) — Administrative fines range from TRY 85,437 (minimum, information-obligation breach) to TRY 17,092,242 (maximum), with a TRY 90,308-1,806,177 band for failure to notify a standard cross-border-transfer contract within five business days under Art 18(1)(d) observed
  10. Probable KVKK Otomat — Law No. 6698 Art 18(1) — 2026 administrative fine bands up to approximately TRY 17,092,242 for data-security/VERBİS failures; TRY 85,437-1,709,200 for information-obligation failures observed
  11. Probable ASY Legal — The 2026 KVKK administrative fine ceiling for non-compliance with a Board decision is TRY 17,092,242. observed
  12. Uncertain Wikipedia — The KVKK's most recently surfaced decision-summary batch is dated 10 August 2026. observed
  13. Probable Köksal Partners — KVKK Article 18 administrative fine bands — KVKK Article 18(1)(b) fines are revalued annually by the Personal Data Protection Authority; the maximum fixed fine band for 2026 is TRY 17,092,242, applied per breach. Entities fined under this regime include Clickbus Seyahat Hizmetleri A.Ş. (TRY 550,000, Board Decision 2019/141, 16 May 2019), Marriott International (approximately TRY 1.45 million) and Cathay Pacific Airway Limited (TRY 550,000), for breach-notification and data-security failures. observed
  14. Probable NHIMG — KVKK — Article 18 administrative fine bands revalued for 2026 by 25.49% (Official Gazette No. 33090, 27 Nov 2025); data-security-obligation fine band (Art 18(1)(b)) now TRY 256,357 to TRY 17,092,242; Board-decision non-compliance band (Art 18(1)(c)) TRY 427,263 to TRY 17,092,242. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 92 claim(s) (92 category placement(s)), 64 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (1 contradicted by the cited source; 7 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsdeadlines and response windows
Art. 14Data Subject Rightsdeadlines and response windows
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacyadequacy granted
Art. 47Cross-Border & Adequacytransfer mechanisms
Art. 48Cross-Border & Adequacysccs and bcrs
Art. 49Cross-Border & Adequacysccs and bcrs
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressregulator powers and penalties
Art. 79Enforcement & Redressregulator powers and penalties
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redressenforcement activity index
Art. 84Enforcement & Redressregulator powers and penalties