Data Collection, Data Usage and Data Ownership Sample Clauses

Data Collection, Data Usage and Data Ownership. 1. Additional Definitions. The following terms shall have the following meaning: • “IO Details” are details recorded on the IO including Ad pricing information, Ad description, Ad placement information, and Ad targeting information. • “Performance Data” is data regarding a Campaign collected either via Tags or directly by Agency (or Advertiser) during delivery of the Campaign (e.g., number of impressions, interactions, and header information), including Tag Data (defined below) and other data that identifies or allows identification of the Advertiser, the Campaign, Media Company / Site context, but excluding Media Company Data and IO Details.
AutoNDA by SimpleDocs

Related to Data Collection, Data Usage and Data Ownership

  • Data Collection The grant recipient will be required to provide performance data reports on a schedule delineated within Section A of this contract, Specific Terms and Conditions.

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

  • Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.

  • Data Collection and Usage The Company and the Employer collect, process and use certain personal information about the Participant, including, but not limited to, the Participant’s name, home address and telephone number, email address, date of birth, social insurance, passport or other identification number, salary, nationality, job title, any Shares or directorships held in the Company, details of all restricted stock units or any other entitlement to Shares or equivalent benefits awarded, canceled, exercised, vested, unvested or outstanding in the Participant’s favor (“Data”), for the legitimate purpose of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is the Participant’s consent.

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

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

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

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.

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

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

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