Destruction or Return of District Data Sample Clauses

Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Contractor to use after termination or expiration of this Addendum, or District Data for which Contractor has specifically obtained consent from the parent, legal guardian or student to keep, no later than (30) calendar days after termination or expiration of this Addendum, Contractor shall certify in writing that all District Data and PII that Contractor collected, generated or inferred pursuant to the Contract (“Contract Data”), is securely returned or Securely Destroyed, pursuant to Schedule 4 attached hereto.
Sample 1Sample 2Sample 3See All (33)
AutoNDA by SimpleDocs
Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Contractor to use after termination or expiration of this Agreement, or District Data for which Contractor has specifically obtained consent from the parent, legal guardian or student to keep, within thirty (30) calendar days after termination or expiration of this Agreement, Contractor shall ensure that all District Data and PII that Contractor collected, generated or inferred pursuant to the Contract (“Contract Data”), is securely returned or Securely Destroyed, as directed by the District. In the event that the District requests destruction, Contractor agrees to Securely Destroy all District Data and Contract Data that is in its possession and cause its Subcontractors to Securely Destroy all District Data and Contract Data that is in the possession of any Subcontractors. If the District requests return, Contractor shall securely return all District Data and Contract Data to the authorized person specified by the District, using the methods requested by the District, in its discretion, including any applicable fees charged to the District by the Contractor. The Contractor shall promptly certify in writing to District that such District Data and Contract Data has been disposed of or returned securely.
Sample 1Sample 2Sample 3See All (17)
Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Infinite Campus to use after termination or expiration of this Agreement, or District Data for which Infinite Campus has specifically obtained consent from the parent, legal guardian or student to keep, within thirty (30) calendar days after termination or expiration of this Agreement, Infinite Campus shall ensure that all District Data and PII that Infinite Campus collected, generated or inferred pursuant to the XXXX (“XXXX Data”), is securely returned or Securely Destroyed, as directed by the District. In the event that the District requests destruction, Infinite Campus agrees to Securely Destroy all District Data and XXXX Data that is in its possession and cause its Subcontractors to Securely Destroy all District Data and XXXX Data that is in the possession of any Subcontractors. If the District requests return, Infinite Campus shall securely return all District Data and XXXX Data to the authorized person specified by the District, using the methods requested by the District, in its discretion, including any applicable fees charged to the District by Infinite Campus. Infinite Campus shall promptly certify in writing to District that such District Data and XXXX Data has been disposed of or returned securely.
Sample 1Sample 2Sample 3See All (6)
Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Contractor to use after termination or expiration of this Addendum pursuant to Schedule 3, or District Data for which Contractor has specifically obtained consent from the parent, legal guardian or student to keep, no later than
Sample 1Sample 2Sample 3See All (4)
Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Partner to use after termination or expiration of the Agreement, or District Data for which Partner has specifically obtained consent from the parent, legal guardian or student to keep, no later than (30) calendar days after termination or expiration of the Agreement, Partner shall certify in writing that all District Data and PII that Partner collected, generated or inferred pursuant to the Agreement (“Contract Data”), is securely returned or Securely Destroyed, pursuant to Schedule 4 attached hereto.
Sample 1
Destruction or Return of District Data. All District Data received by Consultant under this Agreement shall be destroyed or returned to District when it is no longer needed for the Study and no later than years after the District Data is first received.
Sample 1
Destruction or Return of District Data. The District is in full control over the District Data at all times through the administrator dashboard feature. The District is able to delete student personally identifiable information at any time and in real time using the administrator dashboard. Once that information is deleted, it is deleted from Contractor’s servers – first from Contractor’s servers and then, after two weeks later, from any back-up server. If information was not deleted by the District before the subscription expired or is terminated, Contractor retains such information for a limited period of six (6) months after expiration or termination.
Sample 1
AutoNDA by SimpleDocs
Destruction or Return of District Data. With the exception of De-identified Data that District has specifically agreed in writing to allow Contractor to use after termination or expiration of this Agreement, or District Data for which Contractor has specifically obtained consent from the parent, legal guardian or student to keep, no later than (30) calendar days after termination or expiration of this Agreement, Contractor shall, upon written request by District, certify in writing that all District Data and PII that Contractor collected, generated or inferred pursuant to the Contract (“Contract Data”), is securely returned, where feasible, or Securely Destroyed, pursuant to Schedule 4 attached hereto. Without prejudice to the foregoing, Contractor may keep copies and/or backups of data as part of its disaster recovery storage system, provided DPS Software Services Agreement 35 Version 3.0 – Updated 3/25/2020 such data is (a) inaccessible to the public; (b) unable to be used in the normal course of business by the Contractor; and (c) deleted after a maximum term of thirteen (13) months since the creation of said copies and/or backups. In case such copies and/or backups are used by the Contractor to repopulate accessible data following a disaster recovery, the District shall be entitled to demand from the Contractor the immediate deletion of said copies and/or backups, by sending a written request at xxxxxxx@xxxxxxxx.xxx.
Sample 1

Related to Destruction or Return of District Data

  • Duration of processing and erasure or return of data Processing by the data importer shall only take place for the duration specified in Annex I.

  • Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA. (b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction. (c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors. (d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e). (b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!