Cookie Policy

UCSM Cookie Policy
Last updated: 14 October 2026 (pro forma, subject to final legal review)

This policy explains which cookies and similar technologies the UCSM platform uses. The controller is UCSM Solutions Ltd, 16 Aleko Konstantinov Str., floor 4, Plovdiv, Bulgaria, UIC/EIK [EIK]. Questions: privacy@ucsm.eu.

1. What we use
UCSM uses only the cookies that the platform needs to work and one cookie that remembers your display theme. These do not need your consent. We do not use advertising cookies, tracking pixels or third-party analytics on the platform. If we ever add cookies that are not necessary, we will ask for your consent first and list them here.

2. Cookies set by the platform
Name: .AspNetCore.Cookies. Purpose: keeps you signed in. Type: necessary. Lasts: for the sign-in session.
Name: .AspNetCore.Session. Purpose: keeps your session on the server side. Type: necessary. Lasts: until you close the browser or after 8 hours of inactivity.
Name: .AspNetCore.Antiforgery.* . Purpose: protects forms against forged requests. Type: necessary. Lasts: for the session.
Name: .AspNetCore.Correlation.* and .AspNetCore.OpenIdConnect.Nonce.* . Purpose: temporary security values used while you sign in through our identity provider. Type: necessary. Lasts: minutes, until the sign-in finishes.
Name: ucsm_kiosk. Purpose: keeps a workshop's Kiosk device signed in. Type: necessary. Lasts: as set by the workshop for that device.
Name: ucsm_theme. Purpose: remembers your light or dark display theme. Type: preference. Lasts: [period, to be confirmed].
Short notices that the platform shows after an action may be kept in a temporary cookie of the framework that is deleted when the message has been shown.

3. Cookies of other providers
When you sign in, the page of our identity provider (Auth0) sets its own cookies. When you pay, the Stripe page sets its own cookies. They are governed by those providers' policies.
Our pages also load fonts from Google Fonts, code libraries from jsDelivr and Cloudflare (cdnjs), and training videos from YouTube in its privacy-enhanced mode. When your browser loads them, those providers receive your IP address and browser details, and a video provider may set cookies when you play a video.

4. The mobile application
The application stores a sign-in token and a push-notification identifier on your device. You can turn push notifications off in the settings of your device.

5. How to control cookies
You can delete or block cookies in your browser settings. If you block the necessary cookies, you will not be able to sign in or use the platform.

6. Changes
We may update this policy and will publish the new version with its date.