Cookie policy
1. Legal basis and purpose
This policy explains cookies, localStorage, sessionStorage, pixels and similar technologies. Article 225 ZEKom-2 generally requires prior consent except for technologies strictly necessary to transmit a communication or provide a service expressly requested by the user. Where personal data is processed, the GDPR and ZVOP-2 also apply.
2. What cookies and local storage are
A cookie is a small value stored by the browser for a domain. Local storage is a similar browser space. These technologies may support sessions, login, basket, language, security, measurement or marketing. In this policy “cookie” also covers comparable technologies where appropriate.
3. Categories
- Necessary: login, security, basket, checkout, storing your choice and transmitting a requested communication. The exemption is interpreted narrowly.
- Functional: remember language or other optional preferences.
- Analytics: measure visits and use when a configured analytics tool is enabled.
- Marketing: measure campaigns, create profiles or support targeted advertising.
4. Your choice
On first visit you can accept all, reject optional technologies, or customize. The choices are presented with comparable prominence. Silence, continued browsing or a pre-ticked box is not consent. Change the choice at any time:
5. Current register
The table is generated from the module configuration. The administrator must update it whenever a service is added or removed.
| Name | Provider | Category | Purpose | Duration |
|---|---|---|---|---|
vdlc_consent | Verdamare | Necessary | Stores cookie choices and policy version. | 180 days |
vd_lang | Verdamare | Functional | Stores the selected website language. | 1 year |
wordpress_logged_in_* / wordpress_sec_* | WordPress | Necessary | Login, account security and session management. | Session / login preference |
vdvic_visitor | Verdamare | Analytics | Links visits from the same browser after analytics consent. | 365 days |
vdvic_session | Verdamare | Analytics | Links page views within one session. | Session |
6. Third-party content
Embedded maps, videos, social networks, analytics or marketing services may set their own technologies and receive IP and technical data. Optional content should load only after the relevant choice. Payment or security technologies may load where strictly required for an expressly requested payment service or transaction protection.
7. Evidence of choice
The system may record a random identifier, categories, time, policy version, and hashed IP and user agent. The purpose is to demonstrate and respect the choice, not advertising tracking. Retention is stated in the privacy policy.
8. Duration and renewed consent
The choice is stored for the configured period. We ask again on expiry, a material category change or a new policy version. Browser storage can also be cleared manually.
9. Browser controls and privacy signals
A browser can block or delete technologies, which may break login, basket or requested functions. A general browser privacy signal is honoured only where technically supported and compliant with consent requirements; an unreliable signal is not a substitute for a clear interface.
10. Module limitation
This module conditionally emits only scripts registered in its script manager. A theme or another plugin may inject other scripts; the administrator must audit those sources and disable them until consent or move them into the manager.
11. Changes and contact
The register and policy are updated when technologies or providers change. Questions: sale@verdamare.si.