1. What cookies and localStorage are
Cookies are small text files a website can set in your browser. localStorage is a similar technology that keeps information directly in the browser, without automatically sending it to the server with every request. We use both technologies, depending on the category, to make the site work correctly and, only with your consent, for statistics and advertising.
2. Necessary (always active)
These cookies/localStorage entries are strictly necessary for the site to function — for example, to remember your choice from the cookie banner (accepted categories, policy version, date of choice) and your random consent identifier (consent_id), used only so that choice can later be proven and changed. You cannot disable this category, since without it the site could not honour your choice about the other categories.
3. Functional
Includes the “wd-lang” localStorage entry, which remembers the language you chose on the homepage (RO/RU/EN) so you don't have to select it again on every visit. It is active only if you choose to accept it; if you decline it, the site falls back to the default language (Romanian) on every new visit.
4. Analytics
Enabled only if you choose this category. Consent does not start Google Tag Manager — the container already runs on the page, with the default signals set to “denied” (see section 7). Choosing this category only permits the corresponding cookies to be stored and data to be processed by the traffic-analysis tags inside the container (e.g. Google Analytics), to understand how the site is used. The exact names of the cookies installed depend on the current configuration of the Google Tag Manager container and may vary — the list below describes the categories that are permitted, not a fixed list of cookies, since that list is not available at the level of the site's code.
5. Marketing
Enabled only if you choose this category. Consent does not start Google Tag Manager; it only permits the corresponding cookies to be stored and data to be processed by the advertising tags inside the container (e.g. Google Ads/remarketing), if and when configured, to show you relevant ads on other sites. As with the analytics category, the exact technologies depend on the container's configuration and are not fixed in the code.
6. How your choice is stored
Your choice (accepted/rejected categories, policy version, language, and time of choice) is saved locally in your browser via localStorage. In addition, we send our server a minimal record — the random identifier (consent_id), the policy version, the language, the chosen categories, the type of action (accept all / reject all / custom / withdraw), and the source of the action — without name, phone number, or full IP address — so that, if needed, we can prove that we honoured your choice.
7. Third parties involved
The only third party whose technologies may run on the site is Google (via Google Tag Manager and, where configured, Google Analytics/Google Ads). The Google Tag Manager script loads on the page with the default consent signals set to “denied” (Google Consent Mode v2, Advanced version), before any choice you make; Google's tags honour that signal and run without analytics or advertising cookies until consent is given for the corresponding category.
8. Purpose and duration
The cookie/localStorage entry needed to store consent remains valid until you change your choice or until we publish a new version of the cookie policy, in which case the banner will ask for your consent again. The functional “wd-lang” entry remains until you clear your browser data or change the language again. Google cookies, if enabled, follow the retention periods set by Google itself, described in Google's own policies.
9. How to change or withdraw your choice
You can change the accepted categories at any time via the “Cookie settings” link, permanently available in the footer of every page. Withdrawing consent for analytics or marketing cookies does not stop Google Tag Manager from loading; instead, it returns the corresponding consent signals to “denied”, stops the storage and processing of data that category had previously permitted, and, where technically possible, we delete the known cookies associated with those categories.
10. Changes to this policy
We update this policy when the technologies used on the site change. Current version: 1.1, updated 09.09.2026. For details on the processing of data collected through the forms, see the Privacy Policy.