Legal
Cookie and Similar Technologies Policy
Which cookies and similar technologies we use, for what purposes, and for how long.
Document content
Effective date: 15 May 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). 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.
| Name | Purpose | Lifetime |
|---|---|---|
UDALIST_LOCALE | Selected website language | per browser settings |
JWT | Sign-in (HttpOnly) | per token validity |
JWT_REFRESH_TOKEN | Session renewal (HttpOnly) | per token validity |
oauth_terms_consent_version | Terms acceptance during Google sign-up (HttpOnly) | approx. 10 minutes |
oauth_login_language_code | Google sign-in completion — language (HttpOnly) | approx. 10 minutes |
oauth_login_intent | Google 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 only 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.
- Analytics runs in cookieless mode — we do not set an analytics cookie for this purpose.
5. 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.
6. 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.
7. 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.
8. 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 15 May 2026.