Cookie policy

Why you see no consent banner

A consent banner is asked for when a page stores something its work does not need: analytics, advertising, behaviour measurement. None of that exists here, so there is nothing to ask you about.

If we ever add a tool that measures something, we will ask before it runs rather than after, and this document will change the same day.

The sign-in cookie

When a clinic's staff sign in, the session is kept in a cookie no script in the browser can read. Its job is to let you move between the system's screens without being asked for a password on every page, and it is strictly necessary: without it, signing in cannot work at all. It is never written for a visitor who has not signed in.

The support-ticket cookie

It is called atmta_support_session, and it is written only after you enter a ticket number and its correct code. Its job is to let you read your ticket's conversation and reply to it without an account.

It lasts twenty-four hours and then expires by itself, no script in the browser can read it, and it carries neither your name nor the text of your message — only a signed permission to read one ticket.

The language is in the URL, not in a cookie

Arabic and English are two different addresses: /ar and /en. Switching language is a move to the other address, so we store no preference in a cookie, and you can share a link in the language it was read in.

And nothing here is loaded from another domain

The fonts, the video and the images are all served from this site. No fonts from an outside service, no video player from another site, no social share button, no measurement pixel. Any request your browser makes on these pages goes to us and to nobody else.

How to block them

From your browser's settings, and we do not have to change anything for you to do it. But each has a plain cost: blocking the sign-in cookie means signing in cannot complete, and blocking the tracking cookie for tickets means entering the ticket number and code again every time.