This draft describes the new website’s technical cookie use. The hospital must verify the controller’s identity, legal bases and the notice to be published. The old website’s archived text does not by itself describe how the new platform works.
This draft describes the new website’s technical cookie use. The hospital must verify the controller’s identity, legal bases and the notice to be published. The old website’s archived text does not by itself describe how the new platform works.
The __Host-nev_patient cookie is a random identifier linking an online appointment or patient portal session to the server. Passwords and medical reports are not stored in the cookie. On HTTPS deployment, it is set for up to 20 minutes with Secure, HttpOnly and SameSite=Strict.
The nev-form-session cookie helps verify that a form submission comes from the same browser session. It is valid for up to 30 minutes on the /api/forms path. Form answers are not stored in it; it is not used for advertising or visitor profiling.
A separate administrative session cookie is used when authorised staff sign in. This session is separate from the patient portal session and does not grant administrative access to public visitors.
The current application code includes no advertising cookies, behavioural analytics or Flash cookies. Language is selected through the URL. Opening a map, video or social network link takes you to a service with its own terms; following a link does not book an appointment.
If optional tracking tools are added later, this text and the preference mechanism must be reassessed. Continuing to browse is not recorded as general consent to marketing or tracking.
You can delete or block cookies in your browser settings. Blocking session and security cookies may prevent sign-in, booking or form submission. On a shared device, sign out and close the browser after use.
