Buscar

Política de cookies

We, as Vestel Trade Co. (the "Company"), make use of various technologies such as cookies, pixels, GIFs, etc., to improve your experience during your use or visit of our websites ("Website"), applications or all similar online or offline platforms (all mentioned platforms shall collectively be referred to as the "Platform") offered to your use in digital environment.

Cookies are small text files which we store on your device when you visit our website. These cookies are sent back to us every time you access our website subsequently. This allows us to recognise you, for example, or makes navigating our website easier for you thanks to the information stored in the cookies.

We do not share the information stored in the cookies with third parties without your express permission.

The use of such technologies performed in accordance with the legislation we are subject to, particularly with the General Data Protection Regulation ("Law").



With this Cookie Disclosure Policy, the usage purposes for which Cookies will be collected during the use of the Platforms and how you can control these Cookies will be explained to your side. 



You can opt out of using the cookies we use on our website and in our application, change their types or functions, or add new cookies to our website. Therefore, we reserve the right to change the provisions of this Cookie Policy at any time. Any changes made to the current Cookie Policy shall become effective at the time they are published on the website, in the application or any platform open to the public. Latest update information has been provided at the end of the text.



  1. Method and Legal Grounds to Collect Cookies 



Cookies which are obtained within the scope of your visit to our applications or our website and which are technically required to perform the primary functions of our website will be collected based on the legal grounds for the legitimate interest of the our Company as stated under the Law. Cookies collected for preference, statistics and marketing purposes can only be collected only upon your explicit consent. 



You can always manage the use of cookies from the Manage Cookies section. 

Your collected personal data may be shared with our suppliers limited to the fulfillment of the purposes specified under this Cookie Policy and in accordance with the legislation. 




  1. Cookie Types According to their Duration



  1. Session Cookies: These Cookies are temporary and they disappear upon closing the browser or the termination of the session. 



  1. Permanent Cookies: These Cookies are those that remain on your hard drive until you delete them or your browser automatically deletes them depending on their expiry date. The expiry date of Permanent Cookies are predetermined even if such vary. 



  1. Types of Cookies According to Provenance 



  1.  First-Party Cookies: As the name suggests, first-party Cookies are those placed on your device by our Platforms. 



  1. Third-Party Cookies: These Cookies are those placed on your device not by our Platforms you visit, but by the advertising third parties performing analytics systems. 



  1. Cookies Used on Our Platforms



Strictly Necessary Cookies

The use of certain Cookies is imperative for our website and application to function properly. For example, authentication cookies which are activated when you log in to our website allow your session to continue when you switch to different pages within our website. 



Name

Provider 

Purpose

Expiry

PHPSESSID

SHARP

HOLDS USER LOGIN ACTIVITY

1 year

COOKIEPREF

SHARP

HOLDS USERS COOKIE PREFERENCES

1 year



Functional Cookies 

These Cookies enable you to personalize the services offered on our website by remembering your preferences and choices on the website and the application. For example, they allow us to remember our choice of language or the font size chosen while reading a text.



Name

Provider 

Purpose

Expiry

_ga

Google

Analytics used to distinguish users

2 years

_gid

Google

Analytics used to distinguish users

1 day

_hjIncludedInSample

HotJar

Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

1 year

_hjid

Hotjar

Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

1 year

_pk_id.1.fc50

Matomo

(used to store a few details about the user such as the unique visitor ID)

13 month

_ym_d

Yandex

Yandex collects information that allows us to understand your interaction with our Website, track attendance rates, so we can improve user characteristics

1 year

_ym_isad, _ym_uid, _ym_visorc

Yandex

These cookies are used by Yandex Metrica as part of their embedded services on the Website.

_ym_isad = 2days, _ym_visorc=30minutes, rest 1 year

_ym_wasSynced

Yandex

User ID in Google analytics Yandex.Metrika

1 day




Performance Cookies 

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us know which pages are the most and least popular and see how visitors move around the site. All the information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies, we will not know when you have visited our site.

Name

Provider 

Purpose

Expiry

_ga

Google

Used to distinguish users.

2 years

_gid

Google

Used to distinguish users.

24 hours

_gat

Google

Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.

1 minute

AMP_TOKEN

Google

Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.

30 seconds to 1 year

_gac_

Google

Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

90 days

__utma

Google

Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.

2 years from set/update

