Data processing agreement
Last updated: 18 November 2026 · under Art. 28 GDPR
Translation: this English version is provided to help you understand the data processing agreement. Only the German version is legally binding: https://parafeld.de/auftragsverarbeitung/
Anyone who works professionally with the Parafeld™ System Board and processes data of other people in the account or in a live session – for example of clients – is themselves the controller for this data. We then process it on your behalf. This agreement sets out how.
Parties. The controller is whoever holds an account with the Parafeld™ System Board and acts as a business in doing so (Unternehmer, § 14 BGB, German Civil Code) – hereinafter “controller”. The processor is METAFELD · Ulrich Reuther, Zossener Straße 41, 10961 Berlin, Germany, telephone +49 30 84523850, email service@parafeld.de – hereinafter “processor”.
Conclusion. The agreement is concluded electronically (Art. 28 (9) GDPR): when creating the account, by accepting the conditions for the account – the terms of use (hereinafter “main contract”). It applies to the account, whether it is used free of charge or with the Practice plan. On request we will confirm its conclusion in text form.
1. Subject matter and duration
(1) The processor provides the account with folders and saved constellations and the live session, backs up the data and provides support with questions and faults. In doing so, it processes personal data on behalf of the controller.
(2) The nature and purpose of the processing, the types of data and the data subjects are described in section 12.
(3) The agreement applies for as long as the account exists, and beyond that until all data has been deleted in accordance with section 9.
2. Instructions
(1) The processor processes the data only on documented instructions from the controller. Instructions are the main contract, this agreement and the controller’s actions in the board and in the account – for example saving, changing, moving and deleting constellations and folders, starting and ending a live session. The controller issues further instructions in text form to service@parafeld.de.
(2) If the processor considers an instruction to be unlawful, it will say so without undue delay. It may suspend carrying it out until the controller confirms or changes it.
(3) No processing takes place outside the European Union and the European Economic Area, unless the processor is legally obliged to do so; in that case it informs the controller beforehand, insofar as the law permits.
3. Obligations of the processor
(1) Confidentiality. Only persons needed for operation and support have access to the data. They are bound to confidentiality; this obligation continues beyond their activity.
(2) Security. The processor takes the technical and organisational measures set out in section 13 and adapts them to the state of the art. It may change them provided the level of protection does not decrease.
(3) No use for its own purposes. The processor does not analyse the content, does not use it for its own purposes and does not pass it on to third parties. It looks at content only if the controller asks it to (for example in the case of a reported fault) or if the law obliges it to. Development and test series are carried out with sample data, not with the controller’s data. Before each deployment, the new release is started once on a trial basis on the same server against a copy of the database to check that it can read the data; no one looks at content in the process, and the copy is deleted afterwards. Further copies are made only as data backups.
(4) Record. The processor keeps a record of processing activities in accordance with Art. 30 (2) GDPR.
(5) The contact person for data protection is Ulrich Reuther, service@parafeld.de.
4. Obligations of the controller
(1) The controller is responsible for the lawfulness of the processing, in particular for the legal basis, for informing the data subjects (Art. 13, 14 GDPR) and for the obligations of their profession such as professional confidentiality.
(2) The controller enters only data needed for their work. The processor recommends neutral names such as initials or roles instead of full names.
(3) In support requests, the controller sends data of clients only if this is necessary for the request.
(4) If the controller notices errors or irregularities concerning data protection, they inform the processor without undue delay.
5. Sub-processors
(1) The controller approves the sub-processors listed in section 14 (general authorisation under Art. 28 (2) GDPR).
(2) The processor concludes an agreement with each sub-processor that imposes on it the obligations of this agreement (Art. 28 (4) GDPR). It is liable for the sub-processor as for its own actions.
(3) If the processor wishes to add or replace a sub-processor, it informs the controller by email at least four weeks in advance. The controller may object for an important reason relating to data protection law. If the two do not reach agreement, the controller may delete their account or cancel a running Practice plan with effect from the time of the change; amounts already paid for the period afterwards will be refunded pro rata.
(4) Ancillary services without access to the data, such as telecommunications or the transport of encrypted data over the internet, do not constitute sub-processing.
6. Support for the controller
(1) For requests from data subjects (Art. 12 to 22 GDPR), self-service in the account is the main help: viewing constellations, exporting them as a file, correcting and deleting them. The processor forwards requests that it receives to the controller without undue delay.
(2) It supports the controller with the security of processing, with notifications and communications following personal data breaches and with a data protection impact assessment (Art. 32 to 36 GDPR), using the information available to it.
7. Personal data breaches
(1) The processor notifies the controller of a personal data breach without undue delay, at the latest within 36 hours of becoming aware of it, by email to the account’s address.
(2) The notification contains, as far as known: the nature of the breach, the data and persons concerned (categories and approximate number), the likely consequences, the measures taken and proposed, and a contact person. Missing information is provided subsequently.
(3) The controller decides on notification to the supervisory authority (Art. 33 GDPR) and communication to the data subjects (Art. 34 GDPR). The processor documents every breach.
8. Evidence and inspections
(1) The processor makes available all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR; on request once a year as written information on the measures under section 13.
(2) The controller may carry out inspections itself or have them carried out by an auditor bound to confidentiality. Inspections are announced with reasonable notice (usually two weeks, shorter in the event of an incident) and take place during normal business hours. For the data centre, its own evidence is generally sufficient, for example a certification under ISO/IEC 27001.
9. Deletion and return
(1) The controller can export their constellations as a file at any time and delete constellations, folders or the whole account. The processor removes deleted items from the database immediately.
(2) Deleted data disappears from the backups automatically when they expire, after 30 days at the latest (section 13).
(3) The folders remain readable, exportable and deletable until the controller deletes them or the account, or the account ends in accordance with the main contract – even if a Practice plan ends. When the account ends, all data is deleted.
(4) On request the processor confirms the deletion in text form.
10. Liability
Liability towards data subjects is governed by Art. 82 GDPR. As between the parties, the liability clause of the main contract applies, unless the law mandatorily provides otherwise.
11. Final provisions
(1) In the event of contradictions, this agreement takes precedence over the main contract in matters of data protection.
(2) Changes require text form. The rule of the main contract on changes applies accordingly to changes to this agreement; information about new sub-processors is governed by section 5.
12. Subject matter, data and data subjects
Purpose: provision of the account with folders and saved constellations, synchronisation of the board in the live session, data backup, support with questions and faults.
Nature of the processing: storing, retrieving and displaying in the account, transmitting to the devices of the participants (live session), backing up, restoring, deleting.
| Area | Data | Data subjects |
|---|---|---|
| Folders and constellations in the account | Name of the folder, title of the constellation and everything contained in the constellation: labels of the figures (names or roles), speech bubbles, feelings and symbols, notes on the figures, concern, session notes, snapshots with explanations, position and line of sight of the figures; plus a small preview image. Stored unencrypted on the server, not end-to-end encrypted. | Clients, their relatives and other persons who appear in a constellation |
| Live session | State of the board, changes, names of the participants, chat and views – exclusively end-to-end encrypted, the processor cannot read them; time stamps. List of those present and chat only in working memory. | Participants, persons who appear in the constellation |
| Support | whatever the controller sends to support | depending on the content |
Special categories: depending on the work, constellations may contain health data or other special categories of personal data (Art. 9 GDPR), for example about family, illness or relationships. The controller decides what is stored.
Not part of this agreement is the data that the processor processes as a controller in its own right: email address, name, password and plan of the account and, where applicable, order, payment and cancellations. The privacy policy applies to this. The processor does not handle the picture to take home or the scene link: the constellation is contained entirely in the link, and nothing is stored on the server.
13. Technical and organisational measures (Art. 32 GDPR)
| Area | Measure |
|---|---|
| Data centre | own server in the data centre of Hetzner Online GmbH in Nuremberg (Germany); physical access only for data centre staff |
| Access to the server | only via SSH with a key, password login disabled; database and backups readable only by the system administration |
| Access to the account | only via HTTPS; password at least 10 characters, stored only as a hash (scrypt); sign-ins stored only as a hash, ending after 90 days without use; codes for confirmation, for resetting the password and for confirming a withdrawal random, stored only as a hash, time-limited (48 hours, 2 hours, 14 days) and valid only once; emails with such links held in an outbox until they are handed over to the mail server (no longer than 48 hours); limits against password guessing, mass sign-ups and floods of emails; after the password is reset, all sign-ins end |
| Separation | each folder and constellation belongs to one account and can be retrieved only when signed in to that account |
| Encryption | transfer always encrypted (TLS); live session end-to-end encrypted (the key is in the invitation link after “#” and never reaches the server); folders and constellations in the account and the backups are stored unencrypted; the backups are transferred encrypted via SSH |
| Logs | no content, no email addresses and no IP addresses in the application log; no web server access log for api.parafeld.de; IP addresses only in working memory as counters for the limits, for one hour at most |
| Data backup | every night a verified copy of the database on the server (14 daily copies) and on a separate backup storage of Hetzner Online GmbH in Germany (around 10 days of history); in addition, nightly images of the entire server at Hetzner (7 in total) |
| Deletion | deleted constellations, folders and accounts immediately from the database; from the backups when they expire, after 30 days at the latest; live rooms immediately with “End for everyone”, otherwise 30 days after last use; unconfirmed sign-ups after 48 hours |
| Software releases | before each deployment, new software releases go through automated test series and a trial start against a copy of the database |
| Review | review of these measures once a year |
14. Sub-processors
| Company | Service | Location |
|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen | Application server (account, folders, live session), images of the server and backup storage | Germany |
| ALL-INKL.COM – Neue Medien Münnich, owner René Münnich, Hauptstraße 68, 02742 Friedersdorf | Email mailbox service@parafeld.de (only insofar as a support request contains data of third parties) | Germany |
Stripe does not receive any constellation data. Only after an order for the Practice plan does Stripe process account and payment data of the customers themselves, and it is a controller in its own right for this; Stripe is not involved in the free account.