This text is a draft based on the site’s current contact and data flows. It must not be treated as a final notice until the clinic representative and qualified legal adviser verify the controller identity, application channel, retention periods and international-transfer status.
Cookies and technical storage içeriği
01 / What is a cookie?
What is a cookie?
A cookie is technology that stores a small piece of information in a browser or device so it can be read on later visits. localStorage, sessionStorage or other device identifiers can serve similar purposes.
Cookies may be strictly necessary, preference-based, measurement, advertising or other technologies. Each category must be assessed by provider, purpose, duration and first- or third-party status.
02 / Site behaviour
Which tools are used in this version?
The local JavaScript used for the menu, page motion and video control uses no cookie, browser storage, analytics tool, advertising SDK, pixel, iframe or third-party measurement tag. There is therefore no analytics or advertising consent banner for an unused technology.
03 / Cookie inventory
Cookie and storage inventory
The table separates behaviour detected in the application source from items requiring production-provider verification. “Not detected in source” describes the site application, not every provider layer.
| Technology | Category | Purpose / duration | Status |
|---|---|---|---|
| Application cookie | First party | No purpose or duration defined by the application. | Not detected in source. |
| localStorage / sessionStorage | Browser storage | No purpose or duration defined by the application. | Not detected in source. |
| Analytics / advertising tag | Usually third party | No code for measurement, profiling or advertising. | Not detected in source. |
| Hosting or security identifier | Provider-dependent | Not used by the application; the production service may have its own technical purpose. | Production-provider verification required. |
“Not detected in source” describes the site application. Possible technical behaviour in the provider layer must be verified separately.
04 / Hosting and security
Hosting and security identifiers
The production account, connected security services and possible identifiers cannot be determined from this page. If a security cookie or identifier is used, its name, purpose, duration, provider and any international transfer must be added after checking current provider documentation and account settings. Optional measurement or advertising technology requires an appropriate information and preference mechanism before activation.
05 / Analytics and advertising
Analytics, profiling and advertising
This version contains no Google Analytics, Google Tag Manager, advertising network, remarketing tag, social-media pixel or remote script measuring visitor behaviour. No automated decision, profiling or personalised advertising flow was detected. Any change requires redesign of the data flow, provider, transfer, legal ground, inventory, notice and consent withdrawal mechanism.
06 / Browser controls
Browser settings
Most browsers allow cookies to be viewed, deleted, blocked or limited by site. Settings vary and blocking cookies may affect technical functions. This version has no application-defined preference cookie or preference panel. External services apply their own settings outside this site.
07 / Updates and approval
Updating the policy
The technical inventory and KVKK assessment must be renewed before adding analytics, advertising, embedded content, a security layer or provider cookie. This draft was recorded on 23 October 2026 and remains subject to hosting-provider and authorised clinic verification.