__utmt

Google

Used to throttle request rate.

10 minutes

__utmb

Google

Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.

30 mins from set/update

__utmc

Google

Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.

End of browser session

__utmz

Google

Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.

6 months from set/update

__utmv

Google

Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

2 years from set/update

__utmx

Google

Used to determine a user's inclusion in an experiment.

18 months

__utmxx

Google

Used to determine the expiry of experiments a user has been included in.

18 months

_gaexp

Google

Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.

Depends on the length of the experiment, but typically 90 days.

_opt_awcid

Google

Used for campaigns mapped to Google Ads Customer IDs.

24 hours

_opt_awmid

Google

Used for campaigns mapped to Google Ads Campaign IDs.

24 hours

_opt_awgid

Google

Used for campaigns mapped to Google Ads Ad Group IDs

24 hours

_opt_awkid

Google

Used for campaigns mapped to Google Ads Criterion IDs

24 hours

_opt_utmc

Google

Stores the last utm_campaign query parameter.

24 hours

_cf_bm

ZENDESK

This Cloudflare cookie helps manage incoming traffic that matches criteria associated with bots.
If interested to learn more, Cloudflare provides further detail about some of their Cookies on the Cloudflare website here: Understanding the Cloudflare Cookies

30 minutes

_cfruid

ZENDESK

Cloudflare cookie used in cases were multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.

Session

_cfduid

ZENDESK

Cloudflare cookie used for security restrictions.

30 days

_zendesk_shared_session

ZENDESK

Authentication cookie - set to be anonymous

8 hours
Session duration is configurable by the Subscriber using the Session Expiration config in Admin Center > Security Settings. Can be anything from 5 minutes to 2 weeks. Default is 8 hours.

_zendesk_authenticated

ZENDESK

This is a flag set when a user is authenticated to display the most up to date content.

Session

_gat

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.
See here to enable or disable these Google Analytics Cookies:Enabling Google Analytics for your Help Center

1 minute

_gid

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.

1 day

_ga

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.

2 years

hc:{user_identifier}:recently_ visited_articles

ZENDESK

[LOCAL STORAGE] To help subscribers understand the resources an end-user has attempted in seeking support, this object tracks recently-viewed articles within the help center.
This Cookie allows Zendesk customers to identify an end-user's recently-viewed articles. If used exclusively by Subscriber for providing customer support purposes, this could be deemed Essential.

Forever (Local Storage)

articleVotes

ZENDESK

Article anonymous votes (localStorage or if not available falls back to a session cookie)

Forever (Local Storage)/Session (cookie)

_help_center_session

ZENDESK

Stores unique session key for Help Center product.

Session

ob-{public-api-key}

ZENDESK

Connect js snippet

3 years

_zendesk_nps_session

ZENDESK

Stores a unique key for a session, for landing page after responding to an NPS survey (if enabled)

Session

.appUserId

ZENDESK

Stores the appUser ID for the current session
Sunshine Conversations Web Messenger will not drop any Cookies until the widget is initiated by the End-User. If you wish to further control these Cookies using a third-party cookie solution, that is supported.

Forever

.clientId

ZENDESK

Unique identifier of the SDK instance

Forever

.sessionToken

ZENDESK

Session token to be used to authenticate requests on behalf of an anonymous user. Session tokens are linked to a client ID (see clientId)

Forever

lsid

ZENDESK

(From Stripe)

Session

ab_disable_remember_me

ZENDESK

(From Stripe)

Session

cid

ZENDESK

(From Stripe) Stripe analytics "client ID" used for service improvement

Session

checkout-test-session / checkout-live-session

ZENDESK

(From Stripe) Used to power Legacy Checkout's Remember Me function

1 year

ZD-zE_oauth

ZENDESK

Stores the authentication token once the user has been authenticated.
Web Widget offers pre-built API functionality for cookie consent; see here:Web Widget Cookie Permission in Developer Center
Alternatively, these Cookies respect external cookie bot functionality as well.

2 hours

ZD-settings

ZENDESK

Stores a hash of settings so that we don't keep sending requests to our backend

forever

ZD-suid

ZENDESK

Session id for Sunshine (if Sunshine functionality is being used)

20 minutes

ZD-buid

ZENDESK

Collects Machine ID for use in Sunshine (if Sunshine functionality is being used)

forever

ZD-store

