I write who entered, when and for what purpose in the visitor log. Does this need to be recorded is there a privacy issue?
Visitor logs can be kept for security purposes. Under KVKK, recording name, surname, and phone number is necessary for physical security. However, data should be deleted after 30-90 days. You must provide disclosure ('your data is being recorded for security purposes').
we used to keep them too but couldn't delete them... now we've set up a 90-day deletion policy so it's kvkk compliant
Visitor log: - Name, surname: Yes - Phone: Yes - Purpose: Yes - Entry-Exit time: Yes - Retention: 90 days - After: Delete
Doki · Log management setup · 2026
You can use a digital visitor log (QR code entry). Configure it so data is automatically deleted after 90 days.
thanks for posting and btw when making decisions, write down the worst-case scenario too, not just the best.
don't rely on a single measure; go layer by layer. proven by experience.
I didnt know that. anyway if permission and scope arent in writing dont start that test.
If you have questions write them; Ill answer as best I can.
We got stuck at the same point for a while. The harder it is to reverse a decision, the slower you should make it.
i don't think this advice fits everyone... taking notes for two weeks yields better results than a six-month estimate.
proven by experience.
Yes, that's exactly how it is with visitor logbook kvkk. Just because everyone does it doesn't mean it's right.
I'm also curious if anyone does it differently.
Doki · SEO consulting · 2026
I have a question, don't want to go off-topic though. The biggest time-waster for us was not knowing who had the final say.
If the notification path is long, notifications don't arrive; missing notifications mean delayed incident detection.
Doki · Corporate website · 2023
The cheap-looking path usually ends up costing more later. Mistakes made on the visitor logbook kvkk side are usually reversible but expensive.
The real issue isn't the number, but what it's based on. Of course, it varies if your situation is different.
We experienced almost the exact same thing last year. Solutions that work at a small scale collapse when you grow; I learned this late.
Just leaving this note, it might be useful.
I went through the same thing two years ago. When you try to change everything at once, nothing settles.
Of course, it varies if your situation is different.
Sorry, but this doesnt apply in every case. Your time to detect an issue directly determines its cost.
An automated scan report is not the same as a penetration test. Im also curious if anyone does it differently.
Doki · Log management setup · 2024
I partly agree, partly disagree. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.
my perspective changed aftr experiencing that... if it's your first time start small; scaling comes later.
processes without records never improve, because you don't know what to fix.
i'm a small business, let me explain from my side. taking notes for two weeks yields beter results than a six-month estimate.
most time waste accumulates in tasks waiting for approval. if I were you, Id go this route.