Cookies
Cookie Policy
Version of 1 October 2026. Effective from: 1 October 2026.
What they are and who uses them
Floresca.bg is operated by “Idea Horizont” EOOD, UIC 208778820, address Sofia 1505, Poduyane district, 13 Yoakin Gruev St., apt. 3; info@floresca.bg. Cookies are small files that the site stores or reads on your device. Similar rules also apply to local storage, pixels, and other technologies for accessing information on the device.
Strictly necessary technologies are used, for example, for the cart you selected, a secure session, account login, completing a requested payment operation, and remembering your cookie choice. Without prior consent we use only technologies that are actually necessary for transmitting a communication or for a service you have expressly requested. Each function is assessed separately.
Analytical, advertising, and other optional technologies are activated only after your prior consent for the relevant category. They are not pre-enabled. Continuing to browse, scrolling, and closing the banner are not consent.
Managing your choice
On the first screen you can choose “Accept all”, “Reject optional”, or “Settings”. In settings you select the available purposes individually and save your choice. Rejection is as accessible as acceptance. Optional technologies remain blocked until you allow them.
At any time open “Cookie settings” at the bottom of the site to change your choice or withdraw consent. After withdrawal we stop further optional collection and remove or disable the corresponding identifiers that are available to us. Data already processed lawfully does not automatically become unlawful.
You may also delete or block cookies from your browser. Blocking strictly necessary technologies may interfere with the cart, login, or payment. Rejecting analytical or advertising cookies alone does not prevent purchase.
Google Analytics and Google Tag Manager when activated
Google Analytics 4 is used only after consent for analytics. Data may include pseudonymous identifiers and interactions with the site; we do not send emails, phone numbers, addresses, message texts, or other direct identifiers in analytical events or URLs. The recipient and international transfers are described according to the actual contracts and settings.
Google Tag Manager is a tool for managing tags; installing it alone does not provide consent and does not make the managed services necessary. Analytical and advertising tags and related requests are blocked until the relevant choice is made. A technology that does not use cookies may still process data and is not automatically treated as exempt from the rules.
For implementation: publish the previous two paragraphs only if the services are active. State the actual provider, countries, and the legal basis for transfer. For the initial model, a configuration without advertising features and Google Signals is recommended, with event and user data retention in GA4 set to two months; confirm the setting before publishing.
Catalogue of technologies actually used
For implementation: after setup, fill in one row for each technology actually found. An empty catalogue and examples are not published as established facts. Check all pages, guest, account, cart, each payment method, acceptance, rejection, and later withdrawal. Also include technologies created only after a specific action.
| Name and domain | Provider and purpose | Category and legal basis | Duration and activation moment |
|---|---|---|---|
| __________ | __________ | __________ | __________ |
| __________ | __________ | __________ | __________ |
| __________ | __________ | __________ | __________ |
| __________ | __________ | __________ | __________ |
Examples for checking, not a confirmed list: if WooCommerce is used — woocommerce_cart_hash, woocommerce_items_in_cart and wp_woocommerce_session_…; for WordPress login — wordpress_logged_in_…; for GA4 — _ga and _ga_…; the own cookie of the selected consent tool. Names, domains, purposes, and durations are taken from the live site and the documentation of the active versions.
For implementation: when adding the DSK virtual POS, check the payment scripts, domains, cookies, and local storage. Technologies strictly necessary for the expressly chosen payment are distinguished from analytics and advertising. The entire payment module must not automatically be declared exempt from consent for all of its purposes. The payment integration is added to the catalogue according to its actual mode of operation.
The selected period for remembering settings is six months, unless an earlier material change requires a new choice. Rejection is remembered with the same approach as acceptance. Evidence of the choice is kept in a limited form for up to three years, separately from analytical data. The cookie lifetime is not the same as the data retention period at the provider.
For more information about personal data, recipients, international transfers, and your rights, see the Privacy Policy or contact info@floresca.bg.
