Cookie Policy

Cookies and localStorage

Cookies and localStorage are different browser mechanisms. Cookies can be sent to a server with HTTP requests; this site keeps its theme preference in browser localStorage.

Current storage behavior

There is no first-party application cookie and no third-party runtime embed. Only the theme preference is stored in localStorage under the “theme” key, and it is not used for advertising or profiling.

Clearing the theme preference

You can clear the theme preference in your browser’s site-data settings. Removing it returns theme behavior to your system preference.

Consent banner and change review

For the current no-cookie implementation, no cookie consent banner is needed. 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, map, video embed, marketing tracker or health-data collection field is implemented.

The application intentionally stores only the user’s theme choice in browser localStorage under the “theme” key; this preference is not used for profiling or advertising.

The application does not intentionally set its own HTTP cookies. Therefore no consent banner is shown for the current no-cookie implementation.

External links and direct email

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

Direct email is handled outside the site by the user’s email client and provider, without an on-site form. Do not send personal health information by email.

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.