Unless otherwise defined, capitalised words and expressions have the same meaning as set out in the Software Licence Agreement entered into between you (or the entity for which you are acting) (the “Customer”) and Ionburst (the “Supplier”).
This Metadata Maintenance Policy contains Ionburst’s policy for providing metadata maintenance in relation to the Services.
The Supplier may modify the terms and conditions of this Metadata Maintenance Policy from time to time by posting such amended Metadata Maintenance to the Supplier’s site; but will provide sixty (60) days advance notice to the Customer before materially reducing the benefits offered to the Customer under this Metadata Maintenance Policy.
Issue: means a failure of the Services to substantially conform to the functional specifications set forth in the Documentation.
Third Party: the Cloud provider hosting the Supplier’s Software and Services and any regional presence thereof.
2. Metadata maintenance policy
2.1 Metadata Maintenance.
Metadata maintenance refers to measures and safeguards implemented by the Supplier to ensure the confidentiality, integrity and availability of metadata relating to Customer Data.
In the event of any loss or damage to Customer Data, the Customer’s sole and exclusive remedy against the Supplier shall be for the Supplier to use reasonable commercial endeavours to provide the Customer with available Customer comprehensible metadata to restore the lost or damaged Customer Data from the latest version of such metadata related to Customer Data maintained by the Supplier.
2.2 Measures and Safeguards.
The Supplier has implemented various measures and safeguards within the architecture, infrastructure/network and application layers of the Services to ensure the confidentiality, integrity and availability of metadata relating to Customer Data.
All databases used by the Services are segmented and segregated by architecture and network to ensure only legitimate network and application access is possible to each database. Application access is further enhanced through segregated service account access between the application components and the related databases, ensuring application comprising the Services can access only the databases and data required to operate. Service account credentials are stored programmatically in an encrypted store, further limited by policy to ensure applications can only access the service accounts they require to operate.
The Supplier also makes use of underlying functionality supplied by the Third Party to ensure each database used within the Services is regularly backed-up, with Third Party managed backups occurring every 24 hours. The Supplier supplements this backup functionality with its own automated backups, running multiple times an hour for each database. These backups are stored on encrypted storage within the Services internal infrastructure and allow the Supplier to readily restore functionality to the Services in the event of an Issue.