Customer Data Privacy and backups
1. Customer Data remains the property of the Customer. eLabNext and its subcontractors are entitled to store and process the Data to the extent that this is necessary to provide the Services under the Agreement, to prevent or address technical or security issues or is otherwise allowed in accordance with the Terms of Use.
2. If Customer Data includes personal data, both Parties will comply with their respective obligations under applicable data protection law and, to the extent necessary, will conclude a DPA.
3. The Customer is responsible for the processing of Customer Data and is obliged to assess whether Customer Data, in view of its sensitive nature, is suitable to be processed through or with the use of the Services.
Customer Data Privacy. 3.1. Customer further grants to Entrust (or its Affiliates, and any of their respective licensors and service providers), a world-wide, limited right, during the Device Reputation Service Term, to host, copy, transmit and display Customer Data and Personal Data as reasonably necessary for Entrust (or its Affiliates, and any of their respective licensors and service providers) to provide Device Reputation Service in accordance with the Agreement.
Customer Data Privacy. 8.1 To use the Solution, Customer will input Customer Data and Weeva will collect Customer Data from the Customer which may include Personal Data, as defined in the DPA.
8.2 Weeva will maintain appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Customer Data, as described in the Data Security Addendum available at xxx.xxxxx.xxxxx/policies. Those safeguards will include, but will not be limited to, measures designed to prevent unauthorised access to or disclosure of Customer Data (other than by Customer or Users). Weeva will process Customer Data on behalf of the Customer and in terms of the DPA available at xxx.xxxxx.xxxxx/policies. Both the Data Security Addendum and the DPA shall apply to the extent Customer Data includes Personal Data.
8.3 Weeva’s Privacy Notice available at xxx.xxxxx.xxxxx/policies. It sets out how Weeva will process Personal Data.
8.4 Notwithstanding the above, Customer recognises and agrees that hosting Customer Data online involves risks of unauthorised disclosure or exposure and that, in accessing and using the Solution, Customer assumes such risks. Weeva offers no representation, warranty, or guarantee that Customer Data will not be exposed or disclosed through errors or the actions of third parties.
8.5 Weeva may permanently erase Customer Data if Customer’s account is delinquent, suspended, or terminated for 30 days or more.
8.6 Weeva shall have no responsibility or liability for the accuracy of or content of Customer Data uploaded to the Solution by Customer. Customer represents and warrants that Customer Data does not and will not include, and Customer has not and shall not upload or transmit to Weeva's computers or other media, any content that is prohibited in the AUP available at xxx.xxxxx.xxxxx/policies including, without limitation, any content that may infringe on any third party intellectual property rights.
8.7 Customer grants Weeva a non-exclusive, worldwide, limited licence to the Customer Data for the purposes of: (i) providing the Solution to Customer; (ii) improving the Solution; and (iii) for developing and publishing market reports, but only when the Customer Data has been aggregated or de-identified such that the publication cannot be used to identify Customer.
8.8 Customer will own the Customer Data contained within reports downloaded or generated by the Solution, and Xxxxx will own the reports. Subject to payment of the fees, Weeva g...
Customer Data Privacy. Charging Station operators must collect, process, and retain only that personal information strictly necessary to provide the charging service to a consumer, including information to complete the charging transaction and to provide the location of charging stations to the consumer. EV Chargers and charging networks should be compliant with appropriate Payment Card Industry Data Security Standards (PCI DSS) for the processing, transmission, and storage of cardholder data. Charging Station operators must also take reasonable measures to safeguard consumer data. Traffic Control Devices or On-Premises Signs Acquired, Installed, or Operated – General Requirements: Signage must comply with all applicable local, state, and/or federal laws, ordinances, regulations, and standards. On-Site: Signage and other traffic control devices for each Host Site must clearly identify to an approaching driver from any ingress, that the Host Site has an EV Charger(s) and the location(s) of the EV Charger(s). On-site signage should indicate that parking spaces associated with the EV Chargers are reserved for electric vehicles only. The Manual on Uniform Traffic Control Devices for Streets and Highways (MUTCD) found at 23 CFR Part 655 and the Highway Beautification regulation at 23 CFR Part 750 address requirements about traffic control devices and on-premise signs.
Customer Data Privacy. Charging station operators must collect, process, and retain only that personal information strictly necessary to provide the charging service to a consumer, including information to complete the charging transaction and to provide the location of charging stations to the consumer. Chargers and charging networks should be compliant with appropriate Payment Card Industry Data Security Standards (PCI DSS) for the processing, transmission, and storage of cardholder data. Charging Station Operators must also take reasonable measures to safeguard consumer data. Traffic Control Devices or On-Premises Signs Acquired, Installed, or Operated – General Requirements: Signage must comply with all applicable local, state, and/or federal laws, ordinances, regulations, and standards; and On-Site: Signage and other traffic control devices for each Host Site must clearly identify to an approaching driver from any ingress, that the Host Site has an EV Charger(s) and the location(s) of the EV Charger(s). On-site signage should indicate that parking spaces associated with the chargers are reserved for electric vehicles only. The Manual on Uniform Traffic Control Devices for Streets and Highways (MUTCD) found at 23 CFR part 655 and the Highway Beautification regulation at 23 CFR part 750 address requirements about traffic control devices and on-premise signs. Manual on Uniform Traffic Control Devices for Streets and Highways. All traffic control devices must comply with part 655 of this subchapter. On-Premises Signs. On-property or on-premise advertising signs must comply with part 750 of this chapter. Requirements for Accessibility and Availability – The chargers awarded through this RFP must: Be available to the public 24 hours per day, seven (7) days a week, year-round; Be accessible from a paved or hardscaped parking space that is clearly marked to designate the spaces as reserved for EV Charger parking, where the number of parking spaces reserved for EVs, within reach of the DCFC, is equal to the maximum number of EVs that can be charged simultaneously from chargers awarded pursuant to the RFP; Have dusk-to-xxxx area lighting; Be accessible to persons with disabilities, which will be satisfied if at least one of the parking spaces meets ADA requirements and is accessible according to U.S. Access Board Design Recommendations for Accessible Electric Vehicle Charging Stations (it will not be necessary for the ADA spaces to be ADA reserved);2 and For eligible segments #1 and ...
Customer Data Privacy. Each party will comply with its obligations under (a) Data Protection Legislation (and neither party shall exercise its rights or perform its obligations under this Agreement in such a way as to cause the other party to breach any Data Protection Legislation) and (b) the DPA.
Customer Data Privacy. 17.1. The Parties acknowledge that for the purposes of the App and with regards to their relationship and all the data, including but not limited to customer data, Go Eats is the Data Controller and Data Processor, such meaning been given to them under the Data Protection Xxx 0000.
17.2. The Partner may collect customer information separately by itself and in such case Partner will be the Data Controller. Although, for any customer information stored on or processed through any platform provided by Go Eats, Go Eats is the Data Controller and Data Processor.
17.3. The Partner may not use any data collected through Go Eats Services for any purpose other than fulfilment of an Order.
17.4. While processing any data, the Partner shall comply with all data protection legislation and take all appropriate technical and organisational measures to protect the personal data against any unauthorised or unlawful processing of the data.
17.5. The Partner must take all reasonable steps to ensure that no personal data is published, disclosed, divulged or transferred to any third party or the Partner’s agents or contractors, without prior consent of Go Eats.
17.6. Go Eats will retain your data for as long as is necessary, and for a period of up to six (6) years following closure or termination of your account. We may:
17.6.1. share your customer data with third party service providers for the purpose of fulfilling its Services, including (among other things) account administration and informing you about Go Eats’s services in the future;
17.6.2. use cookies in the App, and you may also have the option of activating and de-activating (as the case may be) cookies through your browser.
17.7. Any breach of this clause 17 will be considered a Default and clause 7.11 above will apply.
Customer Data Privacy. 17.1. The Parties acknowledge that for the purposes of the App and with regards to their relationship and all the data, including but not limited to customer data, Go Eats is the Data Controller and Data Processor, such meaning been given to them under the Data Protection Xxx 0000.
17.2. The Driver may collect customer information separately by itself and in such case Driver will be the Data Controller. Although, for any customer information stored on or processed through any platform provided by Go Eats, Go Eats is the Data Controller and Data Processor.
17.3. The Driver may not use any data collected through the Go Eats Driver App for any purpose other than fulfilment of deliveries.
17.4. While processing any data, the Driver shall comply with all data protection legislation and take all appropriate technical and organisational measures to protect the personal data against any unauthorised or unlawful processing of the data.
17.5. The Driver must take all reasonable steps to ensure that no personal data is published, disclosed, divulged or transferred to any third party or the Driver’s agents or contractors, without prior consent of Go Eats.
17.6. Go Eats will retain your data for as long as is necessary, and for a period of up to six (6) years following closure or termination of your account. We may:
17.6.1. share your customer data with third party service providers for the purpose of fulfilling its services, including (among other things) account administration and informing you about Go Eats’s services in the future;
17.6.2. use cookies in the App, and you may also have the option of activating and de-activating (as the case may be) cookies through your browser.
17.7. Any breach of this clause 17 will be considered a Default and clause 7.11 above will apply.
17.9. This clause 17 shall survive the termination or expiry of this Agreement.
Customer Data Privacy a. Charging station operators must collect, process, and retain only that personal information strictly necessary to provide the charging service to a consumer, including information to complete the charging transaction and to provide the location of charging stations to the consumer. Chargers and charging networks should be compliant with appropriate Payment Card Industry Data Security Standards (PCI DSS) for the processing, transmission, and storage of cardholder data. Charging Station Operators must also take reasonable measures to safeguard consumer data.
Customer Data Privacy
