Passer au contenu principal
Retour aux informations légales

Politique relative aux Cookies et Technologies Similaires

Quels cookies et technologies similaires nous utilisons, à quelles fins et pour combien de temps.

Effective date: July 2, 2026

1. Introduction

This document describes which cookies and similar technologies (local storage, session storage, etc.) the udalist.app Service uses, for what purposes, and for how long.

Information about the processing of personal data related to the operation of the Service is set out in the Privacy Policy. Capitalised terms not defined here have the meaning given in the Service's General Terms of Service.

2. Strictly necessary cookies (Udalist)

These cookies are essential for the core functionality of the Service (sign-in, language preferences, completing Google sign-up, storing your cookie consent choice). The Service cannot work properly without them. They are set automatically and do not require consent under § 89(3) of Act No. 127/2005 Coll., on Electronic Communications.

NamePurposeLifetime
UDALIST_LOCALESelected website languageper browser settings
UDALIST_CONSENTStored cookie consent preferencesup to 12 months
JWTSign-in (HttpOnly)per token validity
JWT_REFRESH_TOKENSession renewal (HttpOnly)per token validity
oauth_terms_consent_versionTerms acceptance during Google sign-up (HttpOnly)approx. 10 minutes
oauth_login_language_codeGoogle sign-in completion — language (HttpOnly)approx. 10 minutes
oauth_login_intentGoogle sign-in completion — action type (HttpOnly)approx. 10 minutes

3. Error monitoring (Sentry)

We use Sentry (Functional Software, Inc.) to detect and fix technical errors.

  • It collects error information (stack trace), browser/OS type, and the URL of the page where the error occurred.
  • Used solely to keep the Service reliable, not for marketing or profiling.
  • Details on the processing of personal data via Sentry are set out in the Privacy Policy and the List of Subprocessors.

4. Web analytics (Umami)

We use Umami (data.udalist.app) to measure traffic on our public website.

  • We collect aggregated visit data: page viewed, referrer (where you came from), time of visit, general browser/device type.
  • We do not use names, emails, or profiling.
  • Without consent: Umami runs in cookieless mode — we count anonymized page views only and do not set an analytics cookie.
  • With consent: Umami may set cookies (e.g. _umami) to recognize returning visitors and attribute marketing campaigns.

We use Google Ads conversion tracking via gtag.js and Consent Mode v2.

  • The gtag consent stub loads on every page with default-denied storage; gtag.js itself loads only after you grant marketing consent.
  • Typical cookies may include _gcl_* and third-party cookies such as IDE (see Google's privacy policy).
  • Purpose: measuring ad conversions and campaign performance.

6. Meta Pixel

We use the Meta Pixel (Facebook) to measure advertising campaigns.

  • Meta Pixel loads only after you grant marketing consent.
  • Typical cookies include _fbp and _fbc (see Meta's privacy policy).
  • Purpose: ad conversion measurement and campaign optimization.

You can change your cookie preferences at any time on the Cookie settings page or via the cookie banner when you first visit the site. You can accept all optional cookies, reject them, or choose categories individually.

8. Payments (Paddle)

We use Paddle (Merchant of Record) to process payments and subscriptions.

  • Paddle loads only when you start a payment or manage a subscription (checkout, customer portal).
  • Paddle may set third-party cookies on its domains (e.g. paddle.com, cdn.paddle.com) to complete payment, prevent fraud, maintain the checkout session, and operate the payment gateway.
  • Specific cookie names and lifetimes are managed by Paddle; see the Paddle Privacy Policy.
  • Details on the processing of personal data via Paddle are set out in the Privacy Policy and the List of Subprocessors.

9. Managing cookies in your browser

You can manage cookie settings directly in your web browser (blocking, deleting). Restricting strictly necessary cookies may affect the functionality of the Service (especially sign-in). Restricting Paddle cookies may make it harder to complete a payment.

10. Changes to this document

The Operator may update this document at any time, in particular in response to changes in technology or the operation of the Service. The current version is always available at the Service's address.

11. Contact

For any matter relating to cookies or the protection of personal data, please contact:

BHPS Labs s.r.o. Company ID: 29574668 Registered office: Klínová 620/1, Hulváky, 709 00 Ostrava, Czech Republic Email: info@udalist.app


This document takes effect on July 2, 2026.