Data Collection/Sharing Sample Clauses
The Data Collection/Sharing clause defines the rules and limitations regarding how parties gather, use, and exchange data within the scope of their agreement. It typically outlines what types of data can be collected, the purposes for which data may be used, and the conditions under which data may be shared with third parties, such as requiring consent or compliance with privacy laws. This clause is essential for protecting sensitive information, ensuring legal compliance, and setting clear expectations about data privacy and security between the parties.
Data Collection/Sharing a. The University will evaluate various aspects of the Pilot Program using data shared by the Licensee with the City of Gainesville through monthly reporting and Mobility Data Specification (MDS) Provider Application Program Interface (API) in accordance with the City Micromobility Services Permit.
b. Licensee understands and agrees that the University may rely upon a third-party researcher or consultant to evaluate various aspects of the Pilot Program. Upon request, Licensee will directly share all data that is relevant to evaluating or enforcing the terms set forth in this Agreement with the University and any such third-party researcher.
c. Licensee agrees that it will provide any and all user or customer data in Licensee’s possession that is directly or indirectly related to active investigations into third party criminal behavior and/or claims of civil liability against the University by persons using or riding a Micromobility Device. Notwithstanding any other provision to the contrary, this section (c) shall be deemed to include personally identifiable customer data.
Data Collection/Sharing a. The City and Licensee each understand and agree that the City is not requesting or requiring the collection or creation of any new data with this license, unless expressly provided and stated herein. Any new data collected, created or stored by Licensee shall be considered Licensee’s private data, and not government data, unless a provision of this license agreement expressly requires its collection or creation, and/or the City requests and receives such data from Licensee.
b. The City and Licensee each understand and agree that the City is not requesting or requiring sharing of user data deemed to be Personally Identifiable Information as defined by the US Department of Commerce, with the exception of data as specified herein.
c. Licensee agrees to disseminate two customer surveys and two lower income program participant surveys annually on behalf of the City. The surveys will be used to aid the City in evaluating whether and how Licensee’s Operation supports City goals for transportation. The surveys shall not include, and Licensee shall not collect, any personally identifiable data related to or in furtherance this provision.
d. Licensee shall provide an API that meets the requirements of the Mobility Data Specification (“MDS”) as published online at ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/openmobilityfoundation/mobility-data-specification. Licensee must notify the City at least 90 days in advance when updating to newer MDS versions or deprecating past versions. Licensee may not change anything related to the API without notifying at least 30 days in advance of change. The City shall only require compliance with the “Provider” component of MDS and shall not require compliance with the other components of MDS without explicit agreement from Licensee. Licensee will maintain operability with the City’s version of MDS.
e. Licensee shall provide an API that meets the requirements of the General Bikeshare Feed Specification (▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/NABSA/gbfs). Licensee may not change the API URL without notifying at least 30 days in advance of change. Licensee is required to make the API endpoint available for public consumption.
f. The Licensee must provide an API to any third party who jointly requests it with the City, within 30 days (unless an extension is granted by the City), and who operates or serves users within the region, which allows for fleet vehicle location, as well as user access and payment, to facilitate the City’s Mobility as a Service program.
g. Licensee shall...
Data Collection/Sharing. Use of certain Software may include our access to your end users’ personal information
(a) solely as required for our provision of such Software in accordance the applicable Documentation and (b) in accordance with our Privacy Policy (available at ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/company/policies/privacy-notice). You consent and agree to such access and further agree that you are solely responsible for notifying your end users of the same and ensuring your privacy policy contemplates the sharing of such end-user information with third parties. Use of Nginx Software and website are subject to the Nginx Privacy Policy (available at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/privacy-policy/ ).
Data Collection/Sharing. There are numerous databases available to EPRI that would improve the understanding and quantification of FPRA. NRC-RES and EPRI will collaborate on data collection and analysis projects as appropriate. All EPRI data and materials subject to commercial or other use restrictions will be submitted to the NRC under a general affidavit addressing all documents, data and materials to be shared with the NRC pursuant to this Addendum and requesting that such documents, data and materials be withheld from disclosure to the public pursuant to 10 C.F.R. §2.390 as provided in the MOU. Should the NRC reject EPRl's request to withhold the EPRI data or materials from public disclosure, the project will not proceed.