Purpose and scope
The purpose is to explain which browser-side technologies may operate when the public website or protected areas are used, why they are needed and how a visitor can manage them.
What is a cookie?
A cookie is a small text value stored or read by a browser for a website or its infrastructure. Similar technologies include local or session storage, although these are technically different from cookies.
Current technology inventory
The application source does not currently write advertising or analytics cookies and does not use localStorage or sessionStorage for public-page preferences. The hero film and images are served from the same website; there are no third-party video, map or social-media embeds on the public pages.
Strictly necessary security cookies
The current review environment uses Cloudflare hosting and security infrastructure. That layer may set a short-lived, strictly necessary security cookie such as __cf_bm to distinguish legitimate traffic and protect the service from automated abuse. It is controlled by the infrastructure provider, not used by Ladik for advertising and is presently observed with a limited expiry.
Authentication and protected areas
The data room and administration areas use an authentication flow provided by the hosting environment. If an authorised user enters those areas, essential session or security technologies may be used to maintain authentication and enforce access control. These technologies are not used on behalf of Ladik for behavioural advertising.
Preferences and device storage
The current public implementation does not persist language choice, motion preference or form content in localStorage or sessionStorage. Language is represented in the page URL; reduced motion follows the device or browser preference through CSS.
Analytics, advertising and social tracking
No analytics platform, advertising pixel, behavioural profiling cookie or social-media tracking script is activated in the current public implementation. If that changes, this policy and any required consent mechanism must be updated before activation.
Duration and control
Necessary security and authentication technologies may be session-based or short-lived, with duration determined by the relevant infrastructure provider. Visitors can inspect, block or delete cookies through browser settings. Blocking necessary cookies may prevent protected areas or security checks from working correctly.
Consent approach
Because the current implementation uses only necessary security and authentication technologies and no non-essential tracking, it does not display a decorative consent banner. This describes the technical state only and is not a general legal conclusion for future integrations.
Changes and contact
This inventory should be reviewed whenever analytics, embeds, authentication or hosting changes. Questions may be sent to cem.ogut@ladikglobalmarketing.com.tr. Last updated: 26 August 2026.