Dokument

Richtlinie zu Cookies und Browserspeicher

Gültig ab 14 October 2026

Version prelaunch-2026-10-14-v2

This description concerns browser mechanisms controlled by the application. Cookies, localStorage, sessionStorage and Service Worker storage are different technologies; not every one of them is used for tracking.

1. Operator

The service is run by Michał Piłat, an entrepreneur entered in CEIDG, NIP 9222839601, REGON 542359454. Place of business: Jatutów 90, 22-400 Jatutów, Polska. Address for service: Rabindranatha Tagore 5A/54, 93-503 Łódź, Polska.

Contact on matters of the service, privacy and security: biuro@yuteki.eu. Do not send a password or access tokens in your message.

2. Session and interface settings

The session cookie maintains the login and the state of requests. The application's default configuration provides for about 2 hours of inactivity; the actual time depends on the deployment configuration and the browser.
XSRF-TOKEN supports form protection; its life cycle is tied to the session.
The remember function selected at login uses a separate cookie. Its actual lifetime depends on the configuration and browser limitations; logging out or revoking access may end its usefulness earlier.
The theme is stored in the appearance cookie (up to a year) and in localStorage. The sidebar_state menu state is saved for 7 days.
The language chosen with the switcher or at sign-up is remembered in the locale cookie (up to a year).
The saas_cookie_consent category choice is in localStorage, with no automatic expiry in the current code; it can be changed or cleared. Next to it lies the random identifier saas_cookie_consent_id, under which the evidence of a guest's choice is recorded; it holds no data about the person.
Chat and layout preferences, filters and the timer state may use browser storage. Some data is scoped to the user and the workspace; not all settings disappear after logging out. One-off tab states may use sessionStorage.

Login and form protection mechanisms serve the selected function of the service. Blocking them may prevent logging in or the correct handling of requests. We describe interface preferences separately from optional analytics and marketing.

3. Optional Google Tag Manager

If the operator configures a GTM container, the application's loader waits for a positive choice of at least one optional category: analytics, marketing or personalisation. Before such a choice it does not download the GTM script. An empty container identifier means this loader is not started.

Changing the choice updates the Google Consent Mode signals. Withdrawing the choice does not automatically remove code that has already been loaded, earlier cookies or data held by recipients. On the next full page load, if all categories are refused, the application's loader does not start GTM. Tags inside a specific container must respect the choices; the application itself gives no guarantee of the behaviour of every tag configured outside it. This document is not a confirmation of the activity or a complete list of tags of any deployment.

4. Other connections and application storage

The waiting list form is handled by Cloudflare Turnstile in order to limit bots. The page template uses Bunny fonts. These resources may cause the browser to connect to an external service independently of GTM. Their presence does not mean consent to the newsletter.

The Service Worker stores static resources, e.g. icons and versioned interface files. This is not a declaration of full offline work on workspace data. Documents, login and registration do not have a separate page response cache in it; versioned resources may remain until the version is replaced or the storage is cleared.

Push requires browser permission and a notification subscription. Delivery uses the infrastructure appropriate to the browser. We do not assume that this infrastructure processes no metadata.

5. Changing the choice

Cookie settings can be reopened with the "Cookie settings" button on the page. You can reject the optional categories or choose them separately. Deleting site data in the browser also deletes the saved choice; on the next visit a new choice may be needed.

The browser lets you separately manage cookies, site storage, the Service Worker and notifications. Withdrawing a setting does not reverse earlier connections. The newsletter/email marketing preference and the choice of optional browser categories are separate states.