Cookie Policy

This policy explains how Diagolia uses cookies and other trackers on the diagolia.com website and on the Diagolia platform.

On the public diagolia.com website, Google Analytics and persistent PostHog tracking are disabled by default. Basic cookieless PostHog audience measurement starts when the website loads. The tawk.to support widget remains available independently of that analytics choice and manages its own consent before chatting.

It supplements the Privacy Policy available at:

/legal/confidentialite/

1. What is a cookie?

A cookie is a small file placed on or read from a user's device, such as a computer, tablet or smartphone, when visiting a website or using an online service.

Cookies and similar technologies may serve several purposes, including enabling the technical operation of the service, maintaining a user session, securing account access, measuring audience or analyzing product usage.

2. Strictly necessary cookies

Diagolia uses cookies or trackers that are strictly necessary for the website and platform to operate.

These trackers may be used to:

• allow access to the user account;
• maintain the login session;
• secure authentication;
• remember certain necessary technical choices;
• ensure payment or subscription features work correctly;
• prevent abuse or unauthorized access;
• store the user's cookie choices.

These cookies are essential to the service and do not require the user's prior consent.

The user may technically block them from the browser, but some website or platform features may then stop working properly.

3. Audience measurement and product analytics cookies

Diagolia may use audience measurement or product analytics tools to understand use of the website and platform.

These tools may measure, for example:

• pages viewed;
• navigation paths;
• features used;
• errors encountered;
• service performance;
• actions performed in the application.

This information helps Diagolia improve the user experience, correct technical issues and evolve the product.

When these trackers are not strictly necessary for the service to operate, they are placed only with the user's consent, except where they meet the conditions for a consent exemption under applicable regulations.

On the public website, Google Analytics and persistent PostHog analytics are optional, disabled by default and enabled only if the user accepts the analytics category in the cookie preferences. Basic PostHog events remain active without browser persistence when that category is refused or no choice has yet been made.

4. Tools that may use cookies or trackers

Diagolia may use the following tools in particular.

Authentication and database

Diagolia uses technical services for account creation, authentication, session management and storage of data required for the platform to operate.

These services may use trackers that are strictly necessary to maintain the user session and secure the service.

Payment and subscription

Diagolia uses Stripe to manage payments and subscriptions.

Stripe may use cookies or trackers necessary for secure payment processing, fraud prevention and the proper operation of the subscription process.

Product usage analytics

Diagolia may use PostHog to understand product usage, measure certain events, improve usability and detect potential issues.

On the public website, PostHog is initialized in cookieless mode before a choice is made. In that mode, it does not store its analytics identifier in cookies or local/session storage, does not record sessions, and uses PostHog's privacy-preserving server hash to count visitors. Accepting analytics enables persistent PostHog measurement and session replay. Google Analytics remains disabled until that acceptance.

Live chat support

Diagolia may use tawk.to to provide a live chat widget on public landing pages. The widget is not loaded on the connected SaaS application, and this website integration does not send Diagolia account identifiers, internal identifiers or diagnostic case identifiers to tawk.to.

On the public website, the native tawk.to support widget remains available regardless of the analytics-cookie choice. tawk.to's own consent form is configured for European visitors so the widget does not set its cookies or local storage before the visitor accepts that form and starts using the chat.

5. Consent management

When a cookie or tracker requires user consent, Diagolia displays a mechanism allowing the user to:

• reject all optional cookies;
• accept all optional cookies;
• customize persistent analytics;
• change the choice later from the "Manage cookies" link in the footer.

Refusing non-essential cookies does not prevent access to the website or platform.

Cookies strictly necessary for the service remain active even if non-essential cookies are refused.

6. Changing or withdrawing consent

The user may change or withdraw consent at any time from the "Manage cookies" link available in the public website footer.

When analytics consent is withdrawn, Google Analytics, persistent PostHog storage and PostHog session replay are disabled. Basic cookieless PostHog audience measurement remains active.

Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.

7. Retention period for choices

The user's cookie choice may be stored for a maximum period of 6 months.

After that period, Diagolia may ask the user to express a choice again.

8. Cookie lifetime

Cookie lifetime depends on the cookie's purpose.

By way of indication:

• session cookies may expire when the browser is closed;
• cookies required for account operation may be stored for the time needed for the session or security;
• consent cookies may be stored for up to 6 months;
• audience measurement or product analytics cookies, when used, are stored for a limited period that is proportionate to their purpose.

Diagolia seeks to limit cookie retention periods to what is strictly necessary.

9. Browser settings

The user may also configure the browser to accept, refuse or delete certain cookies.

The method depends on the browser used.

Warning: blocking certain strictly necessary cookies may prevent access to the user account or disrupt normal operation of the Diagolia platform.

10. Indicative list of cookie categories

The exact list of cookies used may evolve depending on active tools and the website's technical configuration.

11. Contact

For any question about Diagolia's use of cookies or other trackers, you can contact Diagolia at:

hello@diagolia.com