Cookie Policy

Cookie Policy

How are CORONITY Cookies Used?

CORONITY uses cookies;

  • to remember your preferences and to personalize your website/mobile application/mobile site usage. This usage includes cookies:
    1. that save your password and keep your website/mobile app/mobile site session open all the time, thus helps you avoid the hassle of entering passwords more than once for each visit, and
    2. that remember and recognize you on your next visit to the website/mobile application/mobile site.
  • It uses cookies to specify from where and which devices you connect to the electronic commerce platforms operated by CORONITY, what content you view on the website/mobile application/mobile site and the duration of your visit and how you use the website/mobile application/mobile site.
  • It uses cookies to present content and ads that are more suitable for your interests; in other words, for targeted advertisement and promotion. CORONITY offers content more suitable to you, campaigns and products tailored for you and does not offer content or opportunities that you have previously stated that you did not want by matching the information obtained through cookies with your other personal data.

How can CORONITY use third party cookies for advertising and retargeting?

CORONITY can also use cookies to enable “ad technology” to present you ads that may be of interest when you visit the search engines, the websites/mobile applications or mobile site of e-commerce platforms run by CORONITY and/or the websites where CORONITY places ads. Ad technology uses the information about your previous visits to the websites/mobile applications/mobile sites and the websites/mobile applications/mobile site where CORONITY places ads in order to provide you with tailored ads. While presenting these ads, a unique third-party cookie can be placed on your browser so that CORONITY can recognize you. CORONITY also uses Google Analytics, a web analytics service provided by Google Inc. (“Google”). Google Analytics uses cookies to analyze how visitors use the website/mobile application/mobile site with statistical information/reports. For more information about using Google Analytics (including rejection options), you can visit: https://www.google.com/intl/en/policies/privacy/#infocollect

In addition, your e-mail address from your personal data is shared with these platforms in order to present advertisements that may be of interest to you on social media platforms and to create a special target audience. Your e-mail address is transmitted through secure channels and environments offered by these platforms. Social media platforms use your e-mail address hashing, only for the matching process. Your e-mail address is not shared with third parties or other advertisers and will be deleted from the systems of social media platforms as soon as possible after the matching process is completed. For example; Facebook will ensure the privacy and security of your e-mail address and Facebook User ID collection, which is encrypted with the hash method that creates your special target audience. It includes the technical and physical security precautions which is developed (a) to protect the security and integrity of your personal data as long as it is on Facebook systems, and (b) protect your personal data on Facebook systems against accidental or unauthorized access, and against the accidental or unauthorized use, modification or disclosure of your data. Also, unless you grant your permission or it is required by law, Facebook does not provide third parties or other advertisers with access to or information about your specific audience. It does not add your specific audience information to the information about our users, or create profiles based on your interests or use your specific target audience other than to serve you. Visit the address https://www.facebook.com/ads/manage/customaudiences/tos.php?_=_ for Facebook specific target audience conditions, and the address https://www.facebook.com/privacy/explanation for Facebook Privacy Policy.

In mobile application, Google and Criteo SDK (Software Development Kit) are used instead of cookies.

Cookie Management

Depending on the type of internet browser you are using, you can get information about cookies and exercise your right to accept or reject them by following the steps below:

Google Chrome: By clicking the “lock sign” or “i” in the “address section” of your browser, you can accept or reject cookies from the “Cookie” tab.

Internet Explorer: Click the “Security” tab in the “Tool” or “Tools” section in the upper right corner of your browser and make your cookie management choice as “accept” or “reject”.

Mozilla Firefox: Click on the “open menu” tab in the upper right corner of your browser. Click on the “Options” button to manage your cookies using the “Privacy and Security” button.

For other browsers (such as Opera and Microsoft edge), you can review the help or support pages of the relevant browser.

Safari: You can select the “safari” tab in the “Settings” section of your phone and manage all your cookies from the “Privacy and Security” section.

In addition to the above options; for information about all cookies and cookie management: You can visit https://www.allaboutcookies.org, https://www.youronlinechoices.eu/ or use the “Privacy Badger” application (https: //www.eff.org/tr/privacybadger)

