CATEGORIES OF PROCESSED DATA Sample Clauses

CATEGORIES OF PROCESSED DATA. The Controller processes the following categories of your data: - first and last name; - function/job position; - phone number;
AutoNDA by SimpleDocs
CATEGORIES OF PROCESSED DATA. Users email • Users first name • Users last name (Optional) • Users phone number (Optional) • Users photo (Optional) • Users group membership • Video, sound, images and other personal data pertaining to identifiable persons in Customer´s media files • IP addresses
CATEGORIES OF PROCESSED DATA. Users email
CATEGORIES OF PROCESSED DATA. Web browser User-Agent string • User email • User id (UUID) • User first name • User last name (Optional) • User phone number (Optional) • User photo (Optional) • User group membershipUser type in iconik (Power, Standard, Browse, or Admin user type) • Video, sound, images and other personal data pertaining to identifiable persons in Customer´s media files • IP addresses
CATEGORIES OF PROCESSED DATA. Web browser User-Agent string ● User email ● User id (UUID) ● User first name ● User last name (Optional) ● User phone number (Optional) ● User photo (Optional) ● User group membershipUser type in iconik (Power, Standard, Browse, or Admin user type) ● Video, sound, images and other personal data pertaining to identifiable persons in Customer´s media files or metadata ● IP addresses

Related to CATEGORIES OF PROCESSED DATA

  • Categories of Data Data relating to individuals provided to Google via the Services, by (or at the direction of) Customer or End Users. Data subjects include the individuals about whom data is provided to Google via the Services by (or at the direction of) Customer or End Users.

  • Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up

  • Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").

  • Particular Methods of Procurement of Goods Works and Services (other than Consultants’ Services)

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

  • Categories of Personal Data Data Controller may submit Personal Data to the Subscription Service, the extent of which is solely determined by Data Controller, and may include the following categories: • communication data (e.g. telephone, email); • business and personal contact details; and • other Personal Data submitted to the Subscription Service.

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Other Types of Traffic 8.1 Notwithstanding any other provision of this Agreement or any Tariff: (a) the Parties’ rights and obligations with respect to any intercarrier compensation that may be due in connection with their exchange of Internet Traffic shall be governed by the terms of the FCC Internet Order and other applicable FCC orders and FCC Regulations; and, (b) a Party shall not be obligated to pay any intercarrier compensation for Internet Traffic that is in excess of the intercarrier compensation for Internet Traffic that such Party is required to pay under the FCC Internet Order and other applicable FCC orders and FCC Regulations. 8.2 Subject to Section 8.1 of this Attachment, interstate and intrastate Exchange Access, Information Access, exchange services for Exchange Access or Information Access, and Toll Traffic, shall be governed by the applicable provisions of this Agreement and applicable Tariffs. 8.3 For any traffic originating with a third party carrier and delivered by CBB to Verizon, CBB shall pay Verizon the same amount that such third party carrier would have been obligated to pay Verizon for termination of that traffic at the location the traffic is delivered to Verizon by CBB. 8.4 Any traffic not specifically addressed in this Agreement shall be treated as required by the applicable Tariff of the Party transporting and/or terminating the traffic. 8.5 The Parties may also exchange Internet Traffic at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA established hereunder for the exchange of Reciprocal Compensation Traffic. Any intercarrier compensation that may be due in connection with the Parties’ exchange of Internet Traffic shall be applied at such technically feasible Point of Interconnection on Verizon’s network in a LATA in accordance with the FCC Internet Order.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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

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