JumpCloud Data Transfer Mechanism Sample Clauses

JumpCloud Data Transfer Mechanism. For all transfers from the EEA of Customer Personal Data pursuant to the Agreement, the parties hereby incorporate the Standard Contractual Clauses approved by the European Commission (the “SCCs”) as Exhibit A. To the extent there is any conflict between the terms of this DPA and the SCCs, the SCCs shall control to the extent of the conflict. The SCCs will apply only with respect to Customer Personal Data transferred from the EEA (if any). Customer shall take all reasonable steps to determine whether the parties are required under the Applicable Data Protection Laws to either: (a) register the SCCs with any supervisory authority in any member state of the EEA, or (b) procure approval from each such supervisory authority for the transfer referred to in the SCCs and shall promptly inform JumpCloud upon becoming aware of such requirements. With respect to data transfers from the United Kingdom to the United States, the parties hereby incorporate the 2010 Controller-to-Processor standard contractual clauses found at the following link: xxxxx://xxx- xxx.xxxxxx.xx/XxxXxxXxxx/XxxXxxXxxx.xx?uri=OJ:L:2010:039:0005:0018:EN:PDF.
Sample 1
AutoNDA by SimpleDocs
JumpCloud Data Transfer Mechanism. For all transfers from the EEA of Customer Personal Data pursuant to the Agreement, the parties hereby incorporate Modules 2 and 3 of the Standard Contractual Clauses (as applicable) approved by the European Commission (the “SCCs”) as described in Exhibit A. To the extent there is any conflict between the terms of this DPA and the SCCs, the SCCs shall control to the extent of the conflict. The SCCs will apply only with respect to Customer Personal Data transferred from the EEA, if any. Customer shall take all reasonable steps to determine whether the parties are required under the Applicable Data Protection Laws to either: (a) register the SCCs with any supervisory authority in any member state of the EEA, or (b) procure approval from each such supervisory authority for the transfer referred to in the SCCs and shall promptly inform JumpCloud upon becoming aware of such requirements. With respect to transfers of Customer Personal Data from (y) the United Kingdom to the United States, the parties hereby incorporate the International Data Transfer Addendum to the SCCs attached hereto as Exhibit B, and (z) Switzerland to the United States, (i) in Clause 13 of the SCCs, the competent supervisory authority is the FADP and Information Commissioner (if the transfer is governed by FADP), (ii) references to “Member State” in the SCCs refer to Switzerland,
Sample 1
JumpCloud Data Transfer Mechanism. For all transfers of EU Personal Data pursuant to the Agreement, the parties hereby incorporate the Standard Contractual Clauses approved by the European Commission (the “SCCs”) as Schedule 2. To the extent there is any conflict between the body of this DPA and the SCCs, the SCCs shall control. If and when JumpCloud certifies compliance with Privacy Shield, the SCCs will no longer apply under this DPA. To the extent there is any conflict between the body of this DPA and the Standard Contractual Clauses, the Standard Contractual Clauses shall control. Customer shall take all reasonable steps to determine whether the parties are required under the Applicable Data Protection Laws to either: (i) register the SCCs with any Supervisory Authority in any member state of the EU and/or Switzerland, or (b) procure approval from any such Supervisory Authority for the transfer referred to in the SCCs. Customer shall promptly inform JumpCloud upon becoming aware of such requirements.
Sample 1
JumpCloud Data Transfer Mechanism. For all transfers from the EEA of Customer Personal Data pursuant to the Agreement, the parties hereby incorporate the Standard Contractual Clauses approved by the European Commission (the “SCCs”) as Schedule 2. To the extent there is any conflict between the body of this DPA and the SCCs, the SCCs shall control. The SCCs will apply solely with respect to Customer Personal Data transferred from the EEA (if any). Customer shall take all reasonable steps to determine whether the parties are required under the Applicable Data Protection Laws to either:
Sample 1
JumpCloud Data Transfer Mechanism. For all transfers from the EEA of Customer Personal Data pursuant to the Agreement, the parties hereby incorporate Modules 2 and 3 of the Standard Contractual Clauses (as applicable) approved by the European Commission (the “SCCs”) as described in Exhibit A. To the extent there is any conflict between the terms of this DPA and the SCCs, the SCCs shall control to the extent of the conflict. The SCCs will apply only with respect to Customer Personal Data transferred from the EEA, if any. Customer shall take all reasonable steps to determine whether the parties are required under the Applicable Data Protection Laws to either: (a) register the SCCs with any supervisory authority in any member state of the EEA, or (b) procure approval from each such supervisory authority for the transfer referred to in the SCCs and shall promptly inform JumpCloud upon becoming aware of such requirements. With respect to data transfers from the United Kingdom to the United States, the parties hereby incorporate the International Data Transfer Addendum to the SCCs attached hereto as Exhibit B.
Sample 1

Related to JumpCloud Data Transfer Mechanism

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Rules of Grievance Processing 1. Time limits of any stage of the grievance procedure may be extended by written mutual agreement of the parties at that step.

Time is Money Join Law Insider Premium to draft better contracts faster.