Types of Personal Data and Categories of Data Subjects Sample Clauses

Types of Personal Data and Categories of Data Subjects for this licence are described in Appendix B.
AutoNDA by SimpleDocs
Types of Personal Data and Categories of Data Subjects. The types of Personal Data and categories of Data Subjects are set forth in the attached
Types of Personal Data and Categories of Data Subjects. 6.3.1 The types of Customer Personal Data Processed by BT or its Sub-Processors or the Customer will be: 6.3.2 The Customer Personal Data will concern the following categories of Data Subjects:
Types of Personal Data and Categories of Data Subjects. The types of Personal Data and categories of Data Subjects are set forth in Appendix 1 to the Standard Contractual Clauses, which is hereby incorporated into this Addendum by reference and shall be binding as if it were set out in this Addendum in its entirety. Appendices 1 and 2 to this Addendum shall be deemed automatically incorporated into Appendices 1 and 2 of the Standard Contractual Clauses. For the avoidance of doubt, the parties agree that this Section is not intended to amend or modify the Standard Contractual Clauses, but to provide clarity regarding Yeti’s practices for complying with the Standard Contractual Clauses. In the event of any conflict between this Section and the Standard Contractual Clauses, the Standard Contractual Clauses shall control. Rights of Data Subjects Yeti shall, to the extent permitted by Applicable Data Protection Law, promptly notify Customer upon receipt of a request by a Data Subject to exercise the Data Subject’s right of: access, rectification, restriction of Processing, erasure, data portability, restriction or cessation of Processing, withdrawal of consent to Processing, and/or objection to being subject to Processing that constitutes automated decision-making (such requests individually and collectively “Data Subject Request(s)”). If Yeti receives a Data Subject Request in relation to Customer’s data, Yeti will advise the Data Subject to submit their request to Customer and Customer will be responsible for responding to such request, including, where necessary, by using the functionality of the Service. Yeti shall, at the request of the Customer, and taking into account the nature of the Processing applicable to any Data Subject Request, apply appropriate technical and organizational measures to assist Customer in complying with Customer’s obligation to respond to such Data Subject Request and/or in demonstrating such compliance, where possible, provided that (i) Customer is itself unable to respond without Yeti’s assistance and (ii) Yeti is able to do so in accordance with all applicable laws, rules, and regulations. Customer shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by Yeti. Actions and Access Requests Yeti shall, taking into account the nature of the Processing and the information available to Yeti, provide Customer with reasonable cooperation and assistance where necessary for Customer to comply with its obligations under Applicable Data...
Types of Personal Data and Categories of Data Subjects. 3.1. The Processor will process the following types of personal data: [List types of data, e.g., names, email addresses, phone numbers, financial data]. 3.2. The categories of data subjects include: [List categories of data subjects, e.g., customers, employees, clients].
Types of Personal Data and Categories of Data Subjects. The types of Personal Data and categories of Personal Data, and the categories of Data Subjects, shall be those determined by the Customer having the Customer Personal Data. The obligations and rights of the Customer in relation to the Processing of Personal Data shall be as set out in this Terms of Use and the Principal Agreement and in the Data Protection Laws.
Types of Personal Data and Categories of Data Subjects. The Data Processor will process the following types of personal data relating to the following categories of data subjects: Data used to create a User Profile (for the internal Users within the Data Controllers organization) in the Scanmarket system is divided into to mandatory and non-mandatory data. Mandatory data is necessary for the use of Scanmarkets system. and consists of the following data with (*) indicating personal data under the definition of this agreement: Company Name / Department *Person (Name) *Email address Country Time Zone Language Username Non-mandatory fields are: Title Direct telephone no. Mobile no. Fax no. Last Login and Login history including IP address Browser info and Browser version Notes Data Controller and Data Controllers Users can build a Contact Archive/Database consisting of Companies, Departments and Company Contacts (e.g. suppliers) which is used within Scanmarket’s different modules. In the contact archive, contact companies are created. To each company one or more contact persons are added. A contact profile may contain the following personal data (Items listed with a * is mandatory and will be present on all profiles): *Contact name Title Direct telephone no. Mobile no. *Email Last Login (Date only) Username Country Time zone Language Depending on the level of Supply Base Management (SBM) access assigned to the Data Controller and the User, the sections, Email Communication, Notes and Reminders may also be shown. Data Controller may choose to have a questionnaire implemented in their SBM solution where contacts can respond with relevant business data when signing up. These questionnaires are set up by Data Controller and may contain personal data if they request it from the contacts. The Data Processor may process sensitive information to the extent the Data Controller processes such by using the Services.
AutoNDA by SimpleDocs
Types of Personal Data and Categories of Data Subjects. This DPA applies to the Processing of Personal Data relating to individuals about whom data is submitted to or through the Cybereason Platform by Customer or by any Customer end user, including IP addresses, machine names, user names and contact information of Customers’ employees using the Services, the extent of which is determined by Customer (or any Customer end user) in its sole discretion.
Types of Personal Data and Categories of Data Subjects. The Types of Personal Data andCategories of Data Subjects are described in Annex I.

Related to Types of Personal Data and Categories of Data Subjects

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

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

  • Types of Personal Data Contact Information, the extent of which is determined and controlled by the Customer in its sole discretion, and other Personal Data such as navigational data (including website usage information), email data, system usage data, application integration data, and other electronic data submitted, stored, sent, or received by end users via the Subscription Service.

  • Type of Personal Data Data Subjects may provide the following Shared Personal Data in connection with the purchase of a domain name from a Registrar:

  • Processing of Personal Data 1.1. With regard to the Processing of Personal Data, You are the controller and determine the purposes and means of Processing of Personal Data You provide to Us (“Controller”) and You appoint Us as a processor (“Processor”) to process such Personal Data (hereinafter, “Data”) on Your behalf (hereinafter, “Processing”). 1.2. The details of the type and purpose of Processing are defined in the Exhibits attached hereto. Except where the DPA stipulates obligations beyond the Term of the Agreement, the duration of this DPA shall be the same as the Agreement Term. 1.3. You shall be solely responsible for compliance with Your obligations under the applicable Data Protection Laws, including, but not limited to, the lawful disclosure and transfer of Personal Data to Us by upload of source data into the Cloud Service or otherwise. 1.4. Processing shall include all activities detailed in this Agreement and the instructions issued by You. You may, in writing, modify, amend, or replace such instructions by issuing such further instructions to the point of contact designated by Us. Instructions not foreseen in or covered by the Agreement shall be treated as requests for changes. You shall, without undue delay, confirm in writing any instruction issued orally. Where We believe that an instruction would be in breach of applicable law, We shall notify You of such belief without undue delay. We shall be entitled to suspend performance on such instruction until You confirm or modify such instruction. 1.5. We shall ensure that all personnel involved in Processing of Customer Data and other such persons as may be involved in Processing shall only do so within the scope of the instructions. We shall ensure that any person Processing Customer Data is subject to confidentiality obligations similar to the confidentiality terms of the Agreement. All such confidentiality obligations shall survive the termination or expiration of such Processing.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • 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 PNG to Verizon, PNG 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 PNG. 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.

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