PERSONAL DATA INCIDENTS Sample Clauses

PERSONAL DATA INCIDENTS. 4.1. Entrust Datacard shall notify Customer without undue delay after becoming aware of a Personal Data Incident. Entrust Datacard shall identify the cause of such Personal Data Incident and take those steps reasonably necessary in order to remediate the cause of such a Personal Data Incident.
AutoNDA by SimpleDocs
PERSONAL DATA INCIDENTS. 4.1. In the event of a personal data incident (as defined in the Applicable Law), Infobric shall notify the Customer in writing as soon as possible after Infobric is made aware the incident. The notification shall contain information about the nature of the incident, the categories and number of data subjects and personal data items affected, the likely consequences of the incident, and a description of the measures Infobric has taken (if any) to limit any negative effects of the incident. If this is not possible, it is not necessary to notify all of the information at the same time, as Infobric will provide the Customer with the information as soon as it becomes available to Infobric.
PERSONAL DATA INCIDENTS. 5.1. Partner shall notify Entrust without undue delay (and in any event within forty-eight (48) hours) after becoming aware of a Personal Data Incident. Partner shall identify: (i) the cause of the Personal Data Incident, (ii) the nature of the Personal Data including where possible, the categories and approximate number of Data Subject concerned and the categories and approximate number of Personal Data records concerned, (iii) the likely consequences of the Personal Data Incident, (iv) the measures taken or proposed to be taken by Partner to address the Personal Data Incident, including, where appropriate, measures to mitigate its possible adverse effects and (v) the details of a contact point where more information concerning the Personal Data Incident can be obtained. Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
PERSONAL DATA INCIDENTS. Provider shall inform the Subscriber in writing of any personal data incident without undue delay and no later than twenty-four (24) hours after Subscriber's discovery of the personal data incident. This information shall to the extent possible contain all necessary information required in order for the Subscribe to be able to fulfil its reporting/information obligation towards the Supervisory Authority and/or the Data Subject.
PERSONAL DATA INCIDENTS. A. In accordance with applicable Data Protection Laws and Regulations, each party shall notify the other party without undue delay upon becoming aware of an accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data maintained and Processed in the Orion system (a “Personal Data Incident”). Each party shall make reasonable efforts to identify the cause of a Personal Data Incident and take those steps as deemed necessary and reasonable in order to remediate the cause of such Personal Data Incident, to the extent that the remediation is within such party’s reasonable control. Orion’s obligations set forth herein shall not apply to Personal Data Incidents that are caused directly or indirectly by Customer or a Processor engaged by Customer.
PERSONAL DATA INCIDENTS. 4.1. Processor shall notify Controller without undue delay (and in any event within forty-eight
PERSONAL DATA INCIDENTS. 4.1. Vendor shall notify Entrust without undue delay (and in any event within forty-eight (48) hours) after becoming aware of a Personal Data Incident. Vendor shall identify the cause of such Personal Data Incident and take those steps necessary in order to remediate the cause of such a Personal Data Incident.
AutoNDA by SimpleDocs
PERSONAL DATA INCIDENTS. 4.1. Banzai shall notify Customer without undue delay (and in any event within forty-eight (48) hours) after becoming aware of a Personal Data Incident. Banzai shall identify the cause of such Personal Data Incident and take those steps necessary in order to remediate the cause of such a Personal Data Incident.
PERSONAL DATA INCIDENTS. 10.1 The Personal Data Processor shall provide and implement technical and practical solutions to investigate suspicions that an unauthorised person has processed or gained unauthorised access to the Personal Data. In the event of unauthorised Processing, unauthorised access, destruction or modification of Personal Data, as well as attempts at these, the Personal Data Processor shall inform the Personal Data Controller of the incident in writing immediately.

Related to PERSONAL DATA INCIDENTS

  • Personal Data Breach 7.1 Processor shall notify Company without undue delay upon Processor becoming aware of a Personal Data Breach affecting Company Personal Data, providing Company with sufficient information to allow the Company to meet any obligations to report or inform Data Subjects of the Personal Data Breach under the Data Protection Laws.

  • Personal Data Registry Operator shall (i) notify each ICANN-­‐accredited registrar that is a party to the registry-­‐registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.

  • Personal Data Breaches 5.7.1 The Data Processor shall give immediate notice to the Data Controller if a breach occurs, that can lead to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or access to, personal data transmitted, stored or otherwise processed re the Personal Data processed on behalf of the Data Controller (a “Personal Data Breach”).

  • Your Personal Data 17.1. PFS is a registered Data Controller with the Information Commissioners Office in the UK under registration number Z1821175 xxxxx://xxx.xxx.xx/ESDWebPages/Entry/Z1821175

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

  • Personal Data Processing 2.1 The Processor shall process Personal Data only on the basis of corresponding recorded orders from the Controller.

  • Processing of Personal Data (a) SORACOM collects and processes personal data about the Subscriber, including name, e-mail, IP-address as well as data on data uses and billing data in order to provide SORACOM’s service and other purposes such as billing.

  • PERSONAL DATA PROTECTION 7.1 By accessing ESZAM AUCTIONEER SDN BHD website, the E-Bidders acknowledge and agree that ESZAM AUCTIONEER SDN BHD website may collect, retain, or disclose the E-Bidder’s information or any information by the e-bidders for the effectiveness of services, and the collected, retained or disclosed information shall comply with Personal Data Protection Act 2010 and any regulations, laws or rules applicable from time to time.

  • Shared Personal Data This clause sets out the framework for the sharing of personal data between the parties as data controllers. Each party acknowledges that one party (the Data Discloser) will regularly disclose to the other party (the Data Recipient) Shared Personal Data collected by the Data Discloser for the Agreed Purposes.

  • 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: Registrant Name: Example Registrant Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxxx@xxxxxxx.xxx Admin Contact: Xxxx Registrant Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: xxxxxxxxxxxxx@xxxxxxx-xxxxxxxxxx.xxx Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216

Time is Money Join Law Insider Premium to draft better contracts faster.