Podmínky užívání
POUŽÍVÁNÍM TĚCHTO STRÁNEK SOUHLASÍTE S TĚMITO PODMÍNKAMI. POKUD S TĚMITO PODMÍNKAMI NESOUHLASÍTE, TYTO STRÁNKY NEPOUŽÍVEJTE.
Ochrana dat
Společnost Vestel může sbírat, spravovat a zpracovávat informace, které tyto strany poskytnou společnosti Vestel. Tyto informace budou použity při nákupu a pro další oddělení společnosti VEstel a také pro přidružené společnosti.
Mlčenlivost
Vy a vaše společnost musíte uchovávat jakékoli informace z portálu pro dodavatele a z registrační stránky společnosti Vestel jako důvěrné. Pokud se zaregistrujete jako možný dodavatel v portálu dodavatelů společnosti Vestel, uchování vašeho účtu a hesla, které získáte v druhém kroku, je ve vaší odpovědnosti. Pokud tak neučiníte, bude používání vašeho účtu bez odkladu zrušeno.
Stanovisko
Společnost Vestel může používat informace, které jste předali, pro účely předběžné kvalifikace. Společnost Vestel nepřejímá žádnou odpovědnost za náklady na registrační proces. Tato předběžná registrace jako prodejce společnosti Vestel není zárukou objednávky na dodávky zboží nebo služeb do společnosti Vestel ani nezavazuje nijak společnost Vestel k jakékoli dohodě.
Potvrzení
Přijetím Podmínek potvrzujete, že jste oprávněni předkládat informace o nebo jménem určených osob nebo subjektů, a že poskytnuté informace jsou pravdivé a správné, a že zcela chápete a souhlasíte s Podmínkami.
Změna
Společnost Vestel může tyto Podmínky kdykoli aktualizovat a vyhrazuje si právo na změny ve své politice, kdykoli a bez ohlášení.
Zřeknutí se odpovědnosti partnera: Google, Google Play, YouTube, Android TV a další ochranné známky jsou ochranné známky společnosti Google LLC. Asistent Google není k dispozici v některých jazycích a zemích.
- Home
-
TV
Prozkoumejte televizory
Zobrazit všechny TVDalší informace
- Zvuk
- Podpora produktů
TV, která dokonale zapadne do vašeho světa
Další informace
Cookie Management
In order to serve you better, cookies are used on our website. By clicking the "Accept All Cookies" button, you accept the use of cookies for the purposes of making our website compatible with the user, improving the performance of the website, analyzing user behavior provided that no data directly identifies you and for offering personalized advertising activities. You can find detailed information about cookies in our Cookie Policy You can always manage your preferences in the Manage Cookies section.
Strictly Necessary Cookies
Always Active
You can always control the cookies used by Vestel Trade Co. on our website. If you agree to the use of cookies, you can directly click the "Save" button below. You can find detailed information about cookies in our Cookie Policy.
We would like to state that technically required cookies are used to perform the primary functions of our website. The use of such cookies is not dependent on your consent, since they are imperative for our website to function correctly. You can find the list of strictly necessary cookies that are used by website in Cookie Policy.
Show/Hide Cookies
| Name | Provider | Purpose | Expiry |
|---|---|---|---|
| PHPSESSID | TOSHIBA | HOLDS USER LOGIN ACTIVITY | 1 year |
| COOKIEPREF | TOSHIBA | HOLDS USERS COOKIE PREFERENCES | 1 year |
Functional Cookies
Cookies, also known as preference cookies, are those that allow the website to remember your past preferences such as the language used or the region preferred or the user name and password providing automatic login.
You can find the list of functional cookies that are used by website in Cookie Policy.
Show/Hide Cookies
| Name | Provider | Purpose | Expiry |
|---|---|---|---|
| _ga | Analytics used to distinguish users | 2 years | |
| _gid | Analytics used to distinguish users | 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.
You can find the list of performance cookies that are used by website in Cookie Policy.
Show/Hide Cookies
| Name | Provider | Purpose | Expiry |
|---|---|---|---|
| _ga | Used to distinguish users. | 2 years | |
| _gid | Used to distinguish users. | 24 hours | |
| _gat | 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 | 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_ | 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 | 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 | Used to throttle request rate. | 10 minutes | |
| __utmb | 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 | 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 | 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 | 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 | Used to determine a user's inclusion in an experiment. | 18 months | |
| __utmxx | Used to determine the expiry of experiments a user has been included in. | 18 months | |
| _gaexp | 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 | Used for campaigns mapped to Google Ads Customer IDs. | 24 hours | |
| _opt_awmid | Used for campaigns mapped to Google Ads Campaign IDs. | 24 hours | |
| _opt_awgid | Used for campaigns mapped to Google Ads Ad Group IDs | 24 hours | |
| _opt_awkid | Used for campaigns mapped to Google Ads Criterion IDs | 24 hours | |
| _opt_utmc | 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 | Analytics used to distinguish users | 2 years | |
| _gid | Analytics used to distinguish users | 1 day |
Targeting Cookies
These cookies are set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant ads on other sites. They work by uniquely identifying your browser and device. If you don't allow these cookies, you will not experience our targeted advertising across different websites as a result of these cookies. You can find the list of targeting cookies that are used by website in Cookie Policy.
Show/Hide Cookies
| Name | Provider | Purpose | Expiry |
|---|---|---|---|
| _ga | Used to distinguish users. | 2 years | |
| _gid | Used to distinguish users. | 24 hours | |
| _gat | 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 | 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_ | 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 | 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 | Used to throttle request rate. | 10 minutes | |
| __utmb | 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 | 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 | 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 | 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 | Used to determine a user's inclusion in an experiment. | 18 months | |
| __utmxx | Used to determine the expiry of experiments a user has been included in. | 18 months | |
| _gaexp | 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 | Used for campaigns mapped to Google Ads Customer IDs. | 24 hours | |
| _opt_awmid | Used for campaigns mapped to Google Ads Campaign IDs. | 24 hours | |
| _opt_awgid | Used for campaigns mapped to Google Ads Ad Group IDs | 24 hours | |
| _opt_awkid | Used for campaigns mapped to Google Ads Criterion IDs | 24 hours | |
| _opt_utmc | 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 | Analytics used to distinguish users | 2 years | |
| _gid | Analytics used to distinguish users | 1 day |