Cookie Policy

Cookies and browser storage

Cookies can be sent to a server with HTTP requests; localStorage and sessionStorage are browser-side storage mechanisms.

Current storage behavior

The application does not set first-party cookies or write data to localStorage or sessionStorage. The contact page includes a third-party Google Maps embed.

Consent banner and change review

The application has no cookie consent banner. Cookie behavior of the Google Maps embed and any necessary preference mechanisms are within the scope of prelaunch review. Any hosting or CDN change, new cookie, runtime embed or tracker must trigger a joint review of the technical implementation and this policy before it is introduced.

Current repository implementation

No account, login, backend database, contact, appointment, symptom or upload form, analytics, advertising pixel, social embed, video embed, marketing tracker or health-data collection field is implemented.

The application does not write theme or other preference data to localStorage or sessionStorage.

The application does not intentionally set its own HTTP cookies. The Google Maps embed on the contact page may use third-party cookies.

When the Google Maps embed on the contact page loads, the browser connects to Google servers. Google may process technical data such as IP address and browser information under its own privacy policy and may use cookies.

Guide search runs in this page’s browser memory. Search text is not sent to a search server, added to the URL or saved in browser storage.

External links and request channel

After the user follows a hospital, MHRS, LinkedIn, DOI, PubMed, PMC or AVESİS link, that external site’s own data practices apply.

A channel for personal-data requests is not yet published on this site. The request channel is pending confirmation.

Hosting logs and prelaunch review

A hosting provider may process necessary access and security logs such as IP address, request time and path, and user agent. This repository defines no provider, retention period, transfer geography or logging configuration; these choices must be configured and documented before production launch.

These texts describe the current repository implementation and still require review by qualified Turkish health-law and KVKK counsel before launch; they do not certify or guarantee legal compliance.