MB
MertCan Boyar
/

kvkk-dsr-validity

Assesses whether an incoming request to a Turkish data controller is a formally valid *ilgili kişi başvurusu* under KVKK Art. 11 and 13 and the Veri Sorumlusuna Başvuru Usul ve Esasları Hakkında Tebliğ, and produces a Turkish-language memo for compliance teams and in-house counsel. The skill checks form, not merits. It works through a fixed sequence: threshold (natural person, addressed to the controller, an identifiable Art. 11 right, submitted in Turkish per Tebliğ md. 4/2), channel validity (md. 5/1 — written, KEP, e-signature, mobile signature, previously registered e-mail, or purpose-built application), mandatory content (md. 5/2 a–d, with (ç) treated as optional), attachments (md. 5/3, informational only), representation and proof of authority, and application date and deadlines (md. 5/4–5, Art. 13/2 thirty days, Art. 14/1 sixty-day complaint horizon). It returns one of four verdicts — GEÇERLİ, EKSİK – TAMAMLATILABİLİR, GEÇERSİZ, or KVKK m.11 KAPSAMI DIŞINDA — with fixed p

3 views
1 downloads

Overview

Assess whether an incoming request to a Turkish data controller is a formally valid ilgili kişi başvurusu (data subject request) under KVKK Art. 11 and 13 and the Veri Sorumlusuna Başvuru Usul ve Esasları Hakkında Tebliğ (md. 4–5), then produce a Turkish memo with a verdict (geçerli / eksik / geçersiz / kapsam dışı), deadline and recommended action. Use this whenever someone shares or describes a KVKK request, ilgili kişi başvurusu, veri sahibi talebi, "verilerimi silin" e-mail, KEP application, DSAR under Turkish law, or asks whether a controller must respond to a request, whether a request was sent through a valid channel, whether a başvuru is eksik, or when the 30-day period starts — even if they don't say "KVKK" or "Tebliğ" explicitly. Not for GDPR-only requests or for assessing the merits of the request.