Personal Data Notice (PDPL)

Data controller / site editor

This draft notice identifies the site editor as the contact point. The production data-controller role and its obligations must be verified through qualified legal review before launch.

Data categories

If enabled at the hosting layer, access and security logs may include IP address, request time and path, and user agent.

Purposes

Possible technical logs may be processed only as necessary to deliver and secure the site.

Collection method and legal basis

The collection method for hosting logs and the legal basis applicable to each processing activity must be reviewed, selected and documented against the production configuration before launch. This notice does not request consent.

Recipient categories

Possible recipients include configured hosting or technical providers. When the contact page map loads, the browser also connects to Google servers.

Rights under Article 11

Where the statutory conditions apply, data subjects have the rights below. The request channel is pending confirmation; this site does not receive requests until a confirmed channel is published.

• Learn whether their personal data is processed.
• Request information if their personal data has been processed.
• Learn the purpose of processing and whether the data is used in accordance with that purpose.
• Know the third parties to whom personal data is transferred domestically or abroad.
• Request correction where personal data has been processed incompletely or incorrectly.
• Request deletion or destruction of personal data under the conditions set out in Article 7.
• Request notification of correction, deletion or destruction to third parties to whom personal data has been transferred.
• Object to a result adverse to the person arising from analysis of processed data exclusively through automated systems.
• Claim compensation for actual damage incurred because personal data was processed unlawfully.

Notice and explicit consent are separate

This site has no form that collects personal or health data and currently requests no explicit consent. If a future processing activity requires consent, notice and explicit consent must be designed as separate processes.

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.