Customer Contact Information Sample Clauses

Customer Contact Information. Customer will provide Standards Digital with accurate billing and other contact information for all Subscribed Services listed on each Order Form and SOW at all times during the Service Term, including the name of Customer’s applicable legal entity, and the street address, e-mail address, name and telephone number of an authorized billing contact. Customer shall update this information within thirty (30) days after any changes, via email to Standards Digital’s Accounts Receivable team at ▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ for billing contact information. Customer shall also maintain, at all times during the Service Term, at least one User who is a current employee and is authorized to administer Customer’s use of the Service (e.g., by creating accounts and resetting passwords).

Customer Contact Information. Customer is responsible for ensuring that Flexera has at all times updated and accurate Customer contact information for Flexera to notify Customer regarding any security and products related issues. Customer shall provide Customer current contact information via the Flexera support portal.

Customer Contact Information. Customer shall provide in the Subscription Service accurate, current, and complete information on Customer’s legal business name, address, email address and phone number, and maintain and promptly update this information if it should change. The Customer shall provide both contact information for legal notices and service notices related to the Subscription Service.

Customer Contact Information. Customer agrees to provide PV accurate billing and other contact information for each Order Form and SOW at all times during the Service Term, including the name of Customer’s applicable legal entity, and the street address, e-mail address, name and telephone number of an authorized billing contact. Customer shall update this information within 30 days after any changes, via email to PV’s at ▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇. Customer shall also maintain, at all times during the Service Term, at least one User who is a current employee and is authorized to administer Customer’s use of the Service (e.g., by creating accounts and resetting passwords).

Customer Contact Information. To communicate with our customers, HCL Software Support maintains a record of Company and Contact details that include, but is not limited to, Company Name, Company address, Contact Name, email address, and telephone number. Case data including Customer Contact data: The communication data would be any information that the customer enters in the support portal itself during the lifetime of the case (i.e. description of their problem, communication back and forth with HCL support team to troubleshoot the issue). Diagnostic data: To work on customer support queries, information between the customer and HCL Support needs to be shared. Customers may upload data, like log and configuration files, for Support to use in troubleshooting reported problems. Security measures Case data including Customer Contact data: HCL Support keeps Customer Support related information in our Ticketing System, which is hosted by an accredited external company on servers in Canada. The communication is done via HTTPS and uses the protocol supported is TLS 1.2. This backend database is encrypted. Diagnostic data: The data is sent via SFTP or HTTPS and is encrypted once on HCL servers. The database encryption algorithm is AES (Advanced Encryption Standard 360bit). Transfers to countries outside the European Economic Area without a suitable level of protection for which the Data Controller has granted its authorization: Case data including Customer Contact data: We keep Customer Support related information in our Ticketing System, which is hosted by an accredited external company on servers in Canada. Diagnostic data: HCL Support diagnostic data is housed in what we call the Customer Data Repository. This is hosted in Bangalore, India. HCL Support standard data analysis environments are hosted in data centers across US, India, and Italy and are used by our worldwide support engineers. The following Subprocessors may be used to provide services in connection with the Agreement: Amazon AWS USA Cloud hosting services used to reproduce customer reported problems ServiceNow Canada Cloud hosting service used for ticketed management system For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection (the data exporter) and (the data importer) HAVE AGREED on the following Contractual Clauses (the Clauses) in order to adduce adequate safeguards with respect to the ...

Customer Contact Information. Customer agrees to provide App Orchid accurate billing and other contact information for each Order Form and SOW at all times during the Service Term, including the name of Customer’s applicable legal entity, and the street address, e-mail address, name and telephone number of an authorized billing contact. Customer shall update this information within thirty (30) days after any changes, via email to App Orchid’s Accounts Receivable team at ▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇ for billing contact information. Customer shall also maintain, at all times during the Service Term, at least one User who is a current employee and is authorized to administer Customer’s use of the Service (e.g., by creating accounts and resetting passwords).

Customer Contact Information. To communicate with the data exporter regarding their product support cases, the data importer maintains a record of Company and Customer Contact details. • Case communication data including Customer Contact data: The communication data would be any information that the data exporter enters in the customer support portal itself during the lifetime of the case (i.e. description of their problem, communication back and forth with data importer to troubleshoot the issue). • Diagnostic data: The diagnostic data would be shared by the data exporter to the data importer in order to troubleshoot the reported issue in the support case. Such data could include configuration files, log data, or any other piece of relevant data for such investigation. Name: ……………………………………………………………… … …………………………… Name: ……………………………………………………………… ……………………………… This Appendix forms part of the Clauses and must be completed and signed by the parties. Description of the technical and organisational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c) (or document/legislation attached): HCL SW has implemented various technical and organizational security measures to comply with the data processor requirements of various geographies. HCL SW has documented and implemented data privacy policies and procedures. The Data Privacy Organization structure is a part of overall Risk & Compliance Governance Structure in HCL. There is a nominated chief privacy officer who oversees data protection at the organizational level. The HCL privacy statement can be found on our website Description of the technical and organisational security measures implemented by the data processor: • HCL SW has an identified Information Security organization structure which oversees information security related processes and activities for HCL SW. • HCL has defined and documented data privacy policies and processes addressing access to personal data. • HCL has defined, documented and implemented a Risk Management framework to identify risks related to security, privacy and other contractual requirements. • Mandatory Information Security awareness training is provided through a country-wide e- Learning module. • All incidents reported are analyzed for root cause and impact. The remedial actions are initiated by the process owners. The key incidents along with their root causes and impact are reported to HCL management. • HCL SW Data Centers are ISO 27001certified. • Physical access to Data ...

Customer Contact Information. ITS will use the following information as a means of contacting the assigned faculty or staff who are responsible for managing the technical and operational aspects and service(s) listed in this SLA. Students are not acceptable as Customer contacts for this SLA. The Primary Technical Contact is the first person ITS will contact under the terms of this agreement. The Secondary Technical Contact will be contacted if the primary contact cannot be notified. Both personnel agree that under certain special circumstances, ITS staff will contact them any time day or night including official holidays if the situation demands immediate attention under the terms of this agreement. Name: Name: Designation: Designation: Department: Department: Bldg/Room: Bldg/Room: Mail Code: Mail Code: Phone: Phone: Cell/Pager: Cell/Pager: Email address: Email address: Signature: Signature: Date: Date: The Customer is also required to provide ITS with a System Owner contact and a System Billing Contact. Name: Name: Designation: Designation: Department: Department: Bldg/Room: Bldg/Room: Mail Code: Mail Code: Phone: Phone: Cell/Pager: Cell/Pager: Email address: Email address: Signature: Signature: Date: Date: Customer requests for services under this agreement should be directed to the ITS Customer Support Center by sending electronic mail to ▇▇▇▇▇▇▇@▇▇▇.▇▇▇ or by calling (▇▇▇) ▇▇▇-▇▇▇▇. Questions specific to the billing, support cost and adding or removing services or contact staff from this agreement should be addressed to ITS via ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇//its/contact/billing.html or by calling (▇▇▇) ▇▇▇-▇▇▇▇.

Customer Contact Information. 20.1 If you have any questions about the App you can email us at ▇▇▇.▇▇▇▇▇▇▇▇.▇▇.▇▇/▇▇▇▇▇▇▇ centre. 20.2 If you have any questions about a product or service, you must call the Merchant directly.