Data processing agreement pursuant to Art. 28 GDPR
Last updated November 17, 2026
This is a convenience translation. The contract language is German; only the German version is binding.
Version 1.0
between
the customer using TSO, as controller within the meaning of the GDPR ("Controller")
and LeadMetrics GmbH, Wienerbergstraße 11–12 (Regus), 1100 Vienna, Austria, FN 583831a, as provider of TSO and processor ("Processor").
This agreement forms part of the Terms of Service of TSO ("Main Agreement") and is concluded together with them at registration or when ordering. It applies to all activities under the Main Agreement in which the Processor, its employees or persons engaged by it process personal data of the Controller. The definitions of the GDPR apply.
1. Subject matter, duration and instructions
(1) The subject matter, nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in Annex 1. If the commissioned service changes, Annex 1 is adjusted.
(2) The Controller is responsible for the lawfulness of the processing, in particular for ensuring that visitors to its websites are informed, that any required consent (for example under § 165(3) TKG 2021, Austrian Telecommunications Act, or Art. 5(3) of the ePrivacy Directive) is obtained and that the transmission to advertising platforms is permitted. The Processor provides settings for this (privacy mode of the project, connection of a consent management platform).
(3) The Processor processes the data only on documented instructions from the Controller, including with regard to a transfer to a third country, unless required to do so by Union or Member State law to which it is subject; in such a case, it informs the Controller of that legal requirement before processing, unless that law prohibits such information (Art. 28(3)(a) GDPR).
(4) The instructions are laid down in this agreement and in the settings the Controller makes in TSO (e.g. which projects, destinations and advertising platforms it sets up, which data is transmitted to which platform, which privacy mode applies). The Controller gives individual instructions in text form.
(5) If the Processor considers that an instruction infringes data protection provisions, it informs the Controller without undue delay. It may suspend execution until the Controller confirms or changes the instruction, and may refuse an obviously unlawful instruction.
(6) This agreement applies for the term of the Main Agreement and beyond, for as long as the Processor processes personal data of the Controller.
2. Technical and organisational measures
(1) The Processor takes the measures pursuant to Art. 32 GDPR that ensure a level of protection appropriate to the risk. The measures implemented at the time the agreement is concluded are described in Annex 2.
(2) The measures evolve with the state of the art. The Processor may change them as long as the level of protection is not reduced; it documents significant changes.
3. Confidentiality and support access
(1) The Processor only uses persons who have committed themselves to confidentiality before starting their work or are under a statutory obligation of confidentiality, and grants them access only to the extent necessary for their tasks. The obligation continues after the end of this agreement and of the employment relationship.
(2) To handle support requests and for troubleshooting, designated employees of the Processor may open TSO as a user of the Controller sees it and in doing so see the data that this user sees. Such access is read-only, lasts no more than one hour per session and is logged with the employee, the user, start and end; the Controller is not notified individually, but receives the log for its users on request. With this agreement, the Controller gives the instruction for this.
4. Assistance and notification of breaches
(1) The Processor assists the Controller by appropriate technical and organisational measures in responding to requests from data subjects under Chapter III GDPR (Art. 28(3)(e)). Where TSO offers functions for this (such as export and deletion of the data of individual persons), the Controller can use them itself; otherwise, the Processor assists on request. [[adjust to the scope of functions of LT-27]] If a data subject contacts the Processor directly, the Processor refers them to the Controller and informs the Controller.
(2) The Processor assists the Controller in ensuring compliance with the obligations pursuant to Art. 32 to 36 GDPR (security, notification of breaches, data protection impact assessment, prior consultation), taking into account the nature of processing and the information available to it (Art. 28(3)(f)). For assistance going beyond the provision of existing documentation, it may request reasonable remuneration, unless the assistance is caused by its own breach of duty.
(3) The Processor notifies the Controller of a personal data breach affecting the Controller's data without undue delay, and no later than 48 hours after becoming aware of it, in text form. The notification contains, to the extent known: the nature of the breach, including the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed and a contact person. Information not yet known is provided in phases.
(4) The Processor takes the measures to secure the data and to mitigate adverse consequences without undue delay and coordinates with the Controller.
(5) If the data is at risk through attachment, seizure, insolvency proceedings or measures by third parties, the Processor informs the Controller without undue delay, unless prohibited by a court or authority, and informs all parties involved that the power of disposal over the data lies with the Controller.
5. Evidence and audits
(1) On request, the Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR, in particular a current version of Annexes 2 and 3 and available certificates and audit reports of its sub-processors.
(2) In addition, it allows for audits, including inspections, by the Controller or by an auditor mandated by the Controller who is bound to confidentiality and is not a competitor of the Processor, with 14 days' prior notice, during normal business hours and without disproportionate disruption of operations (Art. 28(3)(h)). The data centres of the sub-processors are excluded; their evidence applies to them. For on-site inspections, the Processor may request reasonable remuneration.
6. Sub-processors
(1) The Controller approves the sub-processors listed on the sub-processors page (Annex 3) at the time the agreement is concluded and gives its general authorisation to engage additional sub-processors or replace them.
(2) The Processor informs the Controller in text form at least 14 days before any intended addition or replacement (e.g. by email to the account address and on the sub-processors page). Within this period, the Controller can object in text form for an important reason under data protection law. If the parties cannot reach agreement, either party can terminate the Main Agreement and this agreement effective at the time of the change; fees already paid for the time thereafter are refunded pro rata [[coordinate with Polar as merchant of record]].
(3) The Processor imposes on each sub-processor by contract the same data protection obligations as set out in this agreement, in particular sufficient guarantees for appropriate technical and organisational measures (Art. 28(4) GDPR). It is liable to the Controller for the sub-processor's compliance.
(4) Ancillary services without access to personal data of the Controller, such as telecommunications, DNS or the provision of software images, are not sub-processing.
(5) Recipients on the Controller's instructions are not sub-processors: advertising platforms and tools that the Controller connects in TSO and to which it has data transmitted (e.g. Meta, Google, LinkedIn, TikTok, Microsoft, HubSpot, its own webhooks). The legal relationship with them exists between the Controller and the respective provider.
7. Transfers to third countries
Processing outside the European Economic Area takes place only if the conditions of Art. 44 to 49 GDPR are met, in particular on the basis of an adequacy decision (e.g. for the United Kingdom or for companies certified under the EU-US Data Privacy Framework) or of the standard contractual clauses of the EU Commission. The sub-processors page (Annex 3) states the place and basis for each one.
8. Liability
Liability towards data subjects is governed by Art. 82 GDPR. As between the parties, the liability rules of the Main Agreement apply [[have the lawyer check the relationship to the limitation of liability in the Terms of Service]].
9. End of processing: return and deletion
(1) After the end of the Main Agreement (End of Contract under section 9.4 of the Terms of Service), the Controller can still retrieve its data for 30 days through the export functions or the API. After that, the Processor deletes all personal data of the Controller, unless Union or Member State law requires storage (Art. 28(3)(g) GDPR).
(2) Backup copies are overwritten in the course of the regular backup cycles, no later than two months after deletion.
(3) On request, the Processor confirms the deletion in text form.
10. Final provisions
(1) Any right of retention of the Processor in respect of the Controller's data is excluded.
(2) Changes to this agreement require text form. Changes to Annexes 2 and 3 are made under section 2 and section 6 respectively.
(3) In the event of contradictions, this agreement takes precedence over the Main Agreement in matters of data protection.
(4) If a provision is invalid, the remaining provisions remain valid; the invalid provision is replaced by the rule of Art. 28 GDPR.
(5) Austrian law applies. The place of jurisdiction is Vienna. The German version is authoritative; translations are for information only.
Annex 1: Subject matter, data and data subjects
Subject matter and purpose. For the Controller, TSO measures which advertising campaigns lead to visits, enquiries and sales. To this end, the Controller embeds a tracking script on its websites (delivered from in.tso-hub.com [[only mention the Controller's custom tracking domains once they are offered and the edge server has been announced as a sub-processor]]). At the Controller's request, TSO loads the pixels or tags of the advertising platforms in the visitors' browsers, receives leads and conversions from forms, tools and interfaces, attributes them to visits and campaigns, presents them in reports and transmits conversions according to the Controller's settings to advertising platforms (conversion APIs) and other destinations (webhooks).
Nature of the processing. Collection, storage, combination, analysis, display, transmission to recipients chosen by the Controller, deletion.
Types of personal data (depending on the Controller's setup):
- Identifiers: visitor identifier (first-party cookie
lt_vidor local storage; in "Restricted" mode no identifier before consent; in "Cookieless" mode without consent a daily changing identifier generated on the server), identifiers of advertising platforms from the URL and from their cookies (e.g.gclid,fbclid,_fbp,_ttp,li_fat_id,_uetvid) - Technical data: IP address and user agent (stored for 60 days), and derived from them approximate location (country, region, city), device type, browser, language
- Usage data: pages viewed, referrer, campaign parameters (UTM), times, clicks and events on the website, consent status
- Contact and lead data: name, email address, phone number, company, address (street, city, state, postal code, country), date of birth, gender, answers in forms and other fields that the Controller transmits
- Conversion data: type, time, value and currency of conversions, order or transaction numbers, status of leads
- For advertising platforms, to the extent the Controller has set up the transmission: hashed (SHA-256) contact data (email address, phone number, first and last name, date of birth, gender, city, state, postal code), IP address and user agent, click identifiers and cookies of the platforms
Special categories pursuant to Art. 9 GDPR are not the subject of the processing; the Controller does not transmit any such data [[regulate separately for customers from the health sector, see "health data advertiser mode" in the backlog]].
Categories of data subjects: visitors to the Controller's websites, its prospects (leads) and customers. The Processor processes the accounts of the Controller's users in TSO as a controller in its own right (privacy policy).
Annex 2: Technical and organisational measures
1. Confidentiality
- Physical access: The systems run exclusively in data centres of the sub-processor Civo in Frankfurt am Main (Annex 3) with its physical safeguards; Civo has itself audited annually by third parties and provides its certificates on request. The Processor does not operate its own servers on office premises.
- System access: Administrative access to cloud accounts, cluster and database only for designated persons, with strong passwords and two-factor authentication [[confirm for all accounts]]. The Kubernetes API is reachable only from specified IP addresses, the database only from the cluster's private network, not from the internet.
- Data access: Role and permission concept in the application (workspace, project, roles). The tracking data ingest, the API and the app connect with a database role that may only read and write data but not change the schema; migrations and the background service run with the owner role [[adjust after LT-430]]. Support access to customer accounts is read-only, time-limited and logged. Access credentials for advertising platforms are stored encrypted.
- Separation: Tenant separation in the application by workspace and project; separate test and production environments in separate accounts, networks and databases; no production data in the test system.
- Pseudonymisation: IP addresses and user agents are deleted after 60 days; without consent in "Cookieless" mode, no persistent visitor identifier; contact data is hashed before transmission to advertising platforms.
2. Integrity
- Transmission control: Connections from the internet, to advertising platforms and to the database are encrypted with TLS (certificates from Let's Encrypt); within the cluster, connections run in a private network, restricted by network rules. Transmissions to third parties only to the destinations set up by the Controller.
- Input control: Changes to configuration and deployment are traceable (version control, logged deployments with approval); support sessions are logged. [[add logging of administrative access after LT-424]]
3. Availability and resilience
- Daily backup of the database and restore to any point in time within the retention window (point-in-time restore); the restore has been tested. [[add off-site backup after LT-440]]
- The tracking data ingest runs redundantly on separate servers behind a load balancer; maintenance is carried out without downtime of this ingest.
- Database changes are run separately before each deployment; if one fails, nothing is deployed.
- [[add monitoring and alerting after LT-424]]
4. Procedures for regular review
- Data protection management: record of processing activities, documented procedures for data subject requests and data breaches [[create or confirm]]
- Code reviews before every change, automated tests, regular updates of dependencies
- Careful selection and monitoring of sub-processors
- Control of processing on instructions: processing only under this agreement and the Controller's settings
Annex 3: Sub-processors
The list on the Sub-processors page in the version valid at the time the agreement is concluded is authoritative; changes under section 6.