In cloud and hosting services the contract is a legal commitment as much as it is a technical document. Where the data will be stored, who may access it and what happens in the event of an outage are defined here. In translation the scope of these commitments can be neither narrowed nor widened.
Service descriptions
The scope of the service provided is defined in detail, and what falls outside the scope is listed. The two lists are read together. The scope is preserved.
Data location commitments
The country in which the data will be stored may be committed to, and this has legal consequences. Country and region names are carried over. The wording of the commitment is preserved.
Provisions on transfers abroad
The cross-border transfer of data is subject to regulations and is addressed in the contract. The terms come from the regulation. The established equivalent is used.
Sub-processor lists
The sub-processors used by the service provider are listed and notified. The list is carried over in full. A notice of change is issued.
Availability commitments
For how much of the time the service will be available is expressed as a percentage. The percentage and the measurement period have meaning together. Both are carried over.
Definition of downtime
What counts as downtime is defined in the contract and determines the calculation. The definition is not shortened. The exclusions are preserved.
Service credit calculations
The reduction that applies if the commitment is not met is defined. The calculation method is preserved. Amounts stay in their own fields.
Redundancy tiers
Data centres are classified according to the redundancy of their infrastructure, and the tier is stated. The tier notation is standard. It is carried over.
Power and cooling infrastructure
Uninterruptible power and cooling systems are defined in the technical documents. Capacity values are given with their units. The values are preserved.
Physical security measures
The controls on access to the facility are described in the documents and are subject to audit. The names of the measures are technical terms. They are translated consistently.
Independent audit reports
That the controls are operating is shown by an independent audit, and the types of report differ. The type notation is preserved. The statement of scope is carried over.
Certification documents
Certifications such as information security management come with a statement of scope. The scope is limited. The certificate numbers are carried over.
Incident notification periods
In the event of a security breach the notification period is defined and creates an obligation. Expressions of time are carried over exactly. No interpretation is added.
Backup and restore
The backup frequency and the restore objectives are defined. The target values are carried over. The terms are translated consistently.
Return of data at the end of the contract
How the data is to be returned or destroyed when the service ends is set out. The period and the format are defined. The provision is preserved.
Technical documentation
Configuration and integration documents are addressed to developers. Command and parameter names are not translated. The explanation is translated.
Capacity and usage reports
Usage is reported periodically and feeds invoicing. The units are not mixed up. The values are verified.
The costliest mistake in this sector
If the data location commitment becomes vague in translation, it means that the customer's data may be stored in another country. This is not only a breach of contract but a breach of data protection legislation. The location and transfer provisions are matched one to one.