Contracts

Technical and organisational measures

Annex 1 of the data processing agreement (Art. 32 GDPR).

This English version is a translation of the German original. In the event of any dispute, the German version shall prevail. Read the German version.

These measures form Annex 1 of our data processing agreement. They are also contained in the complete DPA template as a PDF.

The measures apply to all services under this agreement (Art. 32 GDPR). Information as of 18 November 2026; the values were measured on the processor's servers.

Location of processing

Servers in the Falkenstein (Germany) and Helsinki (Finland) data centres of the data centre operator named in Annex 2.

Physical access

The servers are located in the data centres of the data centre operator. Physical access is governed by its technical and organisational measures under the agreement pursuant to § 5 para. 4.

System access

Administrative access to the servers from outside is only possible via a central management access point with sign-in; sign-ins to servers only with SSH keys. Management applications can only be reached after sign-in via the central sign-in service with password and second factor, and only for accounts authorised for the respective service. Administrator sign-ins are logged.

Data access

Each application has its own database accounts with the permissions it requires. Credential files are stored outside the web directories and can only be read by the system administrator and the respective service.

Separation

Websites run in their own virtual hosts with their own web directories and databases, application instances are separated per customer; data of different controllers is not merged.

Transfer

The services are delivered via TLS. The TLS connection terminates at the processor's reverse proxy in Falkenstein (Germany); from there, requests are forwarded to the application servers in Helsinki (Finland), that is, between two data centres. The processor does not commit to additional transport encryption for this forwarding. Backups are transferred in encrypted form.

Pseudonymisation

Pseudonymisation by the processor is not provided for; the controller determines the content and form of the data through its use of the services.

Storage media

The servers' storage media are not encrypted. The backups are stored encrypted, as is data that an application encrypts itself.

Key management

The processor generates and keeps the backup keys (repository key and passphrase) itself on the server that writes the backup, readable only by the system administrator; the data centre operator receives backups and copies of these keys only in encrypted form. Keys with which an application encrypts data itself are kept by the processor separately from that data, per instance with an identifier; older keys are retained as long as backups made with them exist.

Availability

Daily backup of all servers, encrypted (Borg) on storage space of the data centre operator (Storage Box) in the Falkenstein data centre (Germany); retention of snapshots, daily snapshots 14 days, weekly 8 weeks, monthly 12 months, yearly 3 years; after the end of the contract, the controller's copies are locked until they expire (§ 8). Availability and load of the servers and services are monitored.

Resilience and recovery

The services run on individual servers without automatic failover to a second server; high availability is not part of the services. After an outage, the processor restores from the most recent daily backup. A documented recovery test in an isolated environment and a guaranteed recovery time are not yet available; the processor carries out the test at least once a year and discloses the result and measured duration on request.

Protection against malware

Incoming emails are checked for spam and malware, files in file sharing on receipt; the servers receive automatic security updates.

Security updates

Security updates are installed automatically; a security update that remains outstanding for more than 7 days triggers an alert.

Email transport

Submission by users only encrypted (submission with enforced TLS, SMTPS); mailbox retrieval (IMAP, POP3) only encrypted; TLS is used between mail servers if the other side offers it; MTA-STS and TLS reporting can be enabled per domain.

Input control

Access and changes can be traced via the logs of the web servers, the mail server, the system journal and the administrators' sign-in log.

Deletion periods

Web server access and error logs 14 days; block logs (fail2ban) 4 weeks; mail server logs 4 weeks; server system journal 30 days; administrator sign-in log 365 days; backups according to the rotation under “Availability”, at most 3 years. Contents of the services (websites, mailboxes, files, application data) are kept until deleted by the controller or on its instruction and in accordance with § 8.

Personnel

Persons with access are bound to confidentiality before starting their work (§ 3) and instructed in data protection; they receive access only to the extent required, and access is revoked without delay when they leave or change roles.

Incidents

Security incidents are detected through monitoring or reports, assessed, resolved and documented with cause, impact and remedy; the processor reports personal data breaches in accordance with § 7.

Destruction of storage media

Decommissioned server storage media are erased or destroyed by the data centre operator in accordance with its technical and organisational measures (agreement pursuant to § 5 para. 4).

Processing control

Processing only on documented instructions pursuant to § 2; further processors only pursuant to § 5 and with an agreement under Art. 28 para. 4 GDPR.

Review

The processor reviews these measures at least once a year and in the event of significant changes, documents the result and presents it on request (Art. 32 para. 1 lit. d GDPR).