For cookie or SDK management in mobile applications, you can follow the directions in the Privacy or Settings section of your device or use Lumen Privacy Monitor (https://haystack.mobi) by downloading it to your phone.

If you refuse persistent cookies or session cookies, you can continue to use the website, mobile application and mobile site, but you may or may not be able to access all functions of the website, mobile application and mobile site. In mobile applications, this situation may vary.

Cookie Types

Cookie types depending on the duration of use:  Session cookies and persistent cookies are used on the websites, mobile applications and mobile sites of e-commerce platforms run by CORONITY depending on the duration of use. The session cookie expires when you close your browser. The persistent cookie remains on your hard disk for a long time or indefinitely.

Cookie types based on the owner or provider of the cookie: “CORONITY cookies (first party cookies)” and “third party cookies” are used on the websites, mobile applications and mobile sites of the e-commerce platforms run by CORONITY. CORONITY cookies are created by CORONITY whereas third-party cookies are managed by third-party companies with which we cooperate.

Types of cookies according to the purpose of use: Technical cookies, verification cookies, targeting/advertising cookies, personalization cookies and analytical cookies are used on the websites, mobile applications and mobile sites of e-commerce platforms run by CORONITY according to the purpose of use.  Using these cookies, CORONITY specifies the features that distinguish its members from each other and divides the members into large groups in order to launch campaigns and advertisements according to their preferences. It carries out statistical analysis to identify the spending habits such as average spending amount, age, gender, shopping categories, and mobile usage rate.

Information about the cookies on CORONITY’s website is given in the tables below.

Cookie Service Provider Cookie Name Cookie Purpose Cookie Type Cookie Duration
Google eVar17 User Email consent information – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Google eVar16 User ID information – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Google eVar15 User age info – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display eVar14 User gender info – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display eVar48 User registration date – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display eVar49 User last login time – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display eVar51 User VIP info  – For use by applications in the Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display hEvar User hashed e-mail info – For use by applications in the Google Tag Manager system Persistent Cookie It is updated with user login to each site. Maximum 1 year
Criteo Display acsCheck User consent to watch +18 content Persistent Cookie 1 Day
Criteo Display rememberMe In order for the user to login to the system without entering login information Persistent Cookie 1 Week
Criteo Display cid To keep track of which revenue partner has directed the user to the site Persistent Cookie 1 Day
Criteo Display anonymousBasketKey To access the cart content of the Guest User Persistent Cookie 1 Month
Criteo Display Sgmdn_buyerID To segment the user by Google Tag Manager Persistent Cookie 1 Day
Criteo Display __stw For information about switching from MobileWeb view to site view Persistent Cookie 1 Day
Coronity __lpc To keep track of if MobileWeb’s Landing pagehas been displayed Persistent Cookie 4 Hours
Coronity isMember To store whether the user visiting the platform is a member Persistent Cookie 1 Month
Coronity DailyCampaignCodeCookie To store the codes of the daily Affilate Campaigns Persistent Cookie During the Promotion
Coronity CampaignCodeCookie To store the campaign codes of Daily Affiliate Campaigns Persistent Cookie During the Promotion
Coronity browserRecentlyViewedSessionId To store the ID that holds the list of recently viewed products Persistent Cookie 1 Month
Coronity isSignUpPopupClosed To store that the user has logged in with Facebook Persistent Cookie 1 Month
Coronity rtgCriteo To store that the user has been d,rected by Criteo Persistent Cookie 1 Month
Coronity justJoint To store whether the user has signed up in that session Session Cookie During the browser session
Coronity SID Kullanıcı session Id bilgisi Session Cookie Tarayıcı Session süresi boyunca
Coronity captcaID User session Id info Session Cookie During the browser session
Coronity quickaccess To store that the user has been visiting thanks to quick access and shortcut access links Session Cookie During the browser session
Coronity c_nurl To store what url the user is currently at. Session Cookie During the browser session