“My car was hit in the car park last Tuesday; I want that footage.” The moment this application arrives, two clocks start ticking at once: KVKK’s 30-day response period and the NVR’s loop deletion schedule. The second is often shorter. An organization that leaves the application sitting in an inbox for three weeks finds, when it sits down to write the reply, that the recording has long been overwritten. What’s more, people other than the applicant appear in the footage. Below we explain, in order of implementation, how to handle a camera recording request from the day the application is received until the file is closed.
Why camera recordings are different in an application
Article 11 of KVKK gives the data subject rights such as learning whether their personal data is being processed, requesting information if it is, learning the purpose of processing, knowing the third parties the data has been transferred to, requesting correction, deletion or destruction, and claiming compensation for damage. Article 13 provides that the data controller concludes the application as soon as possible according to the nature of the request, within thirty days at the latest, and as a rule free of charge. The application procedure is set out in the Communiqué on the Procedures and Principles of Application to the Data Controller, published in the Official Gazette on 10 March 2018; the current text is available on mevzuat.gov.tr.
Camera recordings differ in exercising these rights at three points. First, recordings are deleted on a loop; they can disappear on their own while the application waits. Second, other people appear in the image, and their data can’t be disclosed to the applicant. Third, verifying that the person is the one in the footage isn’t as easy as matching a name in a customer record. Because KVKK doesn’t contain an explicitly regulated “right to a copy” as the GDPR does, the method used to meet the request is also assessed on the facts of the case.
Receiving the application and verifying identity
Under the Communiqué, an application can be made in writing or by registered electronic mail (KEP), secure electronic signature, mobile signature, an email address the data subject previously notified to the data controller and that is registered in the system, or through software or an application designed for the purpose. The application includes name and surname, a signature if in writing, ID number (nationality and passport or ID number for foreigners), the address for notifications, email and phone if any, and the subject of the request. The application channel you show in the privacy notice should be compatible with these methods; preparing the notice is explained in the camera privacy notice guide.
There’s a disconnect common on site: the application arrives verbally at the security booth or reception, isn’t logged, and the person responsible for cameras never hears of it. A single instruction to reception and security staff is enough: direct anyone asking for camera footage to the written application channel and notify the person responsible the same day. Two separate verifications are done for a camera request:
- Identity verification: That the applicant is who they claim to be is verified according to the application method (signature, KEP, e-signature, registered email).
- Verifying the person in the image: That the applicant is the person in the footage sought is reasonably confirmed. For this, information sufficient to find the recording is requested, such as location, date, time range, vehicle plate or a description of clothing. If needed, matching is done against existing records such as visitor logs or access control records; however, no more new data than necessary should be collected for this purpose.
If the information isn’t enough to find the recording, additional information is requested. If the request is very broad (“all recordings of me in the last six months”), talking with the applicant to clarify the scope both makes the task possible and prevents unnecessary data searching.
Finding and protecting the recording
The first technical task on the day the application is received is protecting the relevant recordings from loop deletion. Camera systems mostly have retention periods measured in days, and the 30-day response period can exceed this. Lock first, correspond later. The steps:
- Identify the relevant cameras from the location information in the application. A camera coverage plan and a camera naming standard speed up this step.
- Add a reasonable margin to the time range (for example 30 minutes before and after the stated time), and check that camera and VMS clocks are correct.
- Lock or protect this range in the VMS; write the application number as the reason for the lock.
- Review the recording to determine whether the applicant appears in the footage; the review should be done only by an authorized role and appear in the audit trail.
- If the retention period has expired and there’s no recording, log this together with the relevant camera’s retention setting.
Don’t underestimate the second step. The clock of a camera without NTP configured can drift by minutes within weeks; an incident the person says happened at 14:10 appears at 14:03 in the recording. If you keep the margin tight, you’ll reply that the recording was “not found.” A recording not being found is also a valid outcome, but the reason must be documented. How the retention period is set and written into policy is explained in the camera recording retention period guide; referring to this period in the reply makes it easier for the person to understand the situation.
Masking third parties
If other people, vehicle plates or screens appear in the footage, they’re made unrecognizable in the copy to be given to the applicant. Masking can be done with the VMS’s redaction tool or a separate video editing workflow. Points to watch:
- The original recording isn’t modified; the masked copy is produced as a separate file, and the hash values of both files are recorded.
- Redaction done with automatic object tracking is checked frame by frame; a face left uncovered in a single frame defeats the purpose of the mask.
- Not just faces: name badges, plates, screens and other elements that make a person recognizable are also assessed.
- If the recording has audio, third parties’ conversations are also removed, or the audio channel is dropped.
Masking options at the static, dynamic and export stages, and an example FFmpeg command, are in the privacy masking in cameras guide. If masking a long recording from a crowded area creates a disproportionate workload, alternatives such as viewing on site or selected frames from the recording can be considered.
Response options table
Possible responses depending on the content of the application and the state of the recording are below. The table is for decision support; the final decision is made with the legal advisor.
| Status | Possible response | Watch out for |
|---|---|---|
| Retention period expired, no recording | Written information: that there’s no recording, and the retention period | The camera setting and date record are kept |
| Recording exists; only the applicant appears | Viewing on site or a copy | The copy format and delivery method must be secure |
| Recording exists; other people appear too | Masked copy or viewing on site | Third parties’ recognizability is removed |
| The recording is part of an investigation or court case | Legal assessment and a reasoned response | KVKK Article 28 exceptions are assessed |
| Deletion request | Deletion according to the retention policy, or reasoned refusal | For a protected recording, the reason for protection is explained |
| Request for transfer information | Information about the parties the recording was transferred to | Export records in the audit trail are used |
If a copy is provided, the delivery method must also be secure. An encrypted archive with the password sent through a separate channel, or hand delivery on presentation of ID, can be preferred. Sending the recording file unencrypted via a general file-sharing link creates a new risk while answering the application. Under the Communiqué, if the response is provided on a recording medium such as a CD or flash drive, any fee charged can’t exceed the cost of the medium; check the Communiqué’s current provisions before charging a fee. If the response is negative or partly met, the reason is given in writing. If the data subject isn’t satisfied with the response, they can file a complaint with the Board under Article 14; follow kvkk.gov.tr for the Board’s decisions and guidance.
Process record and checklist
Every application produces a record file that can later be shown to the Board or an auditor. The file contains the application itself, the identity verification method, the protected camera and time range, the people who carried out the review and masking, the hash values of the files produced, the response text and proof of delivery. When the file closes, the recording lock is lifted, and the copies and working files go into the destruction flow. Forgetting to lift the lock is a common mistake. The result: the application leads to the data subject’s data being kept longer than necessary.
- The application date, channel and number have been logged
- Identity and the person in the footage have been verified
- The relevant cameras and time range were locked on day one
- Camera and VMS clocks have been checked
- The review was done by an authorized role and appears in the audit trail
- Third parties were masked, and the copy was checked by a second person
- Hash values of the original and masked files have been recorded
- The response was sent within the legal period, with reasons
- The recording lock was lifted, and working files were destroyed
Recordings exported for an internal incident investigation follow a different process; this distinction is explained in the camera recording chain of custody guide. We handle turning the application process into a procedure under KVKK camera monitoring and privacy notice processes, and setting up permissions for locking, reviewing and exporting recordings together with our recording access rights and audit trail work. For the deletion steps at the close of the process, the recording retention and destruction policy should be the reference.
Frequently asked questions
Is it mandatory to provide a copy of the camera recording in response to a KVKK application?
Article 11 of KVKK gives a person the right to learn whether their data is being processed and, if so, to request information; whether the request is met with a copy, viewing on site or written information is assessed on the facts of the case. If other people appear in the recording, their rights are also taken into account. Get your legal advisor’s opinion for the decision.
What should be done if the retention period is about to expire when the application arrives?
As soon as the application is logged, the relevant camera and time range are locked in the VMS to protect them from loop deletion. The lock is kept only for the purpose of answering the application; when the process closes, it’s lifted and the recording is left to the normal destruction flow.
Within how many days must a camera recording request be answered?
Under Article 13 of KVKK, the data controller concludes the application as soon as possible according to the nature of the request, and within thirty days at the latest. Because camera recording retention periods are often shorter than this, secure the recording on the first day.
Can a recording be given to an applicant whose identity can’t be verified?
No. Sharing footage without reasonably verifying both the applicant’s identity and that they’re the person in the image risks disclosing someone else’s personal data to an unauthorized person. In this case, additional information is requested, or the option of viewing on site on presentation of ID is offered.