ZENDESK

Ensures consistent presentation of the Web Widget when an End-User navigates to a new web page.

forever

__zlcmid

ZENDESK

Store visitor's machine-id for the Chat widget's authentication
Chat Widget offers out-of-the-box cookie consent management, see here: Enabling cookie consent for the Chat widget & Web SDK
Alternatively, these Chat Cookies respect external cookie bot functionality as well.

1 year

__zlcprivacy

ZENDESK

Store visitor's decision on CookieLaw

1 year

__zlcstore

ZENDESK

[Local Storage] Store visitor's account settings locally

forever

zte2095

ZENDESK

Used to identify the domain/subdomain the Chat Widget is located on.

Session

AWSALB

ZENDESK

Used to ensure user session remains with the same AWS instance to improve performance and stability.

Session

AWSALBCORS

ZENDESK

Used to ensure user session remains with the same AWS instance to improve performance and stability.

Session

JAR

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.
These Google reCAPTCHA Cookies (JAR-SSID) apply on Help Center pages if sign-ins are enabled, and with respect to submitting tickets, if enabled. reCAPTCHA for submitting tickets can be disabled within the help center settings if desired.

30 days

APISID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

CONSENT

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

20 years

DV

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

session

HSID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

NID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

6 months

SAPISID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

SID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

SIDCC

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

3 months

SSID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

_ga

Google

Analytics used to distinguish users

2 years

_gid

Google

Analytics used to distinguish users

1 day

_hjIncludedInSample

HotJar

Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

1 year

_hjid

Hotjar

Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

1 year

_pk_id.1.fc50

Matomo

(used to store a few details about the user such as the unique visitor ID)

13 month

_ym_d

Yandex

Yandex collects information that allows us to understand your interaction with our Website, track attendance rates, so we can improve user characteristics

1 year

_ym_isad, _ym_uid, _ym_visorc

Yandex

These cookies are used by Yandex Metrica as part of their embedded services on the Website.

_ym_isad = 2days, _ym_visorc=30minutes, rest 1 year

_ym_wasSynced

Yandex

User ID in Google analytics Yandex.Metrika

1 day



Targeting Cookies 

We use Cookies to promote products and services to your side on our website or on platforms other than our website. Furthermore, we may cooperate with some of our business partners to advertise and promote some products to your side on or off our website. For example, Cookies can be used to track whether you have clicked on an advertisement you see on our website and whether you have benefited from the service on the website directed by that advertisement after the has appealed to your side. 



Name

Provider 

Purpose

Expiry

_ga

Google

Used to distinguish users.

2 years

_gid

Google

Used to distinguish users.

24 hours

_gat

Google

Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.

1 minute

AMP_TOKEN

Google

Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.

30 seconds to 1 year

_gac_

Google

Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

90 days

__utma

Google

Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.

2 years from set/update

__utmt

Google

Used to throttle request rate.

10 minutes

__utmb

Google

Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.

30 mins from set/update

__utmc

Google

Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.

End of browser session

__utmz

Google

Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.

6 months from set/update

__utmv

Google

Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

2 years from set/update

__utmx

Google

Used to determine a user's inclusion in an experiment.

18 months

__utmxx

Google

Used to determine the expiry of experiments a user has been included in.

18 months

_gaexp

Google

Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.

Depends on the length of the experiment, but typically 90 days.

_opt_awcid

Google

Used for campaigns mapped to Google Ads Customer IDs.

24 hours

_opt_awmid

Google

Used for campaigns mapped to Google Ads Campaign IDs.

24 hours

_opt_awgid

Google

Used for campaigns mapped to Google Ads Ad Group IDs

24 hours

_opt_awkid

Google

Used for campaigns mapped to Google Ads Criterion IDs

24 hours

_opt_utmc

Google

Stores the last utm_campaign query parameter.

24 hours

_cf_bm

ZENDESK

This Cloudflare cookie helps manage incoming traffic that matches criteria associated with bots.
If interested to learn more, Cloudflare provides further detail about some of their Cookies on the Cloudflare website here: Understanding the Cloudflare Cookies

30 minutes

_cfruid

ZENDESK

Cloudflare cookie used in cases were multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.

Session

_cfduid

ZENDESK

Cloudflare cookie used for security restrictions.

30 days

_zendesk_shared_session

ZENDESK

