Customer Access to PII Sample Clauses

Customer Access to PII. Enrollment Assister hereby acknowledges, agrees, and consents to abide by and be bound by the privacy and security standards adopted by PHIEA, as amended and updated from time to time, while engaging in any activity as a Non-Exchange Entity or an Enrollment Assister for purposes of facilitating enrollment and evaluating Customer, Applicants, or Qualified Individuals entitlement to APTC and/or CSRs through the Exchange Platform. Enrollment Assister shall be bound to and strictly adhere to the privacy and security standards, and to ensure that its agents, subcontractors, assignees, or any other person that creates, collects, accesses, stores, maintains, discloses, or uses PII in the Exchange Platform strictly adheres to the same.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Customer Access to PII. Application Xxxxxxxx hereby acknowledges, agrees, and consents to abide by and be bound by the privacy and security standards adopted by Georgia Access, as amended and updated from time to time, while engaging in any activity as an Application Assister through the Exchange Platform. Application Assister shall be bound to and strictly adhere to the privacy and security standards, and to ensure that its agents, subcontractors, assignees, or any other person that creates, collects, accesses, stores, maintains, discloses, or uses PII in the Exchange Platform strictly adheres to the same.
Sample 1
Customer Access to PII. Exchange Producer hereby acknowledges, agrees, and consents to abide by and be bound by the privacy and security standards adopted by Georgia Access, as amended and updated from time to time, while engaging in any activity as an Exchange Producer for purposes of facilitating enrollment and evaluating Customer, Applicants, or Qualified Individuals entitlement to APTC or CSRs through the Exchange Platform. Exchange Producer shall be bound to and strictly adhere to the privacy and security standards, and to ensure that its agents, subcontractors, assignees, or any other person that creates, collects, accesses, stores, maintains, discloses, or uses PII in the Exchange Platform strictly adheres to the same.
Sample 1

Related to Customer Access to PII

  • Customer Access The Customer is responsible for the access to the Cloud Services and is responsible for maintaining the confidentiality of its access methods such as usernames and passwords and agrees to notify the Supplier via the Cloud Services support channel if a password is compromised. The Customer is responsible for all activities that occur under its Account.

  • User Access Transfer Agent shall have a process to promptly disable access to Fund Data by any Transfer Agent personnel who no longer requires such access. Transfer Agent will also promptly remove access of Fund personnel upon receipt of notification from Fund.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • ICANN Access Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

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