Customer Data; Profiles; Authentication Records; Personal Data Sample Clauses

Customer Data; Profiles; Authentication Records; Personal Data. Customer acknowledges and agrees that the Entrust Technology requires certain Customer Data, Profiles, and Personal Data, in order to operate. Use of the Entrust Technology by Customer and Users will also generate Authentication Records. Customer grants to Entrust, its Affiliates, and any of their respective applicable subcontractors and hosting providers, a world-wide, limited right, during the Term, to host, copy, store, transmit, display, view, print or otherwise use Customer Data and Personal Data as reasonably necessary for Entrust (or its Affiliates, and any of their respective applicable subcontractors and hosting providers) to provide the Entrust Technology in accordance with the Agreement.
AutoNDA by SimpleDocs
Customer Data; Profiles; Authentication Records; Personal Data. Customer (or Tenant) acknowledges and agrees that the Service requires certain Customer Data, Profiles, and Personal Data, in order to operate. Use of the Service by Customer, Tenants, and Users will also generate Authentication Records. Customer (or Tenant) grants to Entrust Datacard, its Affiliates, and any of their respective applicable subcontractors and hosting providers), a world-wide, limited right, during the Term, to host, copy, transmit and display Customer Data and Personal Data as reasonably necessary for Entrust Datacard (or its Affiliates, and any of their respective applicable subcontractors and hosting providers) to provide the Service in accordance with the Agreement.
Customer Data; Profiles; Authentication Records; Personal Data. MSP (Sub-MSP or Tenant) acknowledges and agrees that the Service may require certain Customer Data, Profiles, and Personal Data, in order to operate. Use of the Service by MSP, Sub-MSPs, Tenants, and Users may also generate Authentication Records. MSP (Sub-MSP or Tenant) acknowledges and agrees that the Service allows for the uploading of certain Customer Data (including Personal Data), which may be used in order to design the Credentials. MSP (Sub-MSP or Tenant) shall have sole responsibility for the accuracy, quality, integrity, legality, reliability, appropriateness and copyright of all Customer Data (including Personal Data), and the means by which MSP (Sub-MSP or Tenant) acquired them. MSP (Sub-MSP or Tenant) grants to Entrust, its Affiliates, and any of their respective applicable subcontractors and hosting providers), a world-wide, limited right, during the 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 applicable subcontractors and hosting providers) to provide the Service in accordance with the Agreement.
Customer Data; Profiles; Authentication Records; Personal Data. MSP (or Tenant) acknowledges and agrees that the Service may require certain Customer Data, Profiles, and Personal Data, in order to operate. Use of the Service by MSP, Tenants, and Users may also generate Authentication Records. MSP (or Tenant) acknowledges and agrees that the Service allows for the uploading of certain Customer Data (including Personal Data), which may be used in order to design the Credentials. MSP (or Tenant) shall have sole responsibility for the accuracy, quality, integrity, legality, reliability, appropriateness and copyright of all Customer Data (including Personal Data), and the means by which MSP (or Tenant) acquired them. Customer (or Tenant) grants to Entrust Datacard, its Affiliates, and any of their respective applicable subcontractors and hosting providers), a world-wide, limited right, during the Term, to host, copy, transmit and display Customer Data and Personal Data as reasonably necessary for Entrust Datacard (or its Affiliates, and any of their respective applicable subcontractors and hosting providers) to provide the Service in accordance with the Agreement.

Related to Customer Data; Profiles; Authentication Records; Personal Data

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

  • Processing of Customer Personal Data 3.1 UKG will:

  • Personal Data, Confidentiality, Recording of Telephone Calls and Records 22.1. The Company may collect client information directly from the Client (in his completed Account Opening Application Form or otherwise) or from other persons including, for example, the credit reference agencies, fraud prevention agencies, banks, other financial institutions, third authentication service providers and the providers of public registers.

  • Use of Customer Data Verizon, Verizon Affiliates and their respective agents, may use, process and/or transfer Customer Data (including intra-group transfers and transfers to entities in countries that do not provide statutory protections for personal information) as set forth in the Privacy Policy and as necessary:

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Access to Records – Files; Confidential Information Contractor shall maintain all books, documents, papers and records relating to the Agreement for at least seven years following completion of the project. Contractor shall maintain any other records pertinent to this Agreement in such a manner as to clearly document Contractor’s performance. City, state and federal government, and their duly authorized representatives shall have access to the books, documents, papers and records of the Contractor which are directly pertinent to the specific Agreement for the purpose of making audit, examination, excerpts and transcript. Contractor agrees that all files or other documents generated or in the possession of Contractor related to Contractor's delivery of service are the property of the City and shall be available to the City upon request. Contractor understands the nature of project/projects means that Contractor may be privy to information that is confidential, proprietary or sensitive in nature, which information shall not be disclosed to any third person or entity without the consent of the City of Bend or at the City's direction, either during the term of this Agreement or after its termination. Likewise, any analysis or commentary provided by Contractor of a confidential or sensitive nature shall not be released or disclosed to any person without the consent or direction of the City.

  • PRIVACY INFORMATION Through Your Use of the Website and Services, You may provide Us with certain information. By using the Website or the Services, You authorize the Company to use Your information in the United States and any other country where We may operate.

  • Access to Customer Data You agree that we may, for the purposes of providing Maintenance and Customer Support and/or for the purpose of otherwise protecting the integrity of the Software, access and/or download your Customer Data on a limited basis.

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