Data Leaks Clause Samples

Data Leaks. 1. The Parties have an appropriate policy for dealing with Data Leaks. 2. In the event that the Educational Institution or the Processor establish a Data Leak, the respective Party shall inform the other Party about this without unreasonable delay as soon as they learn about that Data Leak. In the event of a Data Leak all relevant information to the Data with regard to the Data Leak, including information on any developments related to the Data Leak measures taken by the Processor to limit the effects of the Data Leak and to prevent recurrence. 3. The Processor informs the Educational Institution immediately in the event that it suspects that a Data Leak probably entails a high level of risk for the rights and freedoms of natural persons as referred to in Article 34(1) of the GDPR. 4. In the event of a Data Leak, the Processor enables the Educational Institution to take appropriate subsequent steps or ensure that these are taken with regard to the Data Leak. The Processor must try to link this up with the existing processes that the Educational Institution has set up for this purpose. The Parties will take all reasonably required measures as soon as possible to prevent or limit (further) breaches or infringements concerning the Processing of Personal Data, and more particularly (further) breaches of the Applicable legislation and regulations concerning the Processing of Personal Data. 5. In the event of a Data Leak, the Educational Institution shall comply with any possible legal reporting options. In the event that a Data Leak affects multiple Educational Institutions to the same extent, the Processor can, after consulting one or more Data Controllers, notify the Dutch Data Protection Authority about the Data Leak on behalf of the Educational Institution. The Processor shall inform the Educational Institution of their intention to do this without delay (and prior to the notification if possible). 6. In the event that the Data Leak potentially entails a high level of risk for the rights and freedoms of natural persons, the Educational Institution shall inform the Involved Parties about the Data Leak. 7. The Parties will, in good faith and in mutual consultation, make arrangements about the reasonable distribution of any costs associated with complying with the reporting obligations. 8. The Parties shall document all Data Leaks in an (incident) register, including the facts relating to the infringement relating to personal data, the consequences of this and...
View Source
Data Leaks. 1. The Parties have an appropriate policy for dealing with Data Leaks.
View Source
Data Leaks. 5.1. We will notify You of any Data Leaks. We will strive to do so within 48 hours of Our discovery of any such Data Leak, or as soon as possible after We have been notified thereof by Our Sub- Processors. Further arrangements as to the relevant procedure are set forth in Article 11 of this Agreement. We will thereby provide You with such information as You will reasonably require - if necessary - to submit a correct and complete notification to the Data Protection Authority and possibly one or more Data Subjects for purposes of the Data Leaks Notification Duty, or We will forward the notification from Our Sub-Processor to You. We will also keep You informed of any measures implemented in response to the Data Leak by Us or by Our Sub- Processor. 5.2. You will at all times be solely responsible for notifying the Data Protection Authority and possibly one or more Data Subjects of any Data Leaks. 5.3. You will at all times be solely responsible for keeping a record of any Data Leaks.
View Source
Data Leaks. 1. The Parties have an appropriate policy for dealing with Data Leaks. 2. In the event that the Educational Institution or the Processor establish a Data Leak, the respective Party shall inform the other Party about this without unreasonable delay as soon as they learn about that Data Leak. In the event of a Data Leak, the Processor shall provide all relevant information with regard to the Data Leak to the Educational Institution, including information on any developments related to the Data Leak and measures taken by the Processor to limit the effects of the Data Leak and to prevent recurrence.
View Source
Data Leaks. 6.1 In the event that a possible Data Leak is discovered, ▇▇▇▇▇ will inform the Customer within 48 hours and provide the Customer with the information indicated in Addendum 3 (Process for reporting Data Leaks and information to be provided), so that the Customer can report this to the competent supervisory authority if necessary. 6.2 After informing the Customer of the Data Leak, ▇▇▇▇▇ will keep the Customer informed of new developments concerning the Data Leak and the measures that ▇▇▇▇▇ has taken to limit the extent of the Data Leak, to terminate it, and to enable it to avoid a similar incident in the future. 6.3 CARYA is not permitted to report a Data Leak to the competent supervisory authority or to inform the Data Subjects of the Data Leak. This is the responsibility of the Customer. 6.4 Any costs incurred in resolving the Data Breach and preventing its recurrence in the future are to be borne by the party that incurs the costs.
View Source

Related to Data Leaks

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.) 1.2. The CONTRACTOR must notify the COUNTY in advance and in writing of any location changes to CONTRACTOR’s data center(s) that will process or store County data.

  • System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.