Data Processing Agreement (DPA)

Diese Seite auf Deutsch

Version 1.0, November 2026

Data Processing Agreement pursuant to Art. 28 GDPR

This Data Processing Agreement ("DPA") forms an integral part of the Terms & Conditions ("Agreement") between TechnologyCircle GmbH and the Customer and governs the processing of personal data by TechnologyCircle GmbH in connection with the Loopthink service.


Processor

TechnologyCircle GmbH
Karolinenstraße 24, Haus 4
20357 Hamburg, Germany
Operator of: Loopthink
Represented by: Henrik Lippke, Managing Director
E-mail: info{at}technologycircle{dot}io


Controller

The Customer, the natural or legal person who registers for the Service and accepts the Agreement. The Customer acts as controller (or itself as processor on behalf of a third-party controller) for the personal data processed via the Service.


Conclusion and Form

This DPA is concluded upon the Customer's acceptance of the Agreement when registering for the Service. No signature is required; it is concluded in electronic form pursuant to Art. 28(9) GDPR.


Section I, General

Clause 1, Purpose and Scope

This DPA ensures that the processing of personal data on behalf of the Controller by the Processor is carried out in accordance with Article 28(3) and (4) GDPR.


Clause 2, Non-alterability

The DPA may only be amended to supplement the annexes, without altering fundamental provisions.


Clause 3, Interpretation

Terms are interpreted in accordance with the GDPR.


Clause 4, Precedence

In the event of a conflict regarding data protection, the provisions of this DPA shall prevail. In all other respects, the Agreement governs.


Section II, Obligations of the Parties

Clause 5, Description of Processing

The subject matter, nature, purpose, data categories and duration of the processing are set out in Annex II.


Clause 6, Obligations of the Processor

6.1 Instructions: Processing shall only be carried out based on documented instructions from the Controller. The Controller's documented instructions are set out in this DPA, the Agreement, and the Customer's configuration and use of the Service (which systems are connected, which tools are published, which member groups may use them, which masking rules apply, and whether changes are allowed); the Customer's use of the Service constitutes such instruction. This includes instructions regarding transfers to a third country, unless the Processor is required to transfer by Union or Member State law.

6.2 Purpose limitation: Processing only for the purposes listed in Annex II.

6.3 Duration: As defined in Annex II.

6.4 Confidentiality: The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. The Processor treats all personal data and non-public information of the Controller as confidential and uses it solely to provide the Service.

6.5 Security of Processing (Art. 32 GDPR): The Processor implements appropriate technical and organisational measures as specified in Annex III. The parties periodically review and update these measures to reflect the current state of the art.

6.6 Sensitive data: See the data restriction in Annex II.

6.7 Accountability: Both parties shall provide each other with all information necessary to demonstrate compliance with Art. 28 GDPR.

6.8 Sub-processors: The Controller grants a general written authorisation for the engagement of sub-processors. The current list of sub-processors is available at loopthink.ai/subprocessors. The Processor shall inform the Controller of any intended addition or replacement of sub-processors, giving the Controller the opportunity to object. The Processor imposes the same data protection obligations on each sub-processor (Art. 28(4) GDPR).

6.9 International Data Transfers: The platform is currently hosted exclusively in the AWS European Sovereign Cloud in Germany; hosting involves no transfer to a third country. Where a sub-processor listed in Annex IV processes personal data outside the European Union, this is stated there together with the transfer mechanism.

6.10 Audit and Inspections: The Processor shall make available all information necessary to demonstrate compliance with Art. 28 GDPR and allow for and contribute to audits, including inspections, by the Controller or a mandated auditor. Audits shall take place during regular business hours, following reasonable prior notice (at least 14 days), and shall not unreasonably interfere with the Processor's operations.


Clause 7, Assistance to the Controller

The Processor shall assist the Controller in handling data subject requests and in conducting data protection impact assessments, taking into account the nature of the processing and the information available to the Processor.


Clause 8, Notification of Data Breaches

The Processor shall notify the Controller of any personal data breach without undue delay, and in any event within 48 hours after becoming aware of it. The notification shall include the information required by Art. 33(3) GDPR to enable the Controller's reporting obligation.


Section III, Final Provisions

Clause 9, Termination

Upon termination of the Agreement, the Processor shall, at the choice of the Controller, delete or return all personal data, and confirm deletion in writing upon request. Deleting a workspace removes its connections and their stored credentials with immediate effect. Audit records are deleted automatically after the retention period stated in Annex II, or earlier on request.


Annex I, List of Parties

Parties

Processor: TechnologyCircle GmbH, Henrik Lippke (Managing Director), info{at}technologycircle{dot}io

Controller: The Customer, as identified by the account and registration data provided to the Service.


Annex II, Description of Processing

Categories of Data Subjects

The Controller's users of the Service (members of a workspace) and any individuals whose data is contained in the systems the Controller connects, for example its customers, contacts or employees.


Categories of Data

Content data: Whatever a connected system returns in answer to a tool call, and the values an AI assistant fills into a tool call (for example a customer number, a date range or a search term). The Service is content-agnostic: which personal data this is depends on the systems the Controller connects.

Account data: E-mail address, name, and the workspaces and member groups a user belongs to.

Audit and usage data: One audit record per tool call (who asked, which workspace and server, the tool, the statement sent to the connected system, which fields were masked or refused, whether the call succeeded, and for a change what was changed), and usage counters without request content.

Connection credentials: The access data of each connection, stored encrypted.


Data Restriction

The Controller shall not use the Service for special categories of personal data (Art. 9 GDPR) or data relating to criminal convictions (Art. 10 GDPR), unless this has been agreed separately in writing. The Processor is not required to monitor content; responsibility for which systems are connected and which data can be reached through them rests with the Controller.


Nature of Processing

  • Receiving tool calls from the AI assistant the Controller connected and forwarding them to the connected system
  • Checking the caller's permission and applying the masking rules the Controller configured
  • Returning the result to the AI assistant; no copy of the result is kept
  • Where the Controller allowed changes for a connection: forwarding the change to the connected system
  • Writing audit records and usage counters
  • Storing connection credentials in encrypted form

The Processor has no routine access to content data. Access is limited to automated system-level monitoring and to troubleshooting by authorised personnel, subject to the confidentiality obligations in Clause 6.4. No data mining, no profiling, no use for training models.


Purposes

Giving the Controller's AI assistants governed access to the Controller's own systems: access control per member group, data masking, and an audit record of every call.


Duration

For the duration of the contractual relationship. Audit records are deleted automatically 24 months after the request they describe, usage counters after 400 days. Credentials are deleted when the connection is removed.


Annex III, Technical and Organisational Measures (TOMs)

Measures

  • Hosting of the platform in the AWS European Sovereign Cloud, in Germany
  • Encryption in transit (TLS)
  • Connection credentials encrypted with a managed key before they are written; never returned by the API
  • Encryption of stored data at rest
  • Access to tools per member group, decided by the Controller's administrators
  • Data masking applied on the platform before a result reaches the AI assistant
  • Append-only audit records: the platform's own permissions allow them to be written and read, not changed or removed
  • Role-based access to the infrastructure (IAM), restricted to authorised personnel
  • Logging of security-relevant activities
  • Data minimisation: no copy of tool results is stored


Annex IV, List of Sub-Processors

Sub-Processors

The current list is maintained at loopthink.ai/subprocessors.

This DPA is concluded electronically in accordance with Art. 28(9) GDPR and requires no signature.

Version 1.0, November 2026