Cookie Policy

This Cookie Policy explains how CLARUS® ("CLARUS", "we", "us") uses cookies and similar technologies across claruslis.com, your lab's <subdomain>.claruslis.com workspace, and our customer portal. It should be read together with our Privacy Policy and Terms of Service.

Our philosophy is simple: a Laboratory Information System is built on trust, so we use only the cookies needed to sign you in safely, protect your session, and remember the preferences you choose. We do not run third-party advertising and we do not track you across other websites.

Effective / last updated: 2026-06-26. Governing law: the Arab Republic of Egypt, while preserving any mandatory consumer-protection rights you have under the law of your own country.

1.What Cookies and Similar Technologies Are

A cookie is a small text file that a website asks your browser to store on your device. When you return, your browser sends that file back, so the site can recognize your session, keep you signed in, and remember choices you made. Cookies cannot run programs, read other files on your device, or carry viruses; they simply hold short pieces of data such as a session reference or a language code.

"Similar technologies" covers a few related mechanisms we may use for the same purposes: local storage and session storage (browser stores that hold preferences or a short-lived session token on your device), and small first-party measurement signals that tell us a page loaded successfully. Where this policy says "cookies", we mean cookies and these equivalent technologies together.

Cookies can be distinguished by who sets them and how long they last. First-party cookies are set by CLARUS® itself; we do not permit third-party advertising cookies on our platform. Session cookies are deleted when you close your browser, while persistent cookies remain for a defined period (for example, to remember your language) until they expire or you clear them.

• First-party vs. third-party: CLARUS® sets its own cookies; we do not allow third-party ad/tracking cookies.
• Session vs. persistent: session cookies clear when you close the browser; persistent cookies expire after a set time or when you clear them.
• Strictly necessary vs. optional: necessary cookies make the service work and cannot be switched off; preference and analytics cookies are limited and privacy-respecting.

2.Our Approach — Privacy by Design, No Advertising, No Cross-Site Tracking

CLARUS® is a healthcare platform used by medical laboratories to process patient and health data. For that reason we deliberately keep our use of cookies minimal and purposeful. We do not display advertising on the platform, we do not embed advertising or social-media tracking pixels, and we do not build cross-site behavioral profiles of you. We never sell or rent any data, and we never use patient/health data for marketing or analytics.

It is important to separate two roles. For the patient and health data your lab processes inside CLARUS®, your laboratory is the data Controller and CLARUS® is the Processor acting only on the lab's documented instructions — and that clinical data is governed by our Privacy Policy and Data Processing terms, not by this Cookie Policy. The cookies described here relate to operating the application interface (signing in, securing your session, remembering your locale), not to the clinical records themselves.

Any analytics we perform are aggregate, first-party, and privacy-friendly (see Section 5). We design for data minimization: if a cookie is not needed to deliver the service securely or to honor a preference you set, we try not to use it at all.

3.Strictly Necessary Cookies (Session, Authentication, Security)

These cookies are essential. They make it possible to sign in, keep your session active and isolated to your lab's tenant, and protect you against common web attacks. Because they are required to deliver a secure service you have requested, they are set without separate consent and cannot be disabled through an in-app toggle. If you block them in your browser, core functions such as login and saving work will not operate.

We keep these strictly necessary cookies scoped to first-party use only, mark them as Secure (sent over HTTPS only) and HttpOnly where applicable (so they cannot be read by page scripts), and apply SameSite protections to reduce cross-site risk. Session and authentication tokens are short-lived and tied to per-tenant isolation and role-based access control.

• Session cookie — maintains your authenticated session and keeps you connected to the correct lab tenant during a visit.
• Authentication / sign-in cookie — confirms you are logged in and, where you opt in, supports staying signed in across the session.
• CSRF / anti-forgery token — protects forms and actions from cross-site request forgery so commands genuinely come from you.
• Security and integrity cookies — support secure transport, two-factor authentication flows, rate-limiting, and abuse/fraud prevention.
• Load-balancing / routing cookie — directs your requests to the correct service node so the application stays fast and reliable.

4.Functional / Preference Cookies (Language and Currency)

Functional cookies remember the choices you make so CLARUS® behaves the way you expect on every visit, without asking you to set things up again. CLARUS® serves a regional audience across MENA and Africa with an interface available in eight languages and multi-currency display, so two preferences matter most: your language/locale and your currency display. These cookies hold only your chosen setting — for example a language code such as "ar" or "fr", or a display-currency code — and contain no health or personal account content.

