This is the personal website and blog of Muhammed Ulvi Özkaya, available at muhammedozkaya.com. This page explains what information is — and what isn't — processed when you visit.
This site is hosted on Vercel, and the blog is served by a separate backend API.
As with most web services, the hosting provider and related infrastructure services may automatically generate certain technical logs for security, debugging, abuse prevention, and system performance purposes. These logs may include information such as IP address, browser details, request timestamps, and similar technical data.
These logs aren't used by me for visitor profiling or behavioral tracking. The processing and retention of this data is governed by the relevant service providers' own policies.
No cookies are used for site visitors.
That said, the /admin page is a login-protected panel used only by me. After a successful login, an authentication token may be stored in the browser's local storage for authentication purposes. This applies only to administrator sessions and doesn't constitute a data-collection activity for regular visitors.
The site may contain links to external platforms such as LinkedIn, GitHub, Instagram, and similar.
Third-party sites visited through these links operate under their own privacy policies. I'm not responsible for their data-handling practices.
This site isn't designed for children. No personal data is knowingly collected from visitors, regardless of age.
If you have questions about technical server logs or this policy, you can contact me at the address below.
This privacy policy may be updated from time to time. If new features are added to the site or data-processing activities change, this page will be updated and the "Last updated" date above will be refreshed.
For questions about this policy: ozkayamuhammed17@gmail.com
In its current form, this site doesn't directly collect personal data from visitors and doesn't carry out systematic user profiling. That said, technical server logs generated through hosting and infrastructure providers are subject to those providers' own processes.
The scope of applicable obligations (e.g., under GDPR or Turkey's KVKK) may be reassessed if how the site operates changes in the future.