What cookies are, which types this website and the QliqSOFT platform use, and how to control them. Companion documents: the Privacy Policy, App Privacy Policy, and Terms of Service.
Last updated: August 11, 2026
This Cookie Policy explains how QliqSOFT uses cookies and similar browser-storage technologies, and the choices you have. It covers three places you may encounter our technology:
We do not use advertising or targeting cookies anywhere, and we do not sell or share personal information for cross-context behavioral advertising. For how we handle personal information generally, see our Privacy Policy; for the mobile and web applications, see the App Privacy Policy.
For the purposes of this Cookie Policy:
This website is built to work without cookies. Browsing the site sets none. We host our own fonts, we run no advertising pixels, and we currently run no analytics at all.
The complete list of storage this website can create:
| Name | Type | Set by | Purpose | Duration |
|---|---|---|---|---|
| qs-consent | localStorage | Us | Records the analytics choice you make in our consent banner ("yes" or "no"), so we don't ask again. Created only after you make a choice. | Until you clear it |
| _GRECAPTCHA | Cookie (third party) | Google reCAPTCHA | Fraud and abuse prevention on our contact and demo forms, when reCAPTCHA protection is active. Google's use is described in the Google Privacy Policy. | ~6 months |
If we ever enable analytics on this website, it will load only after you accept in the consent banner, and this table will be updated to name the vendor and its cookies before that happens.
blog.qliqsoft.com. Our blog uses a privacy-focused analytics service (Datafast) whose vendor states it operates without cookies, and stores reading preferences you create - bookmarks and highlights - in your browser's localStorage. These stay on your device and are not transmitted to us.
The signed-in QliqSOFT applications use first-party cookies that are strictly necessary or functional - they sign you in, keep you signed in, secure your account, and remember your preferences. The platform contains no analytics, advertising, or social-media tracking cookies.
| Name | Purpose | Category | Duration |
|---|---|---|---|
| _session_id | Keeps you signed in during a session (identifies your server-side session). | Strictly necessary | 1 day |
| jwt | Completes single sign-on from partner health systems. | Strictly necessary | 6 hours |
| _api_web_key | Administrative dashboard session (QliqSOFT staff only). | Strictly necessary | 1 hour |
| device_uuid | Recognizes a device you have used before, to support two-factor authentication and block suspicious sign-ins. | Security / functional | 365 days |
| fingerprint | Recognizes a returning device in patient chat so your conversation can continue securely. | Security / functional | 30 days |
| short_url_hash, app_id, mid | Let a patient chat opened from a secure link survive a page reload. | Strictly necessary | Browser session |
| kiosk_visitor_uuid, prev_kiosk_visitor_uuid | Keep the right visitor's session active on shared check-in kiosks. | Strictly necessary | Browser session |
| language_selected | Remembers your language choice in patient chat. | Functional | 365 days |
| use_prerelease_app | Remembers which version of the application to show you. | Functional | Browser session |
| Per-screen paging preferences | Remember your rows-per-page choices on administrative screens. | Functional | Browser session |
The platform also uses browser storage (localStorage and sessionStorage) on your device for session continuity - for example your sign-in session, language and accessibility preferences, and short-lived caches of your own conversations so a page reload doesn't lose your place. This data stays in your browser, is removed by signing out or clearing browser data, and is never used for advertising.
Third-party services inside the platform. Some features rely on service providers that may set their own cookies or storage, strictly to deliver the feature:
Healthcare organizations can embed the QliqSOFT patient-chat widget on their own websites. The widget runs in a frame served from our domain: it does not read or write cookies on the host site, and the host site cannot read the widget's data. Inside the frame, the widget uses the platform cookies and browser storage described above - on the host organization's website these count as "third-party" storage from QliqSOFT. Modern browsers may isolate ("partition") that storage for each host website, so the widget can behave as a fresh session on each organization's site. If you use a chat widget on a healthcare organization's site, that organization's own privacy notice and cookie choices apply alongside this policy.
Consent banner. If optional analytics are enabled on this website, we ask before loading them, and you can say no with one click. Essential platform cookies do not require consent because the services you request cannot work without them.
Global Privacy Control. We honor the Global Privacy Control (GPC) signal: if your browser sends it, we treat it as a "no" to optional analytics without showing you a banner.
Browser controls. You can block or delete cookies in your browser settings. Blocking strictly necessary cookies will prevent sign-in and patient chat from working.
If you are in a jurisdiction that requires consent for non-essential cookies (for example the EEA or UK), we rely on your consent for any optional analytics and on legitimate interest / necessity for the essential cookies above.
If you have questions about this Cookie Policy or want to exercise a privacy right, contact us: