NOTIFYING DATA SUBJECTS Sample Clauses

NOTIFYING DATA SUBJECTS. 7.1 If we collect personal data directly from data subjects, we will inform them about: (a) The purpose or purposes for which we intend to process that personal data. (b) The types of third parties, if any, with which we will share or to which we will disclose that personal data. (c) The means, if any, with which data subjects can limit our use and disclosure of their personal data. 7.2 If we receive personal data about a data subject from other sources, we will provide the data subject with this information as soon as possible thereafter.
AutoNDA by SimpleDocs

Related to NOTIFYING DATA SUBJECTS

  • Data Subjects The categories of Data Subjects who we may collect Personal Data about may include the following where they are a natural person: the Customer, the directors and ultimate beneficial owner(s) of the Customer, your customers, employees and contractors, payers and payees. You may share with Airwallex some or all of the following types of Personal Data regarding Data Subjects: • full name; • email address; • phone number and other contact information; • date of birth; • nationality; • public information about the data subject; • other relevant verification or due diligence documentation as required under these terms; and • any other data that is necessary or relevant to carry out the Agreed Purposes.

  • Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.

  • Purchaser Information Each Purchaser covenants that it will promptly notify the Company of any changes in the information set forth in the Registration Statement regarding such Purchaser or such Purchaser's "Plan of Distribution."

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • Data Subjects Rights 5.1. Where a data subject asserts claims for rectification, erasure or access to Us, and where We are able to correlate the data subject to You, based on the information provided by the data subject, We shall refer such data subject to You without undue delay. We shall support You, where possible, and based upon Your instruction insofar as agreed upon. We shall not be liable in cases where You fail to respond to the data subject’s request completely, correctly, or in a timely manner. Notwithstanding the foregoing, if Your employee submits a data subject request in relation to Online Training Cloud, You agree that we can fulfill such request without Your further approval. 5.2. We shall support You, insofar as is agreed upon by the parties, and where possible for Us, in fulfilling data subjects’ requests and claims, as detailed in chapter III of the GDPR and in fulfilling the obligations enumerated in Articles 33 to 36 GDPR.

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

  • Rights of Data Subjects 5.1 You control access to Your Services environment that holds Personal Information about Your end users, and Your end users should direct any requests related to their rights under Applicable Data Protection Law to You. 5.2 To the extent such access is not available to You, Oracle will provide assistance with requests from individuals to access, delete or erase, restrict, rectify, receive and transmit, block access to or object to processing related to Personal Information held in Your Services environment on Oracle systems, insofar as reasonably and technically possible. 5.3 If Oracle directly receives any requests or inquiries from Your end users that have identified You as the Controller, it will promptly pass on such requests to You without responding to the end user.

  • DISCLOSURE OF TBS ACCESS CODE TO THIRD PARTY (a) The Account Holder must exercise all care to ensure that the TBS Access Code is not disclosed to any person and shall take all steps to prevent forgery or fraud in connection with the use of his TBS Access Code and/or the operation of the TBS. If the TBS Access Code is disclosed to any person, the Account Holder must forthwith give the Bank written notice thereof, thereupon the Account Holder shall immediately cease to use the TBS Access Code. (b) Unless and until the Bank receives such written notice of disclosure, the Account Holder shall be fully liable and be bound by all transactions effected by the use of such TBS, with or without his consent or knowledge.

  • Identifying Information Issuer and Broker acknowledge that a portion of the identifying information set forth on Exhibit A is being requested by NCPS in connection with the USA Patriot Act, Pub.L.107-56 (the “Act”). To help the government fight the funding of terrorism and money laundering activities, Federal law requires all financial institutions to obtain, verify, and record information that identifies each person who opens an account. For a non-individual person such as a business entity, a charity, a Trust, or other legal entity, we ask for documentation to verify its formation and existence as a legal entity. We may also ask to see financial statements, licenses, identification and authorization documents from individuals claiming authority to represent the entity or other relevant documentation.

  • IDENTIFYING INFORMATION AND PRIVACY NOTIFICATION (a) FEDERAL EMPLOYER IDENTIFICATION NUMBER and/or FEDERAL SOCIAL SECURITY NUMBER. As a condition to NYSERDA’s obligation to pay any invoices submitted by Contractor pursuant to this Agreement, Contractor shall provide to NYSERDA its Federal employer identification number or Federal social security number, or both such numbers when the Contractor has both such numbers. Where the Contractor does not have such number or numbers, the Contractor must give the reason or reasons why the payee does not have such number or numbers.

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