Data Processing Agreement (Art. 28 GDPR)

Last updated: October 2026

This agreement is available in German and English. The German version is the legally binding one; the English version is provided for convenience.

This agreement describes the processing as it is actually carried out, but it has not yet been reviewed by a lawyer.

§ 1 Subject matter, roles and term

This data processing agreement ("DPA") under Art. 28 GDPR forms part of the contract between Dr. Sergio Vargas - biodatum.io ("Provider", processor) and the business using Feedblick Swarm ("Customer", controller) under the terms and conditions, § 10. It applies when the Provider processes personal data on the Customer's behalf while providing the service, and it ends with the contract. The Customer decides on the purposes and means of that processing and is responsible for its lawfulness, including the lawfulness of using the service with the people it invites (for example with minors or in a school context, § 5 of the terms) and for informing them. The Provider is a controller, not a processor, for its own processing: host accounts, access requests, billing and payment records, security and the legal record of announcements. That processing is described in the privacy policy and is not covered by this DPA. The nature, purpose, data and data subjects are described in Annex 1.

§ 2 Instructions

The Provider processes the personal data only on the Customer's documented instructions, unless European or German law requires otherwise (in which case the Provider informs the Customer beforehand, unless the law forbids it). The Customer's instructions are this DPA, the terms, and the Customer's use of the service's functions (creating sessions and task lists, sending announcements, deleting sessions or the account). Further instructions that go beyond the service's functions need the Provider's agreement and may be charged for if they cause unreasonable effort. The Provider informs the Customer without undue delay if it believes an instruction infringes data-protection law. It may suspend the instruction until the Customer confirms or changes it.

§ 3 Confidentiality

The Provider ensures that everyone it authorises to process the personal data is bound to confidentiality or is under an appropriate statutory obligation of confidentiality, and processes the data only as far as their work requires.

§ 4 Security of processing

The Provider takes the technical and organisational measures required by Art. 32 GDPR. The measures at the time of this agreement are listed in Annex 2. The Provider may change them as long as the level of protection is not lowered. Material changes are documented.

§ 5 Sub-processors

The Customer gives the Provider a general authorisation to engage sub-processors. The sub-processors engaged at the time of this agreement are listed in Annex 3. The Provider informs the Customer of an intended addition or replacement in text form (for example by email to the address of the host account) at least two weeks beforehand. The Customer may object on important data-protection grounds within that period; if the parties cannot agree on a solution, the Customer may terminate the contract with effect from the date of the change. The Provider binds each sub-processor to data-protection obligations that correspond to those in this DPA, in particular as to security and confidentiality, and remains responsible to the Customer for their performance.

§ 6 Data subjects' rights and assistance

Taking into account the nature of the processing, the Provider helps the Customer, with appropriate technical and organisational measures, to answer requests from data subjects (access, rectification, erasure, restriction, portability, objection). If a data subject contacts the Provider directly about data the Provider processes for the Customer, the Provider forwards the request to the Customer and does not answer it itself, unless the law requires it. The Provider helps the Customer, with the information available to it, to comply with Articles 32 to 36 GDPR (security, notification of breaches, data protection impact assessments and prior consultation). Much of the participant data is not stored by the Provider at all (Annex 1). The Customer takes this into account when it answers requests: what is not stored cannot be disclosed or erased by the Provider.

§ 7 Personal data breaches

The Provider notifies the Customer without undue delay after becoming aware of a personal data breach affecting the Customer's data, with the information it has (nature of the breach, categories and approximate number of data subjects and records affected, likely consequences, measures taken or proposed), and supplements it as more becomes known. The Customer decides on any notification of the supervisory authority or the data subjects; the Provider helps as set out in § 6.

§ 8 Deletion and return

The Customer can delete individual sessions and its whole account at any time in the app. Deleting a session deletes its tasks and announcements; deleting the account deletes all of the Customer's sessions. The Customer can export a session's task list as a PDF once the session has ended. When a session ends (by the host, or by itself ten minutes after the last round of a scheduled session), the names stored with claimed tasks and the session's announcements are deleted automatically. When the contract ends, the Provider deletes the personal data it processes for the Customer, unless the law requires it to be kept (for example billing records, which are the Provider's own data and not covered by this DPA). Copies in the backups of a sub-processor are overwritten in the course of that sub-processor's regular backup cycle. The Provider confirms the deletion on request.

§ 9 Proof and audits

On request, the Provider gives the Customer the information necessary to show that the obligations in Art. 28 GDPR are met. The Customer, or an auditor bound to confidentiality that it appoints, may check this agreement's compliance once per year with reasonable notice, during normal working hours and without disrupting operations, at the Customer's cost. The Provider may meet the request in the first place by documents, such as the certifications of its sub-processors (for example SOC 2 reports), and the description in Annex 2.

§ 10 Processing location and transfers

The Provider processes the Customer's data in the European Union: the database in Frankfurt, Germany, and the web application in the Frankfurt region. A transfer to a country outside the EU/EEA (for example a sub-processor's support access from a group company in a third country) takes place only if the conditions of Chapter V GDPR are met, for example through an adequacy decision (such as the EU–US Data Privacy Framework) or the standard contractual clauses in the sub-processor's data processing agreement.

§ 11 Liability and final provisions