Note the distinction between display and settlement: a currency-display preference changes only how prices are shown to you. Billing and settlement are performed in Egyptian Pound (EGP) regardless of the display currency you select; the cookie does not change what you are charged. If you decline functional cookies, the service still works, but it may default to a fallback language (English) or a default currency display and forget your selection between visits.

• Language / locale preference — stores your chosen UI language and reading direction (RTL/LTR) across the 8 supported languages, defaulting to English if unset.
• Currency display preference — remembers the currency used to show prices for readability; settlement remains in EGP and is unaffected.
• Interface/state preferences — remember non-sensitive layout choices, such as a collapsed sidebar or a selected tab, to keep your workspace consistent.

5.Analytics / Performance Cookies

To keep CLARUS® fast, stable, and easy to use, we measure how the application performs in aggregate — for example, which pages load slowly, where errors occur, and broadly how features are used. This analytics is privacy-friendly by design: it is first-party, reported in aggregate, and is never used to advertise to you or to build a personal profile. We do not sell, rent, or share analytics data with advertising networks.

We apply data minimization to measurement: we avoid capturing unnecessary identifiers, we do not include patient or clinical record content in analytics, and where feasible we truncate or pseudonymize technical identifiers such as IP addresses. The goal is operational quality and security monitoring, not surveillance.

Where applicable law treats these analytics cookies as non-essential, we present them as optional and honor your choice; declining them does not reduce the security or core functionality of the service.

6.How to Manage or Clear Cookies

You are always in control of cookies through your browser. Every major browser lets you view stored cookies, delete them, and block some or all of them, either globally or for specific sites such as claruslis.com. You can also use private/incognito windows, which typically clear cookies when the window closes. Consult your browser's help pages for the exact steps.

Please be aware of the trade-off: if you block or clear strictly necessary cookies (Section 3), essential features will break — you may be unable to sign in, your session may drop unexpectedly, secured forms may be rejected, or saved work may fail to submit. Blocking functional cookies (Section 4) means CLARUS® may forget your language and currency-display preferences between visits and fall back to defaults. Because of this, we recommend allowing first-party essential and functional cookies for the CLARUS® domain even if you restrict cookies elsewhere.

• Use your browser settings to view, delete, or block cookies for claruslis.com specifically or for all sites.
• Clearing cookies signs you out and resets saved preferences such as language and currency display.
• Blocking strictly necessary cookies disables login, secure sessions, and saving work; functional and analytics cookies can be declined with limited impact.
• Private/incognito browsing usually discards cookies when the session ends.

7.Do-Not-Track and Consent

Where the law of your country requires consent for non-essential cookies, we ask for it before setting functional or analytics cookies, record your choice, and let you change your mind at any time through your browser controls or any in-app cookie settings we provide. Strictly necessary cookies are exempt from consent because they are required to deliver a service you have actively requested, such as logging in securely.

"Do Not Track" (DNT) is a browser signal indicating you prefer not to be tracked across sites. Because there is no consistent industry standard for how DNT must be interpreted, we instead take the stronger position of not engaging in cross-site advertising or behavioral tracking at all — regardless of whether your browser sends a DNT signal. Withdrawing consent or clearing cookies does not delete the patient/health records your lab stores in CLARUS®, which are governed separately by the agreement between CLARUS® and your laboratory.

8.Changes and Contact

We may update this Cookie Policy as our technology, security practices, or legal obligations evolve. When we make material changes we will revise the "last updated" date above and, where appropriate, give additional notice within the platform. We encourage you to review this page periodically so you remain informed about how we use cookies.

If you have questions about this policy or about cookies and your privacy on CLARUS®, we are glad to help. You can reach us by email or through in-app live chat, and we aim to respond promptly and clearly.

• Privacy questions: privacy@claruslis.com
• Data Protection Officer: dpo@claruslis.com
• General support: support@claruslis.com (or in-app live chat)
• Legal: legal@claruslis.com

9.Cookies We Use & How Long They Last

For transparency, this section summarises the cookies and similar technologies CLARUS® may set, grouped by the categories described above. We keep durations as short as the purpose allows, and we do not use advertising or cross-site tracking cookies.

• Strictly necessary — session & authentication tokens: session-based or short-lived (they expire when you close your browser or after a short period of inactivity, typically up to 24 hours).
• Strictly necessary — CSRF / anti-forgery token: lasts for the session only.
• Strictly necessary — load-balancing / routing: session-based.
• Functional — language/locale and currency-display preference: persistent, typically up to 12 months, until you change or clear it.
• Analytics / performance: aggregate and privacy-friendly, typically retained no longer than 12 months; no advertising use.