Device Data Sample Clauses

The Device Data clause defines how data generated, collected, or processed by a device is handled within the context of an agreement. It typically specifies what types of data are included, such as usage statistics, performance metrics, or user information, and outlines the rights and responsibilities of each party regarding access, storage, and use of this data. By clearly delineating data ownership and permitted uses, this clause helps prevent disputes over data control and ensures compliance with privacy or regulatory requirements.
POPULAR SAMPLE Copied 1 times
Device Data. We collect the following information about your Device used to access the Website: device platform, device version, device IP address and other device characteristics including your choice of settings such as Wi-Fi, Bluetooth, Global Positioning System (“GPS”). We use the data we collect about your Device to help authenticate you when you login, to help ensure you are able to use the Website as intended, to perform analysis on web traffic on an aggregated basis and or to route traffic more efficiently. If you choose to submit an online credit application on our website, with your permission and if enabled on your Device, we may collect your geolocation.
Device Data. We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.
Device Data. We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud
Device Data. We collect the following information about your computer or other device used to access the Website: device platform, device version, device IP address and other device characteristics including your choice of settings such as Wi-Fi, Bluetooth, Global Positioning System (“GPS”). We use the data we collect about your device to help authenticate you when you login, to help ensure you are able to use the Website as intended, to perform analysis on web traffic on an aggregated basis and or to route traffic more efficiently. If you choose to submit an online credit application on our website, with permission and if enabled on your device, we collect device information that allows us to know your geolocation. Geolocation technology is only tied to our web based online credit application experience. We do not ask you for, access, or track any location based information from your mobile device at any time while downloading or using our mobile applications or services.
Device Data. You shall be solely responsible for all data stored in your Registered Device and you shall delete all data from the Registered Device before its collection by True. True is not responsible for data you left on the Registered Device and will not transfer any such data or information between the Registered Device and the Like Mobile Device. Such data left on the Registered Device or transfer of any data or information off the Registered Device, if done by True at your request, will be done entirely at your own risk. In the event there is any inconvenience, delay, loss, misappropriation of or damage to any data or information, you agree not to hold True responsible or liable for any such damage to you.
Device Data. We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and f raud data f rom and about you to a database of similar device and f raud information in order to provide f raud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with f raudulent or abusive activity. Such information may be used by us and our third-party service providers to provide similar f raud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.
Device Data. Electrical drive controllers are distinguished by virtue of the fact that changes in a process variable (e.g. the speed) are caused by analog or digital signals. Additional parameters are needed to optimally adapt drive controllers and motors to the process. This is described in further detail with reference to the example of the static frequency inverter used to adjust three phase asynchronous machines. Besides needing the actual setpoint information, this device also needs information about the motor’s type point, the system’s minimum and maximum permissible speeds, the maximum speed change during acceleration and deceleration and information about commissioning and shutdown of the machine. An analysis of the above-mentioned parameters leads to the creation of two data classes, namely: the group of data to be transmitted cyclically (e.g. speed, position and torque) and the acyclic data transfer group (e.g. the minimum and maximum speed limits). This data classification is encountered not only in drive engineering, but also in the entire field of sensors/actuators. If we take a look at the two data classes from the point of view of quality, there are significant differences in relation to the time requirements and data width involved. The cyclic data generally involves low quantities of data ranging from 16 - 32 bits and has to be transferred with a cycle time of a few milliseconds. In contrast, the group of acyclic data involves clearly higher quantities of data, e.g. 50 * 16 bits of information units. Contrary to the cyclic data, such data changes seldomly. The time requirement, the cycle time, is therefore oriented to the cyclic data.
Device Data. All end user data collected by Ogury through its SDK during the term of this agreement remain the full property of ▇▇▇▇▇ during and after the termination of this agreement, in compliance with applicable privacy rules.
Device Data. ▇▇▇▇▇ acknowledges and agrees that the Goods purchased hereunder record and log usage data, including, without limitation: raw instrument data, analysis, results and timestamp, cultivar, sample ID, operator and other Buyer entered information (including, without limitation, Buyer’s notes) (collectively, “Device Data”). Data Device is associated with Buyer’s unique Product serial number. Device Data may be transmitted automatically to Seller via remote means (such as via Internet) and is stored on Seller’s servers and onboard on the Products via an onboard memory card. Seller will have access to Device Data stored on its servers. Seller will only use the Device Data to provide Buyer with services offered or performed by Seller, for its internal business purposes, to understand Product usage characteristics, to improve and provide support for its Products, and to offer additional products and services to Buyers related to its Product(s). Seller may use certain Device Data and aggregate it with information collected from other users or sources to attempt to improve the quality and value of Seller’s products and services. It will only share Device Data with third parties in aggregate, except that Seller may engage third parties to assist Seller in its internal business research, development and support activities, in which Seller may share Device Data with those third parties solely as necessary for them to assist Seller in performing services offered by Seller or requested by Buyer or to assist Seller in offering additional services and products to Buyers.

Related to Device Data

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Data Encryption 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism. 2.2. For all COUNTY data, if the CONTRACTOR stores sensitive personally identifiable or otherwise confidential information, this data shall be encrypted at rest. Examples are social security number, date of birth, driver’s license number, financial data, federal/state tax information, and hashed passwords. 2.3. For all COUNTY data, the CONTRACTOR’S encryption shall be consistent with validated cryptography standards as specified in National Institute of Standards and Technology Security Requirements as outlined at ▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.