Processing of Usage Data Sample Clauses

Processing of Usage Data. 2.1. The parties anticipate that Service Provider will need to process End Customer Personal Information such as, but not limited to, MAC address and Serial Number devices used (“Usage Data”) to provide the Solution. 2.2. Service Provider shall Process Usage Data in order to (i) fulfill its obligations under the Agreement and this Addendum, and (ii) develop and maintain Service Provider’s products across its customer base. 2.3. The parties agree and acknowledge that they independently control the purpose and means of processing Usage Data, and, as such, each party is solely responsible for how it protects and safeguards Usage Data. 2.4. Each party will, to the extent required by applicable law, be responsible for notifying End Users about whom it receives Usage Data of its privacy practices and obtaining any required consents. 2.5. Service Provider shall retain, use, disclose, and otherwise Process Usage Data solely to fulfill its obligations under the Agreement, this Addendum, or as otherwise expressly instructed by End Customer. 2.6. Insofar as the Agreement involves the transfer of Usage Data from the European Economic Area (“EEA”) to a jurisdiction outside of the EEA where the transfer would be prohibited by Data Protection Laws in the absence of Standard Contractual Clauses or another adequate transfer mechanism as approved by the European Commission, the Parties agree to comply with the Standard Contractual Clauses – Module 1, incorporated by reference in Exhibit 1. 2.7. Insofar as the Agreement involves the transfer of Usage Data from the United Kingdom to a jurisdiction outside of the United Kingdom where the transfer would be prohibited by Data Protection Laws in the absence of the UK Standard Contractual Clauses or another adequate transfer mechanism as approved by the UK Information Commissioners Office, the Parties agree to comply with the UK Standard Contractual Clauses (Controller to Controller), incorporated by reference in Exhibit 2. 2.8. Insofar as the Agreement involves the transfer of Usage Data from any other jurisdiction where applicable Data Protection Laws requires that additional steps, or safeguards, be imposed before the data can be transferred to a second jurisdiction, Service Provider agrees to cooperate with End Customer to take appropriate steps to comply with applicable Data Protection Laws.
AutoNDA by SimpleDocs
Processing of Usage Data. Sage may collect and use data resulting from Customer’s installation and use of the Software for Sage’s legitimate business purposes (“Usage Data”). Usage Data includes information about Customer’s hardware, when Customer installs the Program, and how Customer uses the Software (i.e., which functionality is selected, which in-product help and services that Customer utilizes, etc.). Usage Data does not include any data that Customer inputs into the Software. Further, Customer acknowledges that Sage may collect, use, and disclose Usage Data as described in the Sage Privacy Notice posted at xxxxx://xxx.xxxx.xxx/en-us/legal/privacy-and-cookies/ (if you are contracting with Sage Software, Inc.) or xxxxx://xxx.xxxx.xxx/en- ca/legal/privacy-and-cookies/ (if you are contracting with Sage Software Canada Ltd.), or such other URL as Sage may notify Customer of, and as may be described in the user interface associated with the Software’s applicable features.
Processing of Usage Data 

Related to Processing of Usage Data

  • Processing of Customer Personal Data 3.1 UKG will: 3.1.1 comply with all applicable Data Protection Laws in the Processing of Customer Personal Data; and 3.1.2 not Process Customer Personal Data other than for the purpose, and in accordance with, the relevant Customer’s instructions as documented in the Agreement and this DPA, unless Processing is required by the Data Protection Laws to which the relevant UKG Processor is subject, in which case UKG to the extent permitted by the Data Protection Laws, will inform Customer of that legal requirement before the Processing of that Customer Personal Data. 3.2 Customer hereby: 3.2.1 instructs UKG (and authorizes UKG to instruct each Subprocessor) to: (a) Process Customer Personal Data; and (b) in particular, transfer Customer Personal Data to any country or territory subject to the provisions of this DPA, in each case as reasonably necessary for the provision of the Services and consistent with the Agreement. 3.2.2 warrants and represents that it is and will at all relevant times remain duly and effectively authorized to give the instructions set out in Section 3.2.1 on behalf of each relevant Customer Affiliate; and 3.2.3 warrants and represents that it has all necessary rights in relation to the Customer Personal Data and/or has collected all necessary consents from Data Subjects to Process Customer Personal Data to the extent required by Applicable Law. 3.3 Schedule 1 to this DPA sets out certain information regarding UKG’s Processing of Customer Personal Data as required by Article 28(3) of the GDPR (and equivalent requirements of other Data Protection Laws).

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

  • Usage Data 7.1. The parties shall supply data on usage of the Licensed Work that is available to them during the term of this Licence. Notwithstanding the foregoing, the parties shall neither assemble nor provide data from which an individual user could be identified.

  • Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Transmission and Routing of Telephone Exchange Service Traffic 50.4.1 The Appendix Reciprocal Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the Appendix ITR, which is/are attached hereto and incorporated herein by reference.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Usage for Voice Mail Message Service Rated Incollects (originated in BellSouth and from other companies) can also be on Optional Daily Usage File. Rated Incollects will be intermingled with BellSouth recorded rated and unrated usage. Rated Incollects will not be packed separately.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a ECI Customer is served by resold Verizon dial tone line Telecommunications Service or a Verizon Local Switching UNE, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service or UNE to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its Customer. 5.3 ECI shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event ECI exercises such option, ECI will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow ECI to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless ECI has entered into a written agreement with Verizon under which ECI will collect from ECI’s Customer and remit to Verizon the Voice Information Service provider’s charges, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its own Customer.

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