De­Identified Data Sample Clauses

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 XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx 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.

De­Identified Data. To the extent Customer discloses or otherwise makes available Deidentified Data to Okta, or to the extent Okta generates Deidentified Data from Personal Data, Okta shall (1) implement technical safeguards that prohibit re-identification of the User to whom the information may pertain; (2) has implemented business processes that specifically prohibit re-identification of the Deidentified Data and prevent the inadvertent release of De-identified Data; and (3) make no attempt to reidentify the Deidentified Data.

De­Identified Data. 7.1. In the event that Company discloses or makes available Deidentified data (as such term is defined in the U.S. State Privacy Laws) to Vendor, Vendor shall not attempt to reidentify the information.

De­Identified Data. “Deidentified Data” means any data that has been de-identified, anonymized, or aggregated with other data on any anonymized or de-identified basis. Deidentified Data is owned by PreApp.

De­Identified Data. 29.1 In addition to requirements under Lilly's Vendor Privacy and Security Standard, Supplier will share with Lilly patient information only after suitable anonymisation.

De­Identified Data. 6.1. In the event that Subscriber discloses or makes available Deidentified data (as such term is defined in the State Privacy Laws) to Domo, Domo will not attempt to reidentify the information.

De­Identified Data. A. If Supplier receives Deidentified Data from or on behalf of Legends, then Supplier will: 1. take reasonable measures to ensure the information cannot be associated with a Data Subject. 2. publicly commit to Process the Deidentified Data solely in deidentified form and not to attempt to reidentify the information. 3. contractually obligate any recipients of the Deidentified Data to comply with the foregoing requirements and Applicable Data Protection Laws.

De­Identified Data. Customer acknowledges and agrees that Rapid7 may further use Personal Data it processes pursuant to this DPA for the purposes of creating analytical reports and service improvement, provided that Rapid7 first de-identifies the Personal Data such that neither Customer nor any individual data subject is directly identifiable from the data processed for these purposes. Rapid7 and Customer have caused this DPA to be executed by their duly authorized representatives as of the Effective Date. Signature: Printed Name: Signature: Xxxxxxx X'Xxxx Printed Name: Title: Title: Date Signed: Date Signed: Terms used but not defined in this Appendix shall have the meanings given to them in the Rapid7 Data Processing Addendum and any Master Services Agreement, Terms of Service, End User License Agreement, or other written or electronic agreement between Rapid7 and Customer for the purchase of Services. A. LIST OF PARTIES Controller(s) / Data exporter(s): 1. Name: The Customer. The Customer's details are specified in the Agreement for the Services with Rapid7. Address: As above. Contact person’s name, position and contact details: As above. Activities relevant to the data transferred under these Clauses: The Customer has purchased Services from Rapid7 pursuant to the Agreement. Signature and date: This Annex I shall be deemed executed upon execution of the DPA. Role (controller/processor): Controller. 1. Name: Each non-EEA and non-UK member of the Rapid7 group of companies, details of which can be found at xxxxx://xxx.xxxxx0.xxx/legal/subprocessors/. Address: As above. Contact person’s name, position and contact details: Senior Legal Counsel (Privacy) Email: xxxxxxx@xxxxx0.xxx Activities relevant to the data transferred under these Clauses: Provision of Services to the Customer pursuant to the Agreement. Signature and date: This Annex I shall be deemed executed upon execution of the DPA. Role (controller/processor): Processor.

De­Identified Data. De­Identified Data may be used for any lawful purpose including, but not limited to, operating and improving the Services. Summit Learning’s use of such De­Identified Data shall survive termination of this Data Privacy Addendum or any request by Partner School to return or destroy Student Data. Summit Learning agrees not to attempt or have any third party attempt to re­identify De­Identified Data.

De­Identified Data. De­Identified Data may be used for any lawful purpose including, but not limited to, operating and improving the System. RCA’s use of such De­Identified Data shall survive termination of this Data Privacy Addendum or any request by Partner School to return or destroy Student Data. RCA agrees not to attempt or have any third party attempt to re­identify De­Identified Data.