Authentication cookie - set to be anonymous

8 hours
Session duration is configurable by the Subscriber using the Session Expiration config in Admin Center > Security Settings. Can be anything from 5 minutes to 2 weeks. Default is 8 hours.

_zendesk_authenticated

ZENDESK

This is a flag set when a user is authenticated to display the most up to date content.

Session

_gat

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.
See here to enable or disable these Google Analytics Cookies:Enabling Google Analytics for your Help Center

1 minute

_gid

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.

1 day

_ga

ZENDESK

Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.

2 years

hc:{user_identifier}:recently_ visited_articles

ZENDESK

[LOCAL STORAGE] To help subscribers understand the resources an end-user has attempted in seeking support, this object tracks recently-viewed articles within the help center.
This Cookie allows Zendesk customers to identify an end-user's recently-viewed articles. If used exclusively by Subscriber for providing customer support purposes, this could be deemed Essential.

Forever (Local Storage)

articleVotes

ZENDESK

Article anonymous votes (localStorage or if not available falls back to a session cookie)

Forever (Local Storage)/Session (cookie)

_help_center_session

ZENDESK

Stores unique session key for Help Center product.

Session

ob-{public-api-key}

ZENDESK

Connect js snippet

3 years

_zendesk_nps_session

ZENDESK

Stores a unique key for a session, for landing page after responding to an NPS survey (if enabled)

Session

.appUserId

ZENDESK

Stores the appUser ID for the current session
Sunshine Conversations Web Messenger will not drop any Cookies until the widget is initiated by the End-User. If you wish to further control these Cookies using a third-party cookie solution, that is supported.

Forever

.clientId

ZENDESK

Unique identifier of the SDK instance

Forever

.sessionToken

ZENDESK

Session token to be used to authenticate requests on behalf of an anonymous user. Session tokens are linked to a client ID (see clientId)

Forever

lsid

ZENDESK

(From Stripe)

Session

ab_disable_remember_me

ZENDESK

(From Stripe)

Session

cid

ZENDESK

(From Stripe) Stripe analytics "client ID" used for service improvement

Session

checkout-test-session / checkout-live-session

ZENDESK

(From Stripe) Used to power Legacy Checkout's Remember Me function

1 year

ZD-zE_oauth

ZENDESK

Stores the authentication token once the user has been authenticated.
Web Widget offers pre-built API functionality for cookie consent; see here: Web Widget Cookie Permission in Developer Center
Alternatively, these Cookies respect external cookie bot functionality as well.

2 hours

ZD-settings

ZENDESK

Stores a hash of settings so that we don't keep sending requests to our backend

forever

ZD-suid

ZENDESK

Session id for Sunshine (if Sunshine functionality is being used)

20 minutes

ZD-buid

ZENDESK

Collects Machine ID for use in Sunshine (if Sunshine functionality is being used)

forever

ZD-store

ZENDESK

Ensures consistent presentation of the Web Widget when an End-User navigates to a new web page.

forever

__zlcmid

ZENDESK

Store visitor's machine-id for the Chat widget's authentication
Chat Widget offers out-of-the-box cookie consent management, see here: Enabling cookie consent for the Chat widget & Web SDK
Alternatively, these Chat Cookies respect external cookie bot functionality as well.

1 year

__zlcprivacy

ZENDESK

Store visitor's decision on CookieLaw

1 year

__zlcstore

ZENDESK

[Local Storage] Store visitor's account settings locally

forever

zte2095

ZENDESK

Used to identify the domain/subdomain the Chat Widget is located on.

Session

AWSALB

ZENDESK

Used to ensure user session remains with the same AWS instance to improve performance and stability.

Session

AWSALBCORS

ZENDESK

Used to ensure user session remains with the same AWS instance to improve performance and stability.

Session

JAR

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.
These Google reCAPTCHA Cookies (JAR-SSID) apply on Help Center pages if sign-ins are enabled, and with respect to submitting tickets, if enabled. reCAPTCHA for submitting tickets can be disabled within the help center settings if desired.

30 days

APISID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

CONSENT

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

20 years

DV

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

session

HSID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

NID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

6 months

SAPISID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

SID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

SIDCC

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

3 months

SSID

ZENDESK

Used to allow human users easy access to Zendesk features, while blocking actions by bots.

2 years

_ga

Google

Analytics used to distinguish users

