This policy explains how the Platform uses cookies, local storage, pixels, SDKs, and similar technologies that store information on, or access information from, a user’s device. Where consent is required under applicable ePrivacy rules, non-essential technologies will be activated only after the user has granted consent. Strictly necessary technologies do not require consent where they are genuinely required to provide or secure the requested service.
2. Categories of technologies
Strictly necessary: technologies required for login sessions, security, load balancing, fraud prevention, consent storage, core user preferences, and technical service delivery. Functional / preference technologies: technologies that remember language, display settings, or saved non-essential user preferences. Depending on implementation, these may require consent if not strictly necessary. Analytics: technologies used to understand traffic, performance, and product usage. These should be disabled until consent is collected unless the implementation qualifies as strictly necessary under applicable law, which is uncommon. Advertising or profiling: if deployed in the future, these technologies must remain off until explicit consent is obtained and the policy must be updated before rollout.
3. Local storage for favorites and guest functions
The Platform may store selected listings, consent choices, and similar interface data in browser local storage. For example, guest favorites may remain on the user’s device and be associated with that device or browser until the user clears them or they are overwritten. If local storage is used for analytics or tracking rather than for the specific functionality requested by the user, consent should be collected before activation.
4. Consent management
Users should be able to accept, reject, or customize non-essential technologies through a consent banner or preferences centre. The Platform should keep a record of the user’s consent choice and provide an easy way to change that choice later. Withdrawal of consent must be as easy as giving it. Changing browser settings alone is not always sufficient to meet this requirement.
5. Retention and inventory
Each cookie or similar identifier should have a defined lifespan. Session technologies should expire when the session ends unless a longer duration is necessary and justified. Persistent technologies should use proportionate expiry periods. The Platform uses the following technologies: Session cookies for authentication and security (session duration). Consent cookie to store user preferences (up to 12 months). Google Analytics cookies (only after user consent, duration varies up to 24 months). Local storage for favorites (until cleared by user).
6. Third-party technologies
If third-party analytics, embedded media, payment widgets, maps, or anti-abuse tools place or read identifiers on the user’s device, those technologies must be reflected in this policy and, where required, blocked until consent is obtained.
7. How users can control technologies
In addition to the Platform’s consent settings, users may delete stored identifiers through browser settings. Doing so may log the user out or remove saved preferences and guest favorites.
8. Contact
Questions about cookies, device storage, and consent may be sent to pusto.sk.com@gmail.com.
