Joint Data Controller Sample Clauses

Joint Data Controller. The Parties qualify as joint data controller in relation to the processing of Personal Data via the common (online) storage place referred to in Article 26.2, where the contractual documents as well as contact information lists with regard to Party representatives, personnel and service providers are stored.
AutoNDA by SimpleDocs
Joint Data Controller. The Parties qualify as joint data controller in relation to the processing of Personal Data referred to in Article 18.11.1 to the extent such Personal Data are jointly stored by all Parties

Related to Joint Data Controller

  • Contractor’s Project Manager and Key Personnel Contractor shall appoint a Project Manager to direct the Contractor’s efforts in fulfilling Contractor’s obligations under this Contract. This Project Manager shall be subject to approval by the County and shall not be changed without the written consent of the County’s Project Manager, which consent shall not be unreasonably withheld. The Contractor’s Project Manager shall be assigned to this project for the duration of the Contract and shall diligently pursue all work and services to meet the project time lines. The County’s Project Manager shall have the right to require the removal and replacement of the Contractor’s Project Manager from providing services to the County under this Contract. The County’s Project manager shall notify the Contractor in writing of such action. The Contractor shall accomplish the removal within five (5) business days after written notice by the County’s Project Manager. The County’s Project Manager shall review and approve the appointment of the replacement for the Contractor’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Contractor’s Project Manager from providing further services under the Contract.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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