Password protected access Sample Clauses

Password protected access. Access to the Services and to Student Data by ▇▇▇’s users and Provider’s employees and contractors shall be secured through authentication protocols designed to ensure that Student Data may only be viewed or accessed by parties legally allowed to do so.
View Source
Password protected access. 11.1. We provide You with password protected access to my.digitalSTROM via the Internet. We use a secure transmission protocol (Secure Sockets Layer, SSL / Transport Layer Security, TLS) to encrypt Your transmitted data to protect the security of Your data during transmission. 11.2. You are obligated not to disclose Your access data to unauthorized parties. You are responsible for carefully storing Your access data, and protect it against access by third parties. We reject any and all liability for damage incurred due to the misuse by You or loss of Your access data (user ID, password).
View Source
Password protected access. 6.1. The Operator grants to you as a User a password-protected access to the Cloud Service via the Internet. You will be authorized by your employer to use the Cloud Service. 6.2. You as a User undertake not to disclose your access data to unauthorized persons and to keep this data adequately protected against access by third parties. 6.3. The Operator disclaims any liability for damage incurred by you or your employer due to the misuse or loss of the access data (e.g. User identification, password) provided to you or selected by you yourself.
View Source
Password protected access. 6.1. Access to PVS is password-protected via the web portal or via the PVS app for mobile devices. Users can be authorized and assigned roles in PVS by the Client in accordance with Section 5.2. Users can only connect the PVS App to the customer's PVS account if the customer's administrator has granted the corresponding rights and the user has connected their own PVS App to the customer's PVS account upon notification by the administrator.
View Source

Related to Password protected access

  • ACCESS TO PROTECTED HEALTH INFORMATION 7.1 To the extent Covered Entity determines that Protected Health Information is maintained by Business Associate or its agents or Subcontractors in a Designated Record Set, Business Associate shall, within two (2) business days after receipt of a request from Covered Entity, make the Protected Health Information specified by Covered Entity available to the Individual(s) identified by Covered Entity as being entitled to access and shall provide such Individuals(s) or other person(s) designated by Covered Entity with a copy the specified Protected Health Information, in order for Covered Entity to meet the requirements of 45 C.F.R. § 164.524. 7.2 If any Individual requests access to Protected Health Information directly from Business Associate or its agents or Subcontractors, Business Associate shall notify Covered Entity in writing within two (2) days of the receipt of the request. Whether access shall be provided or denied shall be determined by Covered Entity. 7.3 To the extent that Business Associate maintains Protected Health Information that is subject to access as set forth above in one or more Designated Record Sets electronically and if the Individual requests an electronic copy of such information, Business Associate shall provide the Individual with access to the Protected Health Information in the electronic form and format requested by the Individual, if it is readily producible in such form and format; or, if not, in a readable electronic form and format as agreed to by Covered Entity and the Individual.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Access to Protected Information If BA maintains a designated record set on behalf of CE, BA shall make Protected Information maintained by BA or its agents or subcontractors in Designated Record Sets available to CE for inspection and copying within five (5) days of a request by CE to enable CE to fulfill its obligations under state law [Health and Safety Code Section 123110] and the Privacy Rule, including, but not limited to, 45 C.F.R. Section 164.524 [45 C.F.R. Section 164.504(e)(2)(ii)(E)]. If BA maintains Protected Information in electronic format, BA shall provide such information in electronic format as necessary to enable CE to fulfill its obligations under the HITECH Act and HIPAA Regulations, including, but not limited to, 42 U.S.C. Section 17935(e) and 45 C.F.R. Section 164.524.

  • Data Protection and Privacy: Protected Health Information Party shall maintain the privacy and security of all individually identifiable health information acquired by or provided to it as a part of the performance of this Agreement. Party shall follow federal and state law relating to privacy and security of individually identifiable health information as applicable, including the Health Insurance Portability and Accountability Act (HIPAA) and its federal regulations.

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