SIGN UP LOGIN

Data Processing Agreement (DPA)

This is a convenience translation. Only the German version is legally binding: German version.

Agreement pursuant to Art. 28 GDPR between the customer (controller) and 72IT GmbH (processor).

Preamble and parties

This agreement specifies the parties' data protection obligations arising from the use of the service “lionbackup”. It applies to all processing activities in which 72IT GmbH, Vogelsangstraße 11, 72144 Dußlingen, Germany (hereinafter “processor”) processes personal data on behalf of and on the instructions of the customer (hereinafter “controller”).

1. Subject matter and duration of the processing

The subject matter of the processing is the encrypted storage, retention and restoration of the backup data transmitted by the controller, as well as the management of the associated accounts and metadata within the scope of the service. The duration of the processing corresponds to the term of the underlying main contract plus the statutory or contractually agreed retention and deletion periods.

2. Nature and purpose of the processing

The processing serves to provide the cloud backup service. This includes receiving and storing encrypted data objects via the storage endpoints (Citadels), immutable retention during the retention period, providing data for restoration, and operating the customer portal and the associated administrative functions. The processor does not process the data for its own purposes.

3. Types of personal data

The processing may cover in particular:

Specific data categories will be conclusively specified in the final DPA.

4. Categories of data subjects

Depending on the content backed up by the controller, the following may be affected:

The actual categories are determined by the controller; they will be recorded in the final DPA.

5. Obligations of the processor

6. Technical and organisational measures (Art. 32 GDPR)

The technical and organisational measures implemented by the processor are described in the TOMs and form part of this agreement. They include, among other things, encryption of transmission and storage, network and zone segmentation, access controls with multi-factor authentication and audit-proof logging.

7. Sub-processors

The controller grants the processor general authorisation to engage further sub-processors (e.g. infrastructure and data centre operators). Each sub-processor is bound by at least the same data protection obligations.

The processor gives notice of an intended change or addition at least 30 days in advance in text form. If it has to replace a sub-processor at short notice because the sub-processor has terminated the contractual relationship or ceased operations, it informs the controller without undue delay (section 11 of the terms and conditions). The controller may object within 14 days of receipt of the notice for an important reason under data protection law. If the parties do not reach an amicable solution within 14 days of the objection, either party may terminate the main contract extraordinarily with respect to the affected storage zone; section 11(3) of the terms and conditions applies accordingly to the objects stored there.

The sub-processors engaged are listed in Annex 1. The processor keeps the list up to date.

8. Support with data subject rights

The processor supports the controller with appropriate technical and organisational measures in responding to requests from data subjects for access, rectification, erasure, restriction, data portability and objection (Art. 12 to 23 GDPR). If a data subject contacts the processor directly, the processor forwards the request to the controller without undue delay.

9. Deletion and return

After the end of the processing, the processor deletes the personal data or, at the controller's choice, returns it, unless a statutory retention obligation precludes this. Storage follows the lifecycle of the service (stored → expired → deleted → final removal); details are set out in the service description.

For data in immutable storage (WORN), the following also applies: the controller sets the retention period per project itself (default 30 days, at most 365 days) and thereby instructs the processor to retain this data immutably for the chosen period. Deletion or modification before the retention period expires is technically impossible and therefore also impossible for the processor; an instruction to this effect is carried out when the retention period expires. Deletion takes place without undue delay after it expires. The controller takes this into account when choosing the retention period, in particular with regard to data subject rights (Art. 17 GDPR) and its own deletion concepts; it can shorten the retention period for future backups at any time. The processing of this data accordingly continues until it is deleted, even if the main contract otherwise ends earlier (clause 1).

10. Evidence and audits

The processor provides the controller with the information necessary to demonstrate compliance with the obligations under Art. 28 GDPR and allows reasonable reviews, including inspections, by the controller or an auditor appointed by the controller. Reviews must be announced in good time and carried out in such a way that operations are not disproportionately impaired.

Annex 1: Sub-processors (as of November 2026)

The operators of the storage zones act only for the projects that the controller creates in their zone. The backed-up content of a project does not leave the chosen zone.