Security of Stored and Shared Data and Files Sample Clauses

Security of Stored and Shared Data and Files. Xxxx will endeavour to restrict access to the data and files that you store, retrieve and/or share from your Account to persons accessing such data and files through use of your Account or password. However, no password-protected system of data storage, retrieval and sharing can be made entirely impenetrable. Accordingly, you hereby acknowledge that it may be possible for an unauthorized third party to access, view, copy, modify and distribute data and files you store and/or share in your Account. As the Service utilizes the public Internet and third party networks to transmit data and files, Xxxx does not guarantee the security of any Content or other information transmitted or shared to or from the Service or your Account. Your shared space is designed for sharing; as such, it is recommended that this component of the Service should not include any of your confidential information. Any such use shall be at your sole risk and Xxxx, its affiliates and its agents and suppliers shall be relieved from all liability in connection therewith. SCHEDULE “H” TO XXXX MASTER BUSINESS INTERNET AND VALUE ADDED SERVICES AGREEMENT ("Agreement") BELL BUSINESS INTERNET SECURITY AND BELL BUSINESS INTERNET SECURITY PACK
Sample 1
AutoNDA by SimpleDocs
Security of Stored and Shared Data and Files. No password- protected system of data storage, retrieval and sharing can be made entirely impenetrable, and therefore, it may be possible for an unauthorized third party to access, view, copy, modify and distribute data and files you store and/or share in your account. As the Staples Service utilizes the public Internet and third party networks to transmit data and files, Staples does not guarantee the security of any content or other information transmitted or shared to or from the Staples Service or your account. Although Staples will use commercially reasonable efforts to protect your data while transferring it via the Internet to the Servers, your use of the Staples Service is at your sole risk and Staples, its affiliates, its agents and suppliers are hereby relieved from all liability in connection therewith. Although you may back up data locally on Your Systems up to a maximum amount set by you, remote backups of data are only possible once a connection to the Internet has been established.
Sample 1

Related to Security of Stored and Shared Data and Files

  • System Security and Data Safeguards When SAP is given access to Licensee’s systems and data, SAP shall comply with Licensee’s reasonable administrative, technical, and physical safeguards to protect such data and guard against unauthorized access. In connection with such access, Licensee shall be responsible for providing Consultants with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Licensee deems appropriate from time to time. Licensee shall not grant SAP access to Licensee systems or personal information (of Licensee or any third party) unless such access is essential for the performance of Services under the Agreement. The parties agree that no breach of this provision shall be deemed to have occurred in the event of SAP non-conformance with the aforementioned safeguard but where no personal information has been compromised.

  • Access to File 12.01 An employee shall upon written request, made a reasonable time before the time of viewing, have an opportunity to view their personnel file in the presence of the Director of Human Resources or their designate. The information the employee may review will be:

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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

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