Cookies & Device Storage
This policy describes terminal-storage mechanisms currently used or materially identified on the KOM-5A Web platform.
Effective date: 2026-08-26 • Version: 1.0 • Consent: 2026-08-cookie-v2
KOM-5A distinguishes mechanisms strictly necessary for the service from optional preference storage. Optional mechanisms are not activated merely because a user visits the site or accepts the Terms of Use.
Principles
- Mechanisms strictly necessary for the service, security, authentication, storing the consent choice or an expressly requested action may operate without optional consent where limited to that purpose.
- Optional preferences are off by default and are used only after acceptance.
- Rejecting is as easy as accepting: the first layer provides Reject All, Customize and Accept All.
- Users may reopen Cookie settings at any time and change their choice.
- No choice, silence or acceptance of the Terms of Use constitutes consent to optional storage.
- A new manager version or expiry of the choice triggers a new request.
Current consent-manager categories
Necessary — always active
This covers storage of the consent choice and functional mechanisms genuinely necessary for session, security, authentication or an expressly requested action. They must not be repurposed for incompatible advertising or analytics purposes.
Preferences — optional
These are used only to remember non-essential convenience choices. They are OFF by default. Optional storage currently connected to this category includes remembering whether a mobile promotional notice has already been shown.
Analytics and Marketing
Consent Manager V2 currently has no optional Analytics or Marketing category. If KOM-5A later introduces optional trackers for these purposes, a new choice will be requested before activation.
Currently identified Web inventory
| Name / mechanism | Technology | Purpose | Category | Duration / rule |
|---|---|---|---|---|
| kom5a_cookie_consent | localStorage | Stores consent version, choice and timestamp. | Necessary | Maximum 180 days before re-prompt, unless the version changes or storage is removed earlier. |
| lang | localStorage | Stores the language explicitly selected by the user. | Functional / necessary for the requested preference | Until changed or removed by the user or browser. |
| k5a_mobile_promo_seen_v1 | localStorage | Remembers that a mobile promotional notice has already been shown. | Optional Preferences | Used only while Preferences = accepted; removed when rejected, withdrawn or expired. |
| Invitation / handoff keys | localStorage / sessionStorage | Temporarily preserves a code or context needed for a requested registration or action. | Functional, depending on the requested action | Session or functional lifetime; no advertising purpose. |
| Local reactions / deduplication | localStorage | Prevents certain local repetitions and supports coherent user actions. | Functional | Depends on the mechanism; some entries use daily or 24-hour logic. |
| k5a_last_bid | localStorage | Functional handoff tied to a user-requested action. | Functional | Until consumed, replaced or browser storage is removed. |
How your choice works
- The current manager version is 2026-08-cookie-v2.
- Necessary is always enabled.
- Preferences is optional and off by default.
- Reject All keeps Preferences false.
- Accept All enables Preferences.
- Customize lets the user decide Preferences separately.
- The choice is stored locally with a timestamp.
- The choice expires after 180 days, after which a new request appears.
- An invalid or abnormally future timestamp invalidates the choice.
- Withdrawing Preferences immediately neutralizes known optional storage connected to that category.
Duration and deletion
V2 does not silently extend the choice simply by reading it. A new period starts only when the user actively saves a new choice. Users may also clear browser storage. Other functional storage mechanisms follow the lifecycle appropriate to the relevant feature.
Third-party services and authentication
- KOM-5A uses third-party technical services, including authentication services. Some may use mechanisms strictly necessary for security or session management.
- This page does not claim that a static inventory necessarily lists every technical name that a provider may create dynamically. Any new non-necessary or advertising mechanism must be assessed and, where required, blocked until appropriate consent.
- No active Google Analytics, GTM, Meta Pixel, Hotjar, Clarity, PostHog or Sentry mechanism was materially identified in the Web source audit supporting this version.
iOS, Android and other device storage
- This version describes the Web system that has been audited.
- iOS and Android apps may use operating-system identifiers, push tokens, SDKs or device storage. Their inventory and alignment with App Store and Google Play disclosures are reviewed separately.
- This Web policy must not be interpreted as authorizing an undeclared mobile tracker.
Changes
If KOM-5A introduces a new optional purpose, tracker, advertising provider or audience-measurement mechanism requiring consent, the manager and this policy must be updated before activation. A material change creates a new version and, where required, a new choice.
Contact
For questions about cookies, terminal storage or privacy, use the contact details published in the Legal Notice and Privacy Policy.