Skip to main content
DiaDeep
BIOMARKER SCORINGDiaKwant®Biomarker quantification↗︎
PD‑L1CPS and TPSHER2BreastKi‑67BreastER / PRBreastMitosisH&E
RECURRENCE RISK*DiaSurv®Prognostic risk↗︎
MelanomaEarly-stageColorectalStage II
TREATMENT RESPONSE*DiaThera®Therapeutic response↗︎
PATHOLOGISTSPathologistReview the score against the slide before you report it.↗︎CLINICIANSClinicianExplore the evidence relevant to biomarker results, recurrence risk and treatment benefit.↗︎RESEARCH PARTNERSResearch partnerConnect your clinical question with a prognosis or treatment-response project.↗︎
RESOURCESCLUB QUANTIABOUT
Try it on your cases ↗︎Contact us ↗︎
MENU
HomePRODUCTS
DiaKwant®PD‑L1 CPS and TPSHER2 BreastKi‑67 BreastER / PR BreastMitosis H&E
DiaSurv®Melanoma Early-stageColorectal Stage II
DiaThera®I AMPathologistClinicianResearch partnerResourcesClub QuantiAboutTry it on your cases ↗︎Contact us ↗︎

LEGAL · COOKIES

Cookiepolicy.

How DiaDeep uses essential and analytics cookies on its website and CPS Trainer Platform.

Effective date: September 24th, 2026

  • Part I, Cookie Policy for the DiaDeep corporate website
  • Part II, Cookie Policy for the CPS Trainer Platform
  • Cookie management
  • Updates to this policy
  • Contact

This Cookie Policy explains how DiaDeep SAS (“we”, “us”, or “our”) uses cookies and similar technologies on:

  • the DiaDeep corporate website (hereafter “Website”); and
  • the CPS Trainer Platform (hereafter “Platform”).

It provides clear information about the types of cookies used, their purpose, and your rights to control their use. For information about how we process your personal data, please refer to our Privacy Policy.

A cookie is a small text file stored on your device (computer, tablet, or smartphone) when you visit a website. Cookies help the website recognize your device and store certain information about your preferences or previous actions.

Part I, Cookie Policy for the DiaDeep corporate website

1. What types of cookies do we use?

We use two categories of cookies on the Website: strictly necessary cookies, which are exempt from prior consent under Article 82 of the French Data Protection Act (transposing the ePrivacy Directive) because they are essential to the Website’s operation, and analytics cookies, which are only placed once you have given your consent via the cookie banner. Where a cookie does process personal data, that processing separately relies on the legal bases described in our Privacy Policy.

Strictly necessary

Cookie name Description Type Duration Purpose
_cfuvid Set by Cloudflare when a site uses a Rate Limiting Rule. It allows Cloudflare’s Web Application Firewall (WAF) to distinguish between users who share the same IP address. Third-party (Cloudflare), strictly necessary Session, expires when the session ends Ensures fair rate limiting per user. Without this cookie, users from shared IPs may be blocked or misidentified by the WAF.
diadeep-cookie-consent Stored in your browser’s local storage (not a cookie) to record the choice you made in the cookie banner. First-party, strictly necessary Persistent, until you clear it or withdraw consent Remembers your consent choice so the banner is not shown again on every visit, and so we know whether analytics cookies may be set.

Analytics (subject to consent)

Cookie name Description Type Duration Purpose
_ga Set by Google Analytics to distinguish unique visitors. Third-party (Google), analytics 2 years Helps us understand how visitors use the Website in aggregate, so we can improve it.
_ga_<container-id> Set by Google Analytics (GA4) to persist session state. Third-party (Google), analytics 2 years Used together with _ga to build session and usage statistics.
hubspotutk Set by HubSpot to identify a visitor across sessions and attribute form submissions. Third-party (HubSpot), analytics 13 months Lets us connect a contact-form submission to the visit(s) that led to it.
__hstc Set by HubSpot to track visitor identity, session count and timestamps across visits. Third-party (HubSpot), analytics 13 months Used together with hubspotutk to build session and usage statistics.
__hssc Set by HubSpot to determine whether a new session has started. Third-party (HubSpot), analytics 30 minutes Session-level analytics, refreshed on each page view.
__hssrc Set by HubSpot to detect whether the browser has been restarted. Third-party (HubSpot), analytics Session, expires when the browser is closed Session-level analytics.

No advertising or retargeting cookies are used.

2. How do we use cookies?

We use strictly necessary cookies to:

  • ensure fair rate limiting per user.

If you accept analytics cookies, we also use Google Analytics to understand how the Website is used (pages visited, general traffic patterns) in order to improve it. Analytics cookies are only set after you accept them via the cookie banner, and you can withdraw your consent at any time using the “Manage cookies” link in the footer of any page, which reopens the banner with your current choice preselected.

We do not share cookie-derived data with third parties for marketing purposes.

Part II, Cookie Policy for the CPS Trainer Platform

1. What types of cookies do we use?

We use strictly necessary cookies. These cookies are exempt from prior consent under Article 82 of the French Data Protection Act (transposing the ePrivacy Directive) because they are essential to provide authentication and security features for the CPS Trainer Platform. No third-party tracking cookies or advertising technologies are employed.

Cookie name Description Type Duration Purpose
__session Custom session cookie used to store Firebase ID tokens (JWT) after sign-in. HTTP Cookie (Secure) Configurable, 5 minutes to 14 days Maintains authenticated sessions across page loads. Required for persistent sign-in.
firebase-authentication-session Session-only authentication data used internally by Firebase SDK. Local Storage / IndexedDB Session Supports user login sessions in the browser for seamless navigation.
firebase-authentication-redirect Temporarily stores data during OAuth redirects, such as Google login. Session Storage Session Manages redirect-based sign-in flows securely and reliably.
g_state Used by Google identity providers, for example to manage OAuth state during sign-in. First-party cookie Short-lived Necessary for the integrity of the authentication process using Google Identity.

2. How do we use cookies?

We use cookies to:

  • enable secure login and session continuity;
  • remember user preferences.

We do not use cookies to collect personal data without your explicit consent, nor do we share cookie-derived data with third parties for marketing purposes.

Cookie management

You may configure your browser settings to refuse such necessary cookies. However, this may affect the proper functioning of the Website or the Platform.

For browser-specific instructions:

  • Chrome
  • Firefox
  • Safari
  • Edge

Updates to this policy

We may update this Cookie Policy from time to time to reflect changes in law or how we use cookies. The latest version will always be available on this page with the effective date indicated.

Contact

If you have any questions regarding our use of cookies or this policy, please contact:

Data Protection Officer (DPO)
By mail for the attention of the DPO: 24 rue du Dauphiné, 69003 Lyon, France
Email: dpo@diadeep.com

© 2026 DiaDeep. All rights reserved.

PrivacyCookie policyTerms of useLegal notice