Email backup. XXXX Services under this agreement do not include making backup copies of email, and XXXX is not responsible for retrieving deleted or purged emails.
Email backup Sample Clauses
Related to Email backup
Data Backup The Services do not replace the need for Customer to maintain regular data backups or redundant data archives. PROVIDER HAS NO OBLIGATION OR LIABILITY FOR ANY LOSS, ALTERATION, DESTRUCTION, DAMAGE, CORRUPTION OR RECOVERY OF CUSTOMER DATA.
Backup Authorized Devices that are not shared devices will periodically create automatic backups that are transmitted to the Service when the user is logged in with their Managed Apple ID and the device is screen-locked, connected to a power source, and connected to the Internet via a Wi-Fi network. You may disable backup in the MDM Enrollment Settings. Backup is limited to device settings, device characteristics, photos, videos, documents, messages (iMessage, SMS and MMS, if enabled), ringtones, app data (including Health app data), location settings (such as location-based reminders that You have set up), and Home screen and app organization. Content that You purchase, download or provide access to Your End Users from the iTunes Store, App Store or iBooks Store, and Content purchased from or provided by any third parties, will not be backed up. Such Content may be eligible for re- download from those services, subject to account requirements, availability, and any applicable terms and conditions. Content synced from Your End Users’ computers will not be backed up. If You enable iCloud Photo Library, the photo libraries of Your End Users will be backed up separately from their automatic iCloud backup. The Content stored in an End User’s contacts, calendars, bookmarks, and documents is accessible via iCloud on the web or on any of the End User’s Authorized Devices. When iCloud Backup is enabled, devices managed or controlled by Your Institution will not back up to iTunes automatically during a sync, but You may enable End Users to manually initiate a backup to iTunes. It is solely Your responsibility to maintain appropriate alternative backup of Your and Your End Users’ information and data.
Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.
Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.
Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.
Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.
Backups Provider agrees to maintain backup copies, backed up at least daily, of Student Data in case of Provider’s system failure or any other unforeseen event resulting in loss of Student Data or any portion thereof.
Computer The Contractor shall maintain at its office for its use a computer with, at a minimum, a 1 GHz processor and an internet connection. The Contractor shall maintain individual email accounts for each of its project managers.
Electronic Execution; Electronic Records; Counterparts This Agreement, any Loan Document and any other Communication, including Communications required to be in writing, may be in the form of an Electronic Record and may be executed using Electronic Signatures. Each of the Loan Parties and each of the Administrative Agent and each Lender Party agrees that any Electronic Signature on or associated with any Communication shall be valid and binding on such Person to the same extent as a manual, original signature, and that any Communication entered into by Electronic Signature, will constitute the legal, valid and binding obligation of such Person enforceable against such Person in accordance with the terms thereof to the same extent as if a manually executed original signature was delivered. Any Communication may be executed in as many counterparts as necessary or convenient, including both paper and electronic counterparts, but all such counterparts are one and the same Communication. For the avoidance of doubt, the authorization under this paragraph may include, without limitation, use or acceptance of a manually signed paper Communication which has been converted into electronic form (such as scanned into PDF format), or an electronically signed Communication converted into another format, for transmission, delivery and/or retention. The Administrative Agent and each of the Lender Parties may, at its option, create one or more copies of any Communication in the form of an imaged Electronic Record (“Electronic Copy”), which shall be deemed created in the ordinary course of such Person’s business, and destroy the original paper document. All Communications in the form of an Electronic Record, including an Electronic Copy, shall be considered an original for all purposes, and shall have the same legal effect, validity and enforceability as a paper record. Notwithstanding anything contained herein to the contrary, neither the Administrative Agent, L/C Issuer nor Swing Line Lender is under any obligation to accept an Electronic Signature in any form or in any format unless expressly agreed to by such Person pursuant to procedures approved by it; provided, further, without limiting the foregoing, (a) to the extent the Administrative Agent, L/C Issuer and/or Swing Line Lender has agreed to accept such Electronic Signature, the Administrative Agent and each of the Lender Parties shall be entitled to rely on any such Electronic Signature purportedly given by or on behalf of any Loan Party and/or any Lender Party without further verification and (b) upon the request of the Administrative Agent or any Lender Party, any Electronic Signature shall be promptly followed by such manually executed counterpart. Neither the Administrative Agent, L/C Issuer nor Swing Line Lender shall be responsible for or have any duty to ascertain or inquire into the sufficiency, validity, enforceability, effectiveness or genuineness of any Loan Document or any other agreement, instrument or document (including, for the avoidance of doubt, in connection with the Administrative Agent’s, L/C Issuer’s or Swing Line Lender’s reliance on any Electronic Signature transmitted by telecopy, emailed .pdf or any other electronic means). The Administrative Agent, L/C Issuer and Swing Line Lender shall be entitled to rely on, and shall incur no liability under or in respect of this Agreement or any other Loan Document by acting upon, any Communication (which writing may be a fax, any electronic message, Internet or intranet website posting or other distribution or signed using an Electronic Signature) or any statement made to it orally or by telephone and believed by it to be genuine and signed or sent or otherwise authenticated (whether or not such Person in fact meets the requirements set forth in the Loan Documents for being the maker thereof). Each of the Loan Parties and each Lender Party hereby waives (i) any argument, defense or right to contest the legal effect, validity or enforceability of this Agreement, any other Loan Document based solely on the lack of paper original copies of this Agreement, such other Loan Document, and (ii) waives any claim against the Administrative Agent, each Lender Party and each Related Party for any liabilities arising solely from the Administrative Agent’s and/or any Lender Party’s reliance on or use of Electronic Signatures, including any liabilities arising as a result of the failure of the Loan Parties to use any available security measures in connection with the execution, delivery or transmission of any Electronic Signature.
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.
