Data Collection, Storage, and Use Sample Clauses

Data Collection, Storage, and Use. This Contract does not xxxxx Xxxx Xxxxx any rights to Dealer data, information, or other intellectual property that John Deere may receive under this Contract (“Dealer Content”) except for the right to use the data for the purpose of performing John Deere’s obligations to Dealer under this Contract. Dealer acknowledges that it has been notified of John Deere’s data collection practices set out in this clause and as otherwise set out in the global Enterprise Privacy Statement, the applicable region- or country-specific Privacy Statements and the Xxxx Deere Data Services and Subscriptions Data Policy Statement (all available at xxx.xxxxx.xxx) and agrees that John Deere may use the Dealer Content as described therein and in this Contract. Dealer acknowledges and agrees that the Dealer Content may be transferred out of the country where the Dealer Content is generated to other destinations, including but not limited to the United States of Americ a. In the event that the Dealer Content includes Dealer’s pers onal information, Dealer hereby consents to the collection, use and disclosure of such pers onal information, including with respect to the transfer of pers onal information to other jurisdictions, to permit John Deere and Authorized Dealers to access and use the Dealer Content as set forth in this Contract. DEALER WARRANTS THAT IT HAS PROVIDED THE NECESSARY NOTIFICATIONS, AND OBTAINED ANY NECESSARY CONSENT FROM ITS EMPLOYEES OR ANY OTHER THIRD PARTIES, INCLUDING WITH RESPECT TO THE TRANSFER OF DEALER CONTENT TO OTHER JURISDICTIONS, TO COMPLY WITH ANY APPLICABLE PRIVACY LAWS OR CONTRACTUAL AGREEMENTS WITH SUCH EMPLOYEES OR THIRD PARTIES AND TO PERMIT JOHN DEERE AND AUTHORIZED DEALERS TO ACCESS AND USE THE DEALER CONTENT AS SET FORTH IN THIS CONTRACT..
AutoNDA by SimpleDocs
Data Collection, Storage, and Use. This Contract does not xxxxx Xxxx Xxxxx any rights to Dealer data, information, or other intellectual property that John Deere may receive under this Contract (“Dealer Content”) except for the right to use the data for the purpose of performing John Deere’s obligations to Dealer under this Contract. In the event that the Dealer Content includes Dealer’s or third parties’ personal information, Dealer hereby consents to the collection, use and disclosure of such personal information, including with respect to the transfer of personal information to other jurisdictions, to permit John Deere and Authorized Dealers to access and use the Dealer Content as provided in this Contract. DEALER WARRANTS THAT IT HAS OBTAINED ANY NECESSARY CONSENT FROM ITS EMPLOYEES OR ANY OTHER INTERESTED THIRD PARTIES, INCLUDING WITH RESPECT TO THE TRANSFER OF DEALER CONTENT TO OTHER JURISDICTIONS, TO COMPLY WITH ANY APPLICABLE PRIVACY LAWS OR CONTRACTUAL AGREEMENTS WITH SUCH EMPLOYEES OR THIRD PARTIES AND TO PERMIT JOHN DEERE AND AUTHORIZED DEALERS TO ACCESS AND USE THE DEALER CONTENT AS PROVIDED IN THIS CONTRACT.
Data Collection, Storage, and Use. Nutrien acknowledges that this Contract does not grant Nutrien any rights to Customer data or information (“Customer Content”) that Nutrien may receive under this Contract except for the rights of use described below and in the AGBRIDGE™ Data Services and Subscriptions Data Policy. Advisers authorized by Customer through a Linked Account to access and use the Customer Content are “Authorized Advisers.” Customer acknowledges that it has been notified of Data Services and Subscriptions Data Policy and Customer hereby grants Nutrien the right to use Customer Content as described in this Contract and as needed to provide AGBRIDGE™ Services under this Contract, including, for example, collecting and hosting Customer Content. This permission extends to third parties engaged by Nutrien in connection with providing the AGBRIDGE™ Services. Without limiting the foregoing, Customer acknowledges and agrees that Nutrien may disclose Customer Content to outside parties to (a) comply with any applicable law, regulation or compulsory legal request; (b) protect the safety of any person from death or serious bodily injury;
Data Collection, Storage, and Use. As ReScore is primarily a data storage and reporting system, the Council retains the right to collect, store, aggregate, any and all information uploaded to the system by the Organization and its appointed Users. Any data submitted to the ReScore system is available to the Council for use in its data aggregation activities and reporting without individual attribution. No data submitted within the ReScore system shall be attributed to or used to identify any individual organization publicly or privately by the Council. The Council retains the right and ability to aggregate performance results reported within ReScore in order to demonstrate and communicate the cumulative impacts and social and/or environmental value of projects recorded within ReScore (e.g. total greenhouse gas emissions calculated, reported, mitigated by all projects reporting within ReScore) to a wider or public audience. These aggregations shall not attach individual names of Users or their affiliated Organizations to event or organization-level data. Users agree that the Council may publicly state the name of a Users’ affiliated Organization name and logo or likeness in promotional materials. No project or Organization level data or performance information shall be shared in such communications, only that the Organization utilizes or has previously utilized the ReScore application. Projects and Users will be deemed inactive when no edits or actions have been taken for 12 months. Organizations and their Users’ inactive projects and project dashboard will be retained for five years (60 months) and may still be recovered at any point within 60 months of the Organization’s and its Users’ account becoming inactive. After five years of inactivity, records and all data uploaded or otherwise entered and stored on the ReScore platform by the Organization will be deleted and thenceforth unrecoverable by either the Organization or the Council and any of its affiliates including, but not limited to Amazon Web Services or any other third-party service provider.
Data Collection, Storage, and Use. This Contract does not xxxxx Xxxx Deere any rights to Customer data, information, or other intellectual property that Xxxx Deere may receive under this Contract (“Customer Content”) except for the rights of use described below and in Xxxx Deere’s Privacy and Data Statements, including the global Enterprise Privacy Statement, any applicable region- or country-specific Privacy Statements and the Xxxx Deere Data Services and Subscriptions Data Policy Statement (all available at xxx.xxxxxxxxx.xxx/xxxxx). Please refer to the Xxxx Deere Data Services and Subscriptions Data Policy Statement for country-specific information regarding how Xxxx Deere may use Customer Content. Dealers authorized by Xxxx Deere or Customer to access and use the Customer Content are “Authorized Dealers.” Xxxx Deere may provide Authorized Dealers information and data for the purpose of servicing Customer’s equipment, including machine diagnostics, remote servicing, and machine component software updates. Customer acknowledges that it has been notified of Xxxx Deere’s Privacy and Data Statements, including the global Enterprise Privacy Statement, the applicable region- or country-specific Privacy Statements and the Xxxx Deere Data Services and Subscriptions Data Policy Statement, and Customer hereby grants Xxxx Deere the right to use Customer Content as described in this Contract and as needed to provide Telematic Services under this Contract, including, for example, collecting and hosting Customer Content. This permission extends to third parties engaged by Xxxx Deere in connection with providing the Telematic Services. Without limiting the foregoing, Customer acknowledges and agrees that Xxxx Deere may disclose Customer Content to outside parties to (a) comply with any applicable law, regulation or compulsory legal request;

Related to Data Collection, Storage, and Use

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • 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.

  • Access to Work Locations Reasonable access to employee work locations shall be granted officers of the Association and their officially designated representatives for the purpose of processing grievances or contacting members of the Association concerning business within the scope of representation. Such officers or representatives shall not enter any work location without the consent of the City Manager. Access shall be restricted so as not to interfere with the normal operations of the department or with established safety or security requirements. Solicitation of membership and activities concerned with the internal management of the Association, such as collecting dues, holding membership meetings, campaigning for office, conducting elections and distributing literature, shall not be conducted during working hours.

  • Service Locations X.X. Xxxxxx maintains various operational/service centers and locations through the United States and foreign jurisdictions. The services provided under this Agreement may be provided from one or more such locations. X.X. Xxxxxx may change the operational/service centers and locations as it deems necessary or appropriate for its business concerns.

  • 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: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • 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.

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