Liability under this DPA follows § 9 of the terms, without prejudice to data subjects' rights against both parties under Art. 82 GDPR and to the internal allocation of liability between the parties under the law. Remuneration for this DPA is included in the price of the plan; § 2 remains unaffected. Changes to this DPA follow § 12 of the terms. German law applies. If a provision is or becomes invalid, the others stay valid. In case of discrepancies between the German and the English version, the German version prevails.

Annex 1 Description of the processing

Subject and nature: providing a shared team timer and task board (storing and transmitting the data below so that the host and participants see the same session). Purpose: running the Customer's sessions as the Customer decides. No other purpose; no analytics, advertising or profiling. Duration: for the term of the contract; per session as set out in § 8. Data subjects: the Customer's hosts and their staff using the service; participants of the Customer's sessions (adults, and pupils or minors where the Customer uses the service in a school context). Types of data: - Session content the host enters: session names, task texts (including subtasks and links), the host's own group names, announcement texts and their time, the session's settings and timer state. - What a participant types or selects: a name or nickname, a group, an avatar (one of a fixed set of animal pictures) and a Done / Blocked / Need 2 min signal. These travel over a temporary live connection and are not stored by the Provider. When a participant signals Blocked, the host's screen answers that participant alone with a one-word message ("seen" or "on it") over a channel only that participant listens to; it contains no personal data and is not stored. The host's screen keeps a participant listed for a few minutes after a disconnect (and while a session is paused), in the host's browser only. - Stored in the database, only while the session runs and when the host has task claiming on: the name a participant typed, with the task they claimed and whether they finished it. Deleted when the session ends. - Stored in the database, only when the host has switched on that participants may edit tasks: the text of tasks that participants add or change, as tasks of the session without any name or other identifier of who wrote them. They stay with the session's task list like tasks the Customer wrote. A task a participant deletes is kept for the Customer, who can restore it, and is removed when the session ends. - Counts with no personal data (tasks open and closed per round, participants at a pause, participants signalling Blocked if the host shows it on the projector, the times at which Blocked signals ended, kept for the break celebration without any name or other identifier of who was stuck, and the time at which the session's timer ran out, kept for the closing celebration). - Completion badges, only when the host has switched them on: after the host approves a participant's request, the name shown for the participant on the host's list, the session's name, the host's name, the date and the number of tasks finished are signed by the Provider's server into a badge that is handed to the participant's device. The Provider does not store the name, the badge or a list of badges issued; the request and the approval travel over live channels that contain no name, and checking a badge sends it to the server for a signature check without storing it. - Technical data on the connection (IP address, time, browser) in the logs of the hosting providers. Special categories of data (Art. 9 GDPR) are not intended. The Customer must tell participants not to type more personal data into names or task texts than needed.

Annex 2 Technical and organisational measures

Access control and confidentiality - Hosts have personal accounts that exist only on invitation by the Provider; self-registration is switched off. Passwords are stored only as hashes by the authentication service. - Participants cannot read or write anything without the session's join code. The database enforces this on every request (row-level security); a request without the code returns nothing. Participants can write only the claim of a task and, only while the Customer has switched it on, the text of a task, adding a task and deleting a task, never other columns. - Only the owning host can change a session, its tasks and its announcements; this is also enforced in the database, not only in the interface. - The service key with full access to the database is used only on the server and is never sent to a browser. Access of the Provider's own staff is limited to what operation requires. - Signals go to the host only, on a channel no participant subscribes to. The host's one-word answer to a Blocked signal goes only to the participant concerned, on a channel named for that participant. The projector display receives no participant names, groups or avatars. Transmission and separation - All connections between browsers, the web application and the database are encrypted (HTTPS/TLS). - Each session is a separate set of records tied to the host account; live channels are separate per session code. Data minimisation and deletion - Participant data is kept out of the database by design (Annex 1). Names stored with claimed tasks and announcements are deleted when the session ends, automatically for scheduled sessions too, and for an open-ended session (one without a timer) after 24 hours without activity. - Participants' own devices drop their saved session data when the session is over, or after 12 hours without use. If the Customer sets it (up to 8 days), a device keeps its record for that long instead, so that a reopened session can find the participant again; the record stays on the device and holds no more than the data above plus the identifiers of the tasks the participant finished. - The legal record of announcements (Provider's own data, see § 1) contains nothing about participants. Integrity and availability - Changes to the database structure go through versioned migrations with automated database tests; the code is covered by automated unit and end-to-end tests before it is deployed. - Availability and backups of the database and hosting are provided by the sub-processors in Annex 3 under their own security programmes. Review - The Provider reviews these measures when the service changes and keeps the description of the data flows (docs/participant-data-map.md) up to date.

Annex 3 Sub-processors

Supabase, Inc. — database, authentication and live-connection infrastructure for the Customer's data. Data stored in the AWS region eu-central-1 (Frankfurt, Germany). SOC 2 Type II certified; offers a data processing agreement. Vercel Inc. — hosting and serving the web application, including the server functions that process the Customer's requests. Frankfurt region (eu-central-1). Not sub-processors for this DPA, because they do not receive the Customer's session content or any participant data, and act for the Provider's own purposes described in the privacy policy: Stripe (payments for the Pro plan), Resend (sending the Provider's emails) and Cloudflare (protecting the access-request form).

Contact

For questions about this agreement, please contact: info@feedblick.io