2 years

_gid

Google

Analytics used to distinguish users

1 day

_hjIncludedInSample

HotJar

Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

1 year

_hjid

Hotjar

Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

1 year

_pk_id.1.fc50

Matomo

(used to store a few details about the user such as the unique visitor ID)

13 month

_ym_d

Yandex

Yandex collects information that allows us to understand your interaction with our Website, track attendance rates, so we can improve user characteristics

1 year

_ym_isad, _ym_uid, _ym_visorc

Yandex

These cookies are used by Yandex Metrica as part of their embedded services on the Website.

_ym_isad = 2days, _ym_visorc=30minutes, rest 1 year

_ym_wasSynced

Yandex

User ID in Google analytics Yandex.Metrika

1 day



What types of personal data do we receive through cookies?

Examples of the types of personal data we receive through the cookies we use are listed below. This includes information we access directly from your device without storing or accessing a file:

• Cookie browser data: cookie identifiers, time/date, services/products selected, whether and to which cookies you have consented;

• Device data: device type, screen resolution, operating system version, browser rendering core, its version and basic settings;

• Log data: Time and duration of usage of our website and search data;

• Location data: Data about your country of access as proclaimed by your device;

• Behavioural data: Data about your usage of our website that we may process if you visit or use third party sites or applications to cooperate with us, and data on how you participate with the content of our website (such as pages visited, if you came from a marketing campaign, button clicks etc.)



  1. How can You Control the Use of Cookies? 

 

The preferences of our visitors and users regarding the use of cookies and similar technologies are constitute the basis for us. However, cookies which are essential for the Platform to operate must be used. Furthermore, we would like to remind you that in the case some Cookies are turned off, certain functions of the Platform may not partially or completely work.



You can always manage your preferences in the "Manage Cookies" section. 



Please note that using the tools might include transfer of your data to recipients outside of the EEA where there is no adequate level of data protection pursuant to the Law (e.g. the USA). Also in that third there might not be a supervisory authority and/or data processing principles and/or data subject rights might not be provided for in the third country.



The information on how you can manage your preferences for cookies used in the Platform is as follows: 





  1. User rights 
    To ensure complete control over your information, you have a comprehensive set of rights that you can use to manage how we process your data.

Your rights 
Should you have cause for complaint, you can find an outline of your rights below. To exercise your rights, please use the Customer Data Request Web form on https://datarequest.bsh-group.com

Your right to information about your data
We will provide you with information about the data we hold about you on request. 

Your right to correct and complete your data
We will correct inaccurate information about you if you notify us accordingly. We will complete incomplete data if you notify us accordingly, provided this data is necessary for the intended purpose of processing your data.

Your right to delete your data
We will delete the information we hold about you on request. However, some data will only be deleted subject to a defined period of retention, for example because we are required to retain the data by law in some cases, or because we require the data to fulfil our contractual obligations to you.

Your right to have your data blocked
In certain legally determined cases, we will block your data if you would like us to do so. Blocked data is only further processed to a very limited extent. 

Your right to withdraw consent
You can withdraw consent given for your data to be processed with effect for the future at any time. The legality of processing your data remains unaffected by this up to the point at which your consent is withdrawn.

Your right to object to the processing of your data 
You can object to the processing of your data with effect for the future at any time, if we are processing your data on the basis of one of the legal justifications set out in article 6(1e or 1f) of Regulation (EU) 2016/679. In the event that you object we will cease processing your data, provided that there are no compelling and legitimate grounds for further processing. The processing of your data for the purposes of direct marketing never constitutes compelling and legitimate grounds for us.

Your right to data portability
At your request, we can make certain information available to you in a structured, commonly used and machine-readable format. 

Your right to appeal to a regulatory authority
You can lodge an appeal pertaining to data protection with a data protection authority. To do so, contact the data protection authority responsible for your place of residence or the data protection authority under whose jurisdiction we fall (named below). 



  1. Your Point Of Contact For All Questions Relating To Data Protection



Please do not hesitate to contact us if you have questions relating to data protection

If you have any questions relating to data protection or exercising your rights, you can use the following contact information to get in touch with our data protection officer directly:

Vestel Trade Co.

vesteltrade@vestel.com.tr 

Organize Sanayi Bölgesi 45030 Manisa Turkey 


Last Updated on: 22/01/2021