Protect Stored Data Clause Samples

The 'Protect Stored Data' clause requires parties to implement measures that safeguard data held within their systems from unauthorized access, loss, or corruption. This typically involves using encryption, access controls, and regular security audits to ensure that sensitive information, such as customer records or proprietary business data, remains secure while stored. The core function of this clause is to mitigate the risk of data breaches and ensure compliance with data protection regulations, thereby protecting both the data subjects and the parties involved from potential harm or liability.
Protect Stored Data. All sensitive cardholder data stored and handled by Stockport School and its employees must be securely protected against unauthorised use at all times. Any sensitive card data that is no longer required by Stockport School for business reasons must be discarded in a secure and irrecoverable manner. • If there is no specific need to see the full PAN (Permanent Account Number), it has to be masked when displayed. • PAN'S which are not protected as stated above should not be sent to the outside network via end user messaging technologies like chats, ICQ messenger etc., 1. The contents of the payment card magnetic stripe (track data) on any media whatsoever. 2. The CVV/CVC (the 3 or 4 digit number on the signature panel on the reverse of the payment card) on any media whatsoever. 3. The PIN or the encrypted PIN Block under any circumstance.
View SourceView Similar (6)
Protect Stored Data.  All sensitive cardholder data stored and handled by Gateway Solutions s.r.o. and its employees must be securely protected against unauthorised use at all times. Any sensitive card data that is no longer required by Gateway Solutions s.r.o. for business reasons must be discarded in a secure and irrecoverable manner.  If there is no specific need to see the full PAN (Permanent Account Number), it has to be masked when displayed.  PAN'S which are not protected as stated above should not be sent to the outside network via end user messaging technologies like chats, ICQ messenger etc., 1. The contents of the payment card magnetic stripe (track data) on any media whatsoever. 2. The CVV/CVC (the 3 or 4 digit number on the signature panel on the reverse of the payment card) on any media whatsoever. 3. The PIN or the encrypted PIN Block under any circumstance. 4. Information Classification
View SourceView Similar (2)
Protect Stored Data.  All sensitive cardholder data stored and handled by NYCDOT or by the Contractor and its employees on NYCDOT’s behalf must be securely protected against unauthorised use at all times. Any sensitive card data that is no longer required by NYCDOT for business reasons must be discarded in a secure and irrecoverable manner.  If there is no specific need to see the full PAN (Permanent Account Number), it has to be masked when displayed.  PAN'S which are not protected as stated above should not be sent to the outside network via end user messaging technologies like chats, ICQ messenger etc.
View Source

Related to Protect Stored Data

  • Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.

  • Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by ▇▇▇ to return or destroy Student Data. Except for Subprocessors, ▇▇▇▇▇▇▇▇ agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.