Notifications Regarding Customer Data Sample Clauses

Notifications Regarding Customer Data. Okta has in place reasonable and appropriate security incident management policies and procedures, as specified in the Trust & Compliance Documentation and shall notify Customer without undue delay after becoming aware of the unlawful or accidental destruction, alteration or damage or loss, unauthorized disclosure of, or access to, Customer Data, including Personal Data, transmitted, stored or otherwise Processed by Okta or its Sub-processors of which Okta becomes aware (hereinafter, a “Customer Data Incident”). Okta shall make reasonable efforts to identify the cause of such Customer Data Incident, and take those steps as Okta deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident, to the extent that the remediation is within Okta’s reasonable control. The obligations set forth herein shall not apply to incidents that are caused by either Customer or Customer’s Users.
AutoNDA by SimpleDocs
Notifications Regarding Customer Data. Data Processor shall notify Data Controller without undue delay of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Data Controller's Personal Data or any accidental or unauthorised access or any other event affecting the integrity, availability or confidentiality of Data Controller's Personal Data as required to assist Data Controller to comply with its obligations to notify a Regulator of such an incident. Data Processor shall make reasonable efforts to identify the cause of such an incident and take those steps as Data Processor deems necessary and reasonable in order to remediate the cause, to the extent that any such remediation is within Data Processor’s reasonable control. The obligations herein shall not apply to incidents that are caused by Data Controller or its Users.
Notifications Regarding Customer Data. Roam has in place reasonable and appropriate security incident management policies and procedures, as specified in the Legal Documentation and shall notify Customer without undue delay, and in any event within 24 hours, after becoming aware of the unlawful or accidental destruction, alteration or damage or loss, unauthorised disclosure of, or access to, Customer Data, including Personal Data, transmitted, stored or otherwise processed by Roam or its Sub-processors of which Roam becomes aware (hereinafter, a “Customer Data Incident”), as required to assist the Customer in ensuring compliance with its obligations to notify the Supervisory Authority in the event of Personal Data breach. Roam shall make reasonable efforts to identify the cause of such Customer Data Incident, and take those steps as Roam deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident, to the extent that the remediation is within Roam’s reasonable control. The obligations set forth herein shall not apply to incidents that are caused by either Customer or Customer’s Users.
Notifications Regarding Customer Data. Okta has in place reasonable and appropriate security incident management policies and procedures, as specified in the Trust & Compliance Documentation and shall notify Customer without undue delay after becoming aware of the unlawful or accidental destruction, alteration or damage or loss, unauthorized disclosure of, or access to, Customer Data, including Personal Data, transmitted, stored or otherwise Processed by Okta or its Sub-processors of which Okta becomes aware (hereinafter, a “Customer Data Incident”), as required to assist the Customer in ensuring compliance with its obligations to notify the Supervisory Authority in the event of Personal Data breach. Okta shall make reasonable efforts to identify the cause of such Customer Data Incident, and take those steps as Okta deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident, to the extent that the remediation is within Okta’s reasonable control. The obligations set forth herein shall not apply to incidents that are caused by either Customer or Customer’s Users.
Notifications Regarding Customer Data. Olono has in place reasonable and appropriate security incident management policies and procedures, as specified in the Trust & Compliance Documentation and shall notify Customer without undue delay after becoming aware of the unlawful or accidental destruction, alteration or damage or loss, unauthorized disclosure of, or access to, Customer Data, including Personal Data, transmitted, stored or otherwise Processed by Olono or its Sub-processors of which Olono becomes aware (hereinafter,
Notifications Regarding Customer Data pganalyze has in place reasonable and appropriate security incident management policies and procedures, as specified in the Agreement and related Security Documentation and shall notify Customer without undue delay (but in no event later than any periods required by applicable Data Protection Laws and Regulations or described in the Agreement) after becoming aware of the unlawful or accidental destruction, alteration or damage or loss, unauthorized disclosure of, or access to, Customer Data, including Personal Data, transmitted, stored or otherwise Processed by pganalyze or its Sub-processors of which pganalyze becomes aware (hereinafter, a “Customer Data Incident”) and shall assist Customer in ensuring compliance with its obligations under applicable Data Protection Laws and Regulations. pganalyze shall make reasonable efforts to identify the cause of such Customer Data Incident, and take steps as pganalyze deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident, to the extent that the remediation is within pganalyze’s reasonable control.

Related to Notifications Regarding Customer Data

  • Customer Notification By executing this Agreement, the Advisor acknowledges that as required by the Advisers Act the Sub-Advisor has supplied to the Advisor and the Trust copies of the Sub-Advisor’s Form ADV with all exhibits and attachments (including the Sub-Advisor’s statement of financial condition) and will promptly supply to the Advisor copies of all amendments or restatements of such document. Otherwise, the Advisor’s rights under federal law allow termination of this contract without penalty within five business days after entering into this contract. U.S. law also requires the Sub-Advisor to obtain, verify, and record information that identifies each person or entity that opens an account. The Sub-Advisor will ask for the Trust’s legal name, principal place of business address, and Taxpayer Identification or other identification number, and may ask for other identifying information.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Cooperative Master Contract Sales Reporting. Contractor shall report total Cooperative Master Contract sales quarterly to Enterprise Services, as set forth below. Cooperative Master Contract Sales Reporting System. Contractor shall report quarterly Cooperative Master Contract sales in Enterprise Services’ Cooperative Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Cooperative Master Contract. If there are no Cooperative Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Cooperative Master Contract Sales Reporting. Quarterly Cooperative Master Contract Sales Reports must be submitted electronically by the following deadlines for all Cooperative Master Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.5 percent on the purchase price for all Cooperative Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Cooperative Master Contract sales invoiced (not including sales tax) x .015. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Cooperative Master Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Cooperative Master Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Cooperative Master Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Cooperative Master Contract sales, to submit a timely Cooperative Master Contract sales report, or to remit timely payment of the VMF to Enterprise Services, may be cause for Enterprise Services to suspend Contractor or terminate this Cooperative Master Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Cooperative Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Cooperative Master Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Cooperative Master Contract sales report. Such report shall include, at a minimum: the Goods/Services sold (including, as applicable, item number or other identifier), per unit quantities sold, items and volumes purchased by Purchaser, shipment/delivery locations by Purchaser, and Cooperative Master Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Cooperative Master Contract.

  • Customer Cooperation 3.2.1. Customer shall provide and make available all Customer personnel as may be further addressed in an applicable Order Form or that SAP reasonably requires in connection with performance of the Services. 3.2.2. Customer shall appoint a contact person with the authority to make decisions and to supply SAP with any necessary or relevant information expeditiously.

  • Customer Data 8.1 You, not bookinglab or JRNI, have sole responsibility for the entry, deletion, correction, accuracy, quality, integrity, legality, reliability, appropriateness, and right to use the Customer Data. bookinglab and JRNI is not responsible for any of the foregoing or for any destruction, damage, loss, or failure to store any Customer Data beyond its reasonable control or resulting from any failure in data transmission or operation of the Booking Service by you. 8.2 As of the MSA Start Date, JRNI is certified under ISO 27001 and shall maintain an information security program for the Services that complies with the ISO 27001 standards or such other standards as are substantially equivalent to ISO 27001. 8.3 If JRNI and/or bookinglab processes any Personal Data on your behalf when performing its obligations under this Agreement, the Parties acknowledge that you shall be the Data Controller and JRNI and/or bookinglab shall be a Data Processor and in any such case: (a) you shall ensure that you are entitled to transfer the relevant Customer Personal Data to JRNI and/or bookinglab so that they may lawfully use, process and transfer the Customer Personal Data in accordance with this Agreement on your behalf; (b) you shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable Data Protection Laws; (c) each Party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage; and (d) notwithstanding any other provision of this Agreement, but subject always to Appendix B(1) Data Protection and B(2) Data Processing Activities, nothing shall prevent JRNI or bookinglab from disclosing Customer Personal Data or Customer Data to their Group Companies, Affiliates and third party service providers as necessary to provide the Services in accordance with clause 3, and otherwise in order to comply with Applicable Law or at the request of a governmental, regulatory or supervisory authority. 8.4 From the MSA Start Date the Parties shall comply with Appendix B(1) Data Protection and Appendix B(2) Data Processing Activities 8.5 ensure that Customer Data and Personal Data deemed as a special category of Data under GDPR is not given to us in any form unless pre-agreed by us in writing 8.6 You are solely responsible and liable for any transfer of Customer Data made by you (or made by JRNI or bookinglab at your request) from the Booking Service to a third party and for ensuring that such transfer is in compliance with the Parties' obligations under the Data Protection Laws.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a PNG Customer is served by resold Verizon dial tone line Telecommunications Service or a Verizon Local Switching UNE, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service or UNE to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, PNG shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to PNG. PNG shall pay Verizon such charges in full regardless of whether or not PNG collects such charges from its Customer. 5.3 PNG shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event PNG exercises such option, PNG will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow PNG to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless PNG has entered into a written agreement with Verizon under which PNG will collect from PNG’s Customer and remit to Verizon the Voice Information Service provider’s charges, PNG shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to PNG. PNG shall pay Verizon such charges in full regardless of whether or not PNG collects such charges from its own Customer.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

  • Privacy of Customer Information The Seller’s Customer Information in the possession of the Administrative Agent or the Buyers, other than information independently obtained by the Administrative Agent or the Buyers and not derived in any manner from or using information obtained under or in connection with this Agreement, is and shall remain confidential and proprietary information of the Seller. Except in accordance with this Section 16.9, the Administrative Agent and the Buyers shall not use any Seller’s Customer Information for any purpose, including the marketing of products or services to, or the solicitation of business from, Customers, or disclose any Seller’s Customer Information to any Person, including any of the Administrative Agent’s or the Buyers’ employees, agents or contractors or any third party not affiliated with the Administrative Agent or a Buyer. The Administrative Agent and the Buyers may use or disclose Seller’s Customer Information only to the extent necessary (i) for examination and audit of the Administrative Agent’s or the Buyers’ respective activities, books and records by their regulatory authorities, (ii) to market or sell Purchased Mortgage Loans or to enforce or exercise their rights under any Repurchase Document, (iii) to carry out the Administrative Agent’s, the Buyers’ and the Custodian’s express rights and obligations under this Agreement and the other Repurchase Documents (including providing Seller’s Customer Information to Approved Investors), or (iv) in connection with an assignment or participation as authorized by Section 22 or in connection with any hedging transaction related to the Purchased Loans and for no other purpose; provided that the Administrative Agent and the Buyers may also use and disclose the Seller’s Customer Information as expressly permitted by the Seller in writing, to the extent that such express permission is in accordance with the Privacy Requirements. The Administrative Agent and the Buyers shall ensure that each Person to which the Administrative Agent or a Buyer intends to disclose Seller’s Customer Information, before any such disclosure of information, agrees to keep confidential any such Seller’s Customer Information and to use or disclose such Seller’s Customer Information only to the extent necessary to protect or exercise the Administrative Agents, the Buyers’ or the Custodian’s rights and privileges, or to carry out the Administrative Agent’s, the Buyers’ and the Custodian’s express obligations, under this Agreement and the other Repurchase Documents (including providing Seller’s Customer Information to Approved Investors). The Administrative Agent agrees to maintain an Information Security Program and to assess, manage and control risks relating to the security and confidentiality of Seller’s Customer Information pursuant to such program in the same manner as the Administrative Agent does in respect of its own customers’ information, and shall implement the standards relating to such risks in the manner set forth in the Interagency Guidelines Establishing Standards for Safeguarding Company Customer Information set forth in 12 C.F.R. Parts 30, 208, 211, 225, 263, 308, 364, 568 and 570. Without limiting the scope of the foregoing sentence, the Administrative Agent and the Buyers shall use at least the same physical and other security measures to protect all of the Seller’s Customer Information in their possession or control as each of them uses for its own customers’ confidential and proprietary information.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • CONTRACT INFORMATION 1. The State of Arkansas may not contract with another party: a. Upon default, to pay all sums to become due under a contract. b. To pay damages, legal expenses or other costs and expenses of any party. c. To conduct litigation in a place other than Pulaski County, Arkansas d. To agree to any provision of a contract; which violates the laws or constitution of the State of Arkansas. 2. A party wishing to contract with the State of Arkansas should: a. Remove any language from its contract which grants to it any remedies other than: i. The right to possession. ii. The right to accrued payments. iii. The right to expenses of de-installation. iv. The right to expenses of repair to return the equipment to normal working order, normal wear and tear excluded. v. The right to recover only amounts due at the time of repossession and any unamortized nonrecurring cost as allowed by Arkansas Law. b. Include in its contract that the laws of the State of Arkansas govern the contract. c. Acknowledge that contracts become effective when awarded by the State Procurement Official.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.

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