Data Subject and Regulator Requests Sample Clauses

The 'Data Subject and Regulator Requests' clause outlines the obligations of parties to respond to inquiries or requests from individuals whose personal data is processed (data subjects) and from regulatory authorities overseeing data protection. Typically, this clause requires the parties to cooperate in providing access to, correcting, or deleting personal data upon request, and to promptly notify each other of any regulatory inquiries or investigations. Its core function is to ensure compliance with data protection laws, such as GDPR, by facilitating timely and coordinated responses to legal rights and regulatory oversight, thereby reducing legal risk and ensuring transparency.
Data Subject and Regulator Requests. Customer shall be responsible for communications and leading any efforts to comply with all requests made by Data Subjects under Data Protection Laws and all communications from Regulators that relate to the Personal Data, in accordance with Data Protection Laws. To the extent such requests or communications require Webflow’s assistance, Customer shall immediately notify Webflow in writing of the Data Subject’s or Regulator’s request.
View SourceView Similar (27)
Data Subject and Regulator Requests. In light of Nectar HR’s capacity as the processor and service provider hereunder, if Nectar HR receives a request from a data subject made under Data Protection Laws (including, without limitation, GDPR or CCPA/CPRA) and determines that Nectar HR is not the controller or covered business and that the controller or covered business is the Client, Nectar HR will refer the data subject to Client as the party to whom the request should be made. Nectar HR further agrees to provide reasonable assistance to Client to address any communications and advice or orders from any Regulator relating to the Personal Data.
View SourceView Similar (9)
Data Subject and Regulator Requests. Webflow will promptly notify Customer in writing of any complaints, questions or requests received from Data Subjects or Regulators regarding the Personal Data. Taking into account the nature of the Processing and to the extent reasonably possible, Webflow will assist Customer in fulfilling Customer’s obligations in relation to Data Subject requests under applicable Data Protection Laws.
View SourceView Similar (8)
Data Subject and Regulator Requests. Olark will promptly notify Customer in writing of any complaints, questions or requests received from Data Subjects or Regulators regarding the Personal Data. Taking into account the nature of the Processing and to the extent reasonably possible, Olark will assist Customer in fulfilling Customerʼs obligations in relation to Articles 13 and 14 of the GDPR, and Data Subject requests, under applicable Data Protection Laws.
View SourceView Similar (2)
Data Subject and Regulator Requests. Honeycomb will promptly notify Customer in writing of any complaints, questions or requests received from Data Subjects or Regulators regarding the Personal Data. Taking into account the nature of the Processing and to the extent reasonably possible, Honeycomb will assist Customer in fulfilling Customer’s obligations in relation to Data Subject requests under applicable Data Protection Laws.
View Source
Data Subject and Regulator Requests. 2.3.1. Data Processor shall immediately inform Data Controller in writing of any requests with respect to Personal Data received from Data Subjects. Data Controller shall be solely responsible for responding substantively to requests from Data Subjects regarding their Personal Data. 2.3.2. To the extent that Data Controller is not able to independently address a request from a Data Subject, then upon Data Controller’s written request, Data Processor shall provide reasonable assistance to respond to requests from Data Subjects, subject to an additional fee. Data Processor will respond to such requests only in accordance with Data Controller’s instructions. 2.3.3. Notwithstanding the foregoing, Data Processor shall have no obligation to reidentify or otherwise link information that is not maintained in a manner that would not be considered Personal Information. Further, notwithstanding anything in the contrary herein, Data Processor shall have no obligation to delete or return Personal Information where it is necessary for Data Processor to maintain the Personal Information in order to (a) complete the transaction for which the Personal Information was collected or otherwise perform a contract between Data Controller and a consumer; (b) detect security incidents, protect against malicious, deceptive, fraudulent, or illegal activity; or prosecute those responsible for that activity; (c) debug to identify and repair errors that impair existing intended functionality; (d) exercise a right under the law; (e) comply with applicable law or a legal obligation; and (f) otherwise use the Personal Information in a lawful manner that is compatible with the context in which the information was provided. 2.3.4. If Data Processor, either directly or indirectly, receives any communication from Regulators relating to Personal Data, Data Processor shall provide a copy to Data Controller within a commercially reasonable time, but no later than within five (5) business days. Data Processor shall not respond to any communication from a Regulator relating to Personal Data without the explicit written consent of Data Controller, unless required by law. Data Processor shall work in full cooperation with Data Controller on any permitted response(s) to Regulators without unreasonable delay. 2.3.5. If Data Processor is required by law to disclose Personal Data to law enforcement or government authorities, Data Processor shall notify Data Controller in writing and liaise with Data Con...
View Source
Data Subject and Regulator Requests. SimpleMDM will promptly notify Customer in writing of any complaints, questions or requests received from Data Subjects or Regulators regarding the Personal Data. Taking into account the nature of the Processing and to the extent reasonably possible, SimpleMDM will assist Customer in fulfilling Customer’s obligations in relation to Data Subject requests under applicable Data Protection Laws.
View Source

Related to Data Subject and Regulator Requests

  • Clinical Data and Regulatory Compliance The preclinical tests and clinical trials, and other studies (collectively, “studies”) that are described in, or the results of which are referred to in, the Registration Statement or the Prospectus were and, if still pending, are being conducted in all material respects in accordance with the protocols, procedures and controls designed and approved for such studies and with standard medical and scientific research procedures; each description of the results of such studies is accurate and complete in all material respects and fairly presents the data derived from such studies, and the Company and its subsidiaries have no knowledge of any other studies the results of which are inconsistent with, or otherwise call into question, the results described or referred to in the Registration Statement or the Prospectus; the Company and its subsidiaries have made all such filings and obtained all such approvals as may be required by the Food and Drug Administration of the U.S. Department of Health and Human Services or any committee thereof or from any other U.S. or foreign government or drug or medical device regulatory agency, or health care facility Institutional Review Board (collectively, the “Regulatory Agencies”); neither the Company nor any of its subsidiaries has received any notice of, or correspondence from, any Regulatory Agency requiring the termination, suspension or modification of any clinical trials that are described or referred to in the Registration Statement or the Prospectus; and the Company and its subsidiaries have each operated and currently are in compliance in all material respects with all applicable rules, regulations and policies of the Regulatory Agencies.

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

  • Governmental and Regulatory Approvals Other than the filing provided for under Section 1.3 and filings pursuant to the HSR Act (which are addressed in Section 6.1(c)), all consents, approvals and actions of, filings with and notices to any Governmental Entity required of AHP, Monsanto or any of their Subsidiaries to consummate the Merger, the Share Issuance and the other transactions contemplated hereby, the failure of which to be obtained or taken would reasonably be expected to have a Material Adverse Effect on Newco and its Subsidiaries (including the Surviving Corporation and its Subsidiaries), taken together after giving effect to the Merger, shall have been obtained; provided however, that the provisions of this Section 6.1(d) shall not be available to any party whose failure to fulfill its obligations pursuant to Section 5.4 shall have been the cause of, or shall have resulted in, the failure to obtain such consent or approval.

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (▇▇▇▇▇://▇▇▇▇▇.▇▇▇.▇▇▇▇▇.▇▇.▇▇/tpasscmblsearch/index.jsp) or by contacting

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.