2.3. The customer and MZ acknowledge that the customer is, within the meaning of data protection legislation, the data manager and MZ responsible for all the customer`s data. 1. „T`h`e`r`e`l`a`n`n`p`r`a „W.,W“ “ – “ The steps described below show a typical user path to policy, starting with the account setting page linked by webex.com. Each data protection assessment contains an overall assessment. Higher scores (up to 100%) means that the product offers more transparent privacy policies, with better procedures for protecting users` data. The score is best used as an indicator of the amount of extra work a person needs to do to make an informed decision about a product. This secondary document is expressly committed to encrypting as a means of protecting information. These obligations include clear language on dormant data and the ability to encrypt end-to-end. The language around the different types of encryption and how the use of end-to-end encryption can be implemented brings useful clarity. (c) any other communication, directly or indirectly, relating to the processing of personal data under this agreement; and in all cases, MZ will provide without delay the information and assistance that the customer reasonably needs to respond and resolve the request, complaint or other communication within a time frame imposed by existing data protection legislation. Cisco`s definition of personal data is fairly broad and comprehensive, which has the potential to provide additional protection for Cisco`s data. If additional safeguards are proposed, that is a good thing.
While there are broad rights to disclose, disclose or transfer personal data, the broad definition of personal data has a negative impact on privacy. Cisco`s privacy policy does not contain essential details about the use – or restrictions on use – of the data they collect to optimize or develop automated data analytics. A secondary policy describing Webex-specific features describes how Webex can use data for facial recognition when a user chooses to use it. The document of the trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/cisco-webex-meetings-privacy-data-sheet.pdf directive is also taken into consideration, although this document is not presented to end-users at the time of account setting. The fact that this document is not submitted to end-users during the account-setting process raises an interesting question: can an end user accept conditions that they do not know exist? The document under the link above is listed as version 4.0, updated in April 2020. In this overview, this document is called the „webex directive“ or „secondary directive.“ All communications on the Webex meetings platform are via encrypted channels. After setting up a session, all media streams (audio, VOIP, video, screen sharing and document sharing) are encrypted. The service then encrypts the media feed again before it is sent to other users.
Note that if a client allows participants to participate in their meetings via third-party video end points, these participants can send their meeting data over the Internet without encryption. Media streams that flow from a user to Cisco Webex meeting servers are deciphered after passing through the Cisco firewalls. This allows Cisco to provide network-based recording and SIP-based call support for video end points. (i) regarding conference and collaboration clients, the name and email address (almost always business email address) of: conference organizers, participants in managerial events (where the customer ordered LA MZ to collect this information) and Cisco product users This document contains data storage and erasure windows that are fairly general and complete.
