Cookie policy
1. What cookies and similar technologies are
Cookies are small text files stored by the browser on the user's end device while using semantichub.app. Alongside cookies, the service also uses the browser's localStorage, which works on a similar principle — it stores information locally on the user's device, without automatically sending it to the server with every request.
Article 173 of the Polish Telecommunications Law of 16 July 2004 covers any storing of information, or gaining access to information already stored, on the user's end device, regardless of the technology used. For this reason, this policy jointly describes cookies and the localStorage entries used by the service — the full registry is set out in the "Registry of stored information" section below.
2. Categories
The service distinguishes two categories of stored information:
- Essential — necessary for the service to work correctly: keeping the user signed in, remembering the interface language and theme, recording the consent decision, telling bot traffic apart from user traffic, and the working state of the views. These cannot be declined in the consent window — blocking them means the service stops working as intended.
- Analytics — disabled by default, enabled only after consent is given. This category covers Umami and Microsoft Clarity.
The essential category also includes the Bugsink application error tracker, even though it does not appear in the registry section below. Bugsink stores nothing on the user's device — it sets neither cookies nor localStorage entries — and is therefore not subject to the consent requirement of Article 173 of the Telecommunications Law at all, since that article covers only the storage of information on the end device. Bugsink additionally runs with personal data collection disabled ("sendDefaultPii: false") and transaction tracing disabled ("tracesSampleRate: 0"). Monitoring application errors falls within the Operator's legitimate interest in keeping the service secure and operational — it is listed here for full transparency, even though it formally requires neither a registry entry nor consent.
The Umami traffic analytics runs in cookieless mode — it stores no identifier on the user's device and could formally be enabled without consent, on the same basis as Bugsink. The Operator nonetheless placed it in the category that requires consent: since the consent window presents analytics as a separate category and leaves the choice to the user, enabling analytics against the user's refusal would be inconsistent with that choice, regardless of whether the technology formally requires it. Declining consent for this category means the user's visit is not included in traffic statistics.
3. Registry of stored information
The registry below covers every cookie and localStorage entry used by the service — consistent with the principle described in "What cookies and similar technologies are", it is not limited to cookies alone.
| Key | Type | Purpose | Retention | Category |
|---|---|---|---|---|
| NEXT_LOCALE | cookie | remembers the selected interface language | 12 months | Essential |
| cc_cookie | cookie | records the cookie consent decision | 6 months | Essential |
| _clck | cookie (Microsoft Clarity) | remembers a pseudonymous user identifier and preferences | period set by Microsoft | Analytics |
| _clsk | cookie (Microsoft Clarity) | links successive page views into one analytics session | period set by Microsoft | Analytics |
| __cf_bm | cookie (Cloudflare) | tells bot traffic apart from users | approx. 30 minutes | Essential |
| access_token | localStorage | keeps the logged-in user's session | until logout | Essential |
| refresh_token | localStorage | refreshes the logged-in user's session | until logout | Essential |
| theme | localStorage | remembers the chosen interface theme (light/dark) | indefinite | Essential |
| sh_locale | localStorage | remembers the application interface language | indefinite | Essential |
| sh_timezone | localStorage | remembers the user's time zone | indefinite | Essential |
| sh-cluster-cart | localStorage | working state of the cluster cart in working views | indefinite | Essential |
| sh-range | localStorage | working state of the selected date range in working views | indefinite | Essential |
4. Withdrawing consent
Consent for the analytics category can be withdrawn at any time using the "Cookie settings" button available in the site footer. The button reopens the consent window, where a previous decision can be changed.
Consent can also be withdrawn or restricted through browser settings — most browsers let you block cookies from being set, delete cookies already stored, and clear localStorage for a given site. The exact steps depend on the browser used and are described in its documentation.
Withdrawing consent does not affect the lawfulness of processing carried out on its basis before the withdrawal.
5. Consequences of refusal or disabling
Refusing or withdrawing consent for the analytics category does not limit any feature of the service — the user's visit is not included in Umami or Microsoft Clarity analytics.
Blocking essential cookies or localStorage entries through browser settings has a different effect: the service may stop working correctly. In particular, the user may be logged out or unable to log in (no "access_token" or "refresh_token" is stored), the interface language and theme may reset on every visit, and the working state of the views (e.g. the cluster cart, the selected date range) may not be remembered between sessions. Blocking the "__cf_bm" cookie may also cause the user's traffic to be misidentified as suspicious by Cloudflare's protection mechanism.
6. Changes to this policy
The Operator may amend this policy, in particular in connection with a change in the technologies used or in applicable law. Every change to the content of this policy is accompanied by raising the revision number in the consent mechanism's configuration, which causes the consent window to be shown again to all users, regardless of any decision they made previously. The current version and effective date are always shown in the header of this document.