Privacy Policy

Scope

This policy describes data-processing behavior implemented in the current source code of this static profile and academic-information site. Any future service requires the text and technical implementation to be reviewed together.

Limits of current processing

The theme preference remains in the user’s browser. Necessary access and security logs may exist only if configured at the hosting layer; when a user independently sends email, email providers process that message.

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.