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.
Backup Copies You may also make copies of the SOFTWARE PRODUCT as may be necessary for backup and archival purposes.
Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.
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.
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.
BACKUP COPY You may make one backup copy of the software. You may use it only to reinstall the software.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
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.