1. ABOUT THE COOKIE POLICY
This policy refers to cookies and similar technologies used, as appropriate, in websites and applications operated by KA & MA TRADING SRL.
Cookies are used for purposes such as:
- Website operation
- Service functionality
- Analysis and performance
- Marketing and advertising
The current page complements the personal data processing policy which can be found in the website's terms and conditions, which we encourage you to read. The personal data processing policy includes additional useful information such as all data processing purposes, your rights, as well as exceptions and limitations thereof, etc. Proper protection of personal data is an important objective for us. Our desire is to be as clear and transparent as possible. For any questions, please contact us at office@depozituldesaltele.ro.
2. WHAT ARE COOKIES AND SIMILAR TECHNOLOGIES?
Cookies and similar technologies are relatively small files containing essential information stored on your devices – these files allow us to record information and data when you interact with the websites, services, applications, messaging, or tools provided by our company. Although these technologies are generally referred to as Cookies, each operates differently, and the entire process is better explained on specialized websites.
3. USE OF COOKIES
Any cookies used by this website run individually or on a session basis to maintain user community preferences or to analyze website traffic or other purposes.
By continuing to use and browse our websites, applications, services, tools, and messaging provided by our company, you agree to the use of cookies and similar technologies for optimal operation. However, if you do not wish to accept these technologies linked to the services we offer, you can access your web browser settings to disable or completely delete them. Web pages with applications designed to give visitors control over processed personal data have also been prepared.
If you leave a comment on the site, you can choose to save your name, email address, and website in the form of cookies. This option is to support user activity and to avoid re-entering data each time you leave new comments. The duration of cookies is usually 1 year. If you visit the login page, we will set temporary cookies to determine whether your browser accepts these technologies. These cookies do not contain personal data and are deleted when you close the browser.
When you log in, we also set cookies to save your login information and screen display preferences. Login data will persist for up to two days, and display options for 1 year. If you select "Remember me," your login will persist for approximately two weeks or 365 days for WHMCS. If you log out of your account, all login-related cookies will be deleted. If you edit or publish an article, an additional cookie will be saved in your browser. This cookie does not include personal data and indicates the ID of the article you edited. It usually expires after one day.
Pages on this site may include embedded content (videos, images, articles, etc.). Embedded content from other sites behaves exactly as if the visitor had accessed those sites. These sites may collect data about you, use cookies, embed third-party tracking codes, and monitor interaction with the embedded content.
4. WHAT COOKIES DO WE USE?
On the websites, we use session and permanent cookies. We may also use first-party, third-party, flash, or zombie cookies.
Session cookies: Session cookies, also known as "temporary cookies," help websites recognize users and the information provided when they navigate a site. Session cookies retain information about a user's activities only for the duration of their visit to the site. Once the web browser is closed, the cookies are deleted. These are commonly used on shopping sites or e-commerce sites.
Permanent cookies: Permanent cookies, also known as "persistent cookies," remain active even after the web browser is closed. For example, they can remember login details and passwords so that web users do not have to re-enter them every time they use a site. The law stipulates: permanent cookies must be deleted after 12 months.
First-party cookies: First-party cookies are set directly by the website (i.e., the domain) the user is visiting (i.e., the URL displayed in the browser's address bar). These cookies allow site owners to collect analytics data, remember language settings, and perform other useful functions that provide a good user experience.
Third-party cookies: Third-party cookies are set by third parties with the aim of collecting certain information from web users to conduct research on behavior, demographics, or spending habits, for example. They are commonly used by advertisers who want to ensure their products and services are promoted to the right target audience.
Flash cookies: Flash cookies, also known as "super cookies," are independent of the web browser. They are designed to be stored permanently on a user's computer. These types of cookies remain on a user's device even after all cookies have been deleted from their web browser.
Zombie cookies: Zombie cookies are a type of Flash cookie that is automatically recreated after a user has deleted them. This means they are difficult to detect or manage. They are often used in online games to prevent users from using cheating applications.
5. HOW ARE COOKIES USED BY THIS SITE?
A visit to this site or the websites operated by our company may place the following types of cookies:
- Strictly necessary cookies for site operation
- Extended functionality cookies
- Analytics and performance cookies
- Marketing and advertising cookies
Strictly necessary cookies and/or similar technologies are essential for the proper functioning of the site, being set on your device when accessing the site or following actions performed on the site, as appropriate. You can set your browser to block cookies, but in this case, certain sections of the site will not function correctly.
6. DO COOKIES OR SIMILAR TECHNOLOGIES CONTAIN PERSONAL DATA?
Cookies or similar technologies themselves do not request personal information to be used and, in many cases, do not personally identify internet users. However, there are situations when personal data may be collected through the use of cookies to facilitate certain functionalities for the user or to provide the user with an experience more tailored to their preferences. Such data is encrypted in a way that makes unauthorized access impossible.
What are similar technologies? There are other technologies that can be used for the same purposes as cookies. We may use Local Storage as a similar technology.
7. BLOCKING COOKIES
If you wish to block cookies, some functionalities of the site will be disabled, which may lead to certain dysfunctions or errors in using our site. For example, blocking cookies may prevent you from logging into your account. Most browsers are set by default to accept cookies, but you can change the settings to block some or all cookies.
8. MANAGING PREFERENCES
Generally, an application used to access web pages allows saving cookies and/or similar technologies on the terminal by default. These settings can usually be changed so that the automatic management of cookies is blocked by the web browser or the user is informed each time cookies are sent to their terminal. Detailed information about the possibilities and ways of managing cookies can be found in the application's (web browser's) settings area. Limiting the use of cookies may affect certain website functionalities.
We make efforts to allow users to manage their cookie preferences and the transmission of personal data to third-party processors in accordance with their own decisions. Therefore, you have the option to set your cookie preferences in the footer of the web page under the "Cookie Preferences" section.
9. URL LINKS & USEFUL ADDITIONAL INFORMATION
You can access the following URLs if you want to learn more about cookies:
https://support.microsoft.com/en-us/help/260971/description-of-cookies
http://www.allaboutcookies.org/
http://www.youronlinechoices.com/ro/
The table below describes each cookie used on the website, including their role. We will not use these cookies in ways other than those indicated. In the case of security cookies, we may treat them as strictly necessary or functional.
| Name | Category | Type | Validity | Description |
|---|---|---|---|---|
| cookie_consent_level | Strictly Necessary | Persistent | ~ 1 year | Displaying the cookie policy banner. |
| cookie_consent_user_accepted | Strictly Necessary | Persistent | ~ 1 year | Storing interaction with the cookie banner. |
| cookie_consent_user_consent_token | Strictly Necessary | Persistent | ~ 1 year | Token for storing user cookie consent. |
| cf_clearance | Strictly Necessary | Session | 1 session | Stores proof that the captcha test has been passed. Used to prevent displaying the captcha challenge again. It is necessary to access the origin server where the site and/or other applications are hosted via CloudFlare proxy. |
| cf_chl_XXXX | – | – | – | Used to verify if the CloudFlare Edge server has cookie compatibility. Can be removed if identified. XXXX represents a dynamic name. |
| cf_chl_rc_i cf_chl_rc_ni cf_chl_rc_m |
– | – | – | These cookies are for internal use to allow CloudFlare to identify production issues on clients. |
| __cflb | – | Session | 1 session | When session affinity is active with CloudFlare Load Balancer, a cookie named __cflb with a unique value is set as the initial response. CloudFlare routes subsequent requests to the same origin, optimizing network resource utilization. In the event of a failover, CloudFlare sets a new __cflb cookie to direct subsequent requests to the failover pool. The __cflb cookie allows CloudFlare to return responses from the same origin for a specific period configured by our company. This allows users to have a smooth experience. This cookie is of Session type and usually exists from a few seconds to 24 hours. This cookie is only set for IP addresses with CloudFlare proxy. |
| __cf_bm | – | – | – | CloudFlare identifies and mitigates automated traffic to protect services from malicious bots. CloudFlare sets the __cf_bm cookie on devices accessing our services through Bot management and Bot fight mode. The __cf_bm cookie is necessary to enable security solutions to function. The cookie expires after 30 minutes of continuous user inactivity. The information in the cookie (other than time-related) is encrypted and can only be decrypted by CloudFlare. A separate __cf_bm cookie is generated for each site the user visits as CloudFlare does not track users from one site to another or from one session to another. The __cf_bm cookie is generated independently by CloudFlare and does not correspond to any user ID or other identifiers. |
| cf_ob_info cf_use_ob cookie |
– | Permanent | ~ 30 seconds | Cloudflare Always Online: The cf_ob_info cookie provides information about: the origin web server's HTTP Status code, the original Ray ID request, the datacenter delivering traffic. The cf_use_ob cookie informs CloudFlare to deliver requested resources from the Always Online cache on the set port. The cf_ob_info and cf_use_ob cookies are persistent and expire after 30 seconds. |
| __cfwaitingroom | – | – | – | The Cloudflare waiting room product enables a waiting room for a particular host and path combination in that zone. Visitors are placed in the waiting room and provided with an ETA on when they will be allowed access to the application if there is no immediate availability. The __cfwaitingroom cookie is only used to track visitors accessing the waiting room host and path combination for that zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active. |
| __cfruid | – | – | – | The __cfruid cookie is strictly necessary for CloudFlare Rate limiting compatibility. It is necessary to manage incoming traffic and to have better visibility regarding the origin on particular requests. |
| _cfuvid | – | – | – | The Rate limiting Rules product uses a number of techniques to apply rate limits to traffic where many unique users share the same IP address, such as traffic from behind a NAT. These techniques can be used by enabling the cf.unique_visitor_id field in the rate limiting configuration. The _cfuvid cookie is only set when the site uses this option in a Rate limiting rule and is only used to allow CloudFlare WAF to distinguish individual users who share the same IP address. Visitors who do not have this cookie are usually grouped together and may not be able to access the site if there are many other visitors from the same IP address. |
| _ga | Analytics and performance | Permanent | ~ 1 year | This cookie name is associated with Google Analytics – which is a significant update to Google's most frequently used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is used to calculate visitor, session, and campaign data for site analytics reports. |
| _ga_GH5S2YY1P9 | Analytics and performance | Permanent | ~ 1 year and one month | This cookie is used by Google Analytics to persist session state. |
| PrestaShop-{hash} | Functional | Permanent | ~ 1 year and one month | Online content display platform, invoice generation, and CMS. |
| PHPSESSID | Functional | Session | 1 session | Display content based on page access and number of sessions. |
| wordpress_test_cookie | Functional | Session | 1 session | Test cookie functionality in browser. |
| wp-settings-{user} | Functional | Permanent | ~ 1 year | Saving admin settings. |
| wp-settings-time-{user} | Functional | Permanent | ~ 1 year | The time at which wp-settings-{user} was set. |
| wordpress_logged_in_{hash} | Functional | Permanent / Session | ~ 14 days / 1 session | Checks if the user is logged into the platform. Retains the user session. |
| wordpress_sec_{hash} | Functional | Permanent / Session | ~ 14 days / 1 session | Checks if the user is logged into the platform. Retains the user session. |
| wp-saving-post | Functional | Permanent | ~ 1 day | Tracks if there are saved posts for the post being edited. If so, allows the user to store information. |
| comment_author_{hash} | Functional | Permanent | ~ 347 days | Tracks the comment author's name if the option to save name, email, and website is checked. |
| comment_author_email_{hash} | Functional | Permanent | ~ 347 days | Tracks the comment author's email address if the option to save name, email, and website is checked. |
| comment_author_url_{hash} | Functional | Permanent | ~ 347 days | Tracks the comment author's URL if the option to save name, email, and website is checked. |
| wp-postpass_{hash} | Functional | Permanent | ~ 10 days | Keeps the session active if a post is password protected. |
| wp_lang | Functional | Session | 1 session | Stores language settings. |
| _gcl_au | Marketing and advertising | Permanent / Session | ~3 months | This cookie is set by Doubleclick and collects information about how the end-user uses the website and any advertising the end-user may have seen before visiting the site. |
| test_cookie | Marketing and advertising | Permanent / Session | ~15 minutes | This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser accepts cookies. |
| _fbp | Marketing and advertising | Permanent / Session | ~3 months | Used by Facebook to deliver a range of advertising products, such as real-time bidding from third-party advertisers. |
| IDE | Marketing and advertising | Permanent / Session | ~1 year | This cookie is set by Doubleclick and collects information about how the end-user uses the website and any advertising the end-user may have seen before visiting the site. |
| _GRECAPTCHA | Strictly Necessary / Functional | Permanent | ~ 6 months | Captcha for user registration on the site to protect against fraud and abuse. |
We use services provided by third parties to offer functionalities, for analytical purposes, and for displaying advertising. These third parties may set and use cookies and similar technologies on the websites and applications we manage, as well as on websites and applications not managed by us.
For more details, consult the data protection policies as well as the user preference management guides and the deactivation options offered by the companies that manage these services, as applicable.
Managing preferences regarding cookies and similar technologies
Google Analytics
Category: Analytics
Purpose: Website analytics
Policies: https://policies.google.com/technologies/cookies?hl=en-US#how-google-uses-cookies, https://marketingplatform.google.com/about/analytics/terms/us/
Google Ads
Category: Advertising
Purpose: Remarketing
Policies: https://policies.google.com/privacy, https://policies.google.com/technologies/ads
Google Maps API
Category: Functionality
Purpose: Delivery points and estimates near the user through reverse geocoding
Policies: https://policies.google.com/privacy
Google Doubleclick
Category: Advertising
Purpose: Display advertising
Policies: https://policies.google.com/technologies/ads
Meta (Facebook, Instagram)
Category: Advertising
Purpose: Remarketing
Policies: https://www.facebook.com/privacy/explanation
Manage cookies and third-party services here. However, please note that if you restrict or block the use of these cookies and similar technologies, you will experience certain disruptions in the site's functionalities, such as the customer or user account login process.