Data Processing Agreement (DPA) pursuant to Art. 28 GDPR
This is a translation. Only the German version is legally binding. The downloadable PDF is in German.
Download the data processing agreement as a PDF · Version 1.1, as of 15.11.2026
Telesherpa GmbH · Version 1.1 · as of 15.11.2026 · https://www.telesherpa.com/de/avv
This DPA is part of the General Terms and Conditions (Terms) of Telesherpa GmbH and applies to all processing of personal data that Telesherpa carries out on behalf of the customer. Acceptance of the Terms at registration (on the web or via an agent account with accept_terms) also constitutes acceptance of this DPA; Telesherpa records the version, time, account and method of acceptance (Art. 28(9) GDPR). Earlier versions are available at https://www.telesherpa.com/de/avv.
Contracting parties
Controller: the customer within the meaning of the Terms, including the operator of an agent account pursuant to Section 4 of the Terms (hereinafter the "Customer"). The customer is an entrepreneur, a public authority, an association or a comparable organisation; purely private use is not the subject of this DPA.
Processor: Telesherpa GmbH, Barbaraweg 8, 53125 Bonn, Amtsgericht Bonn HRB 31107, represented by its management (hereinafter "Telesherpa").
§ 1 Subject matter and duration
1. Subject matter. Telesherpa provides the customer with the Telesherpa ontology platform as a software-as-a-service offering: web application (app.telesherpa.com), progressive web app, native apps for iOS and Android, programming interfaces and MCP server (mcp.telesherpa.com). With it the customer records, links and evaluates business objects itself, through its users and through AI agents operated by it, such as locations, buildings, assets, vehicles, persons, orders and inspections. In doing so, Telesherpa processes personal data on behalf of the customer (§ 2).
2. Duration. This DPA applies for the term of the usage relationship under the Terms and beyond that for as long as Telesherpa processes personal data of the customer, in particular until erasure or return has been completed in accordance with § 12.
3. Delimitation. Processing carried out by Telesherpa under its own responsibility is not the subject of this DPA: administration of the customer account as contracting party, billing of credits including payment processing, content-free technical usage and billing metrics, defence against misuse pursuant to Sections 5 and 9 of the Terms, fulfilment of statutory obligations and the operation of the website www.telesherpa.com. Telesherpa's privacy policy provides information on this.
§ 2 Nature and purpose of the processing, categories of data, data subjects, location
1. Nature of the processing: collection, recording, storage, organisation, structuring, linking, retrieval, querying, evaluation, use, transmission to users, agents and recipients authorised by the customer, restriction, erasure and destruction, in each case via the platform.
2. Purpose: provision, operation, backup, maintenance and troubleshooting of the platform for the customer, in particular:
storage and management of objects, properties, links, files, images, comments and time series in the customer's data areas (scopes);
forms and form responses including photos, documents and signatures, generation of PDF documents;
orders (ServiceOrders) to employees, QR scan and checkpoint workflows, notifications in the platform, by email and by push;
automation via rules and functions, reports and evaluations (CSV, JSON, map data), geocoding of addresses and coordinates;
provision of data to the customer's AI agents via the MCP server within the rights granted by the customer;
data imports and service requests of the customer, for example to supplement object types;
invitations and member management (invitation codes, allowlists);
on the customer's express instruction: release of data areas as public (PUBLIC).
3. Categories of personal data (depending on the customer's configuration):
| Category | Examples |
|---|---|
| Account and identity data | email address or user name, password (only as a hash), profile details, language, roles, scope memberships and rights; for agent accounts the generated address agent-<hex>@agents.telesherpa.com |
| Authentication and session data | access and refresh tokens, MCP session IDs, passkey data, OAuth client registrations, user agent, IP addresses |
| Log data | change and action logs including payload, timestamps, executing account (human or agent) |
| Content data in objects | names, contact details, addresses, functions of persons; customer, tenant or member references created by the customer; comments; free text |
| Location and movement data | addresses, geo-coordinates, time series (e.g. vehicle routes), scan times at checkpoints together with the person performing them |
| Image, document and signature data | photos (including those showing persons), uploaded documents, electronic signatures, generated PDFs |
| Work and deployment data | orders, assignments, processing status, duty rosters, timesheets, inspection records |
| Communication data | notifications, push subscriptions, email addresses in invitations and allowlists |
| Special categories (Art. 9 GDPR) | Excluded. Health data and other special categories of personal data are not the subject of this DPA. The customer undertakes not to introduce such data into the platform and to require the same of its users and agents (§ 5(3)). |
4. Data subjects: employees and other users of the customer (including field staff); operators of agent accounts; customers, tenants, members, guests and visitors of the customer; contacts of suppliers, service providers and partners; other persons recorded by the customer in objects, photos or documents; invited persons.
5. Place of processing. The platform and the customer's data are operated and stored exclusively in the data centre of OVH GmbH at the Limburg site in Germany, including the data backups (Annex 2 Part A). No mirroring to other sites currently takes place. Note: Because production data and data backups are located at the same site, severe damage at this site (e.g. fire) can lead to the loss of data including the backups. Deviations arise only from the services designated in Annex 2 Part B as third-country services, in particular a possible remote access by companies of the OVH group in Canada and the United Kingdom for security and maintenance purposes, as well as email delivery via Apple (Annex 2 Part B No. 2). If the customer uses geocoding, Telesherpa transmits address details to Google as an independent controller on the customer's instruction (§ 7(5), Annex 2 Part D). Push notifications are delivered end-to-end encrypted via the browsers' push services (Annex 2 Part C). Telesherpa decides on further locations in the EU or the EEA in accordance with § 6(6).
§ 3 Instructions
1. Telesherpa processes personal data only on the documented instruction of the customer, including for transfers to a third country, unless Telesherpa is obliged to do so under Union or Member State law (Art. 28(3) subparagraph 1 point (a) GDPR). In that case Telesherpa shall inform the customer of those legal requirements before the processing, unless the law prohibits this on important grounds of public interest.
2. Authorities. Telesherpa transfers personal data of the customer to authorities only to the extent that Telesherpa is obliged to do so under Union or Member State law; paragraph 1 sentence 2 applies. Voluntary reports pursuant to Section 9 of the Terms are limited to data for which Telesherpa is itself responsible. Telesherpa answers requests from authorities in third countries only in accordance with Art. 48 GDPR.
3. What counts as an instruction. Instructions are this DPA, the Terms and the customer's configuration of the platform. All actions that the customer, its users or its agents carry out via the web application, the apps, the API or the MCP server, such as creating, changing, releasing, exporting or deleting, as well as service requests in text form (ontouser_service_request or email to service@telesherpa.com), also count as instructions.
4. Customer's agents. Telesherpa attributes actions of an agent account to the customer as operator (Section 4 of the Terms). The customer is responsible for ensuring that the configuration and control of its agents are compatible with data protection law.
5. Declarations and instructions via agents. Telesherpa is a platform that is used primarily by AI agents. The following therefore applies to declarations and instructions:
a) Acceptance. The customer may accept this DPA via its agent account (e.g. with accept_terms). The agent thereby transmits the operator's declaration as its messenger; if it formulates the declaration itself, it acts as a tool deployed by the operator, whose declarations the operator holds good against itself (Section 4 of the Terms). The operator remains the controller within the meaning of the GDPR.
b) Instructions. Instructions given by an account authorised by the customer, including an agent account, via the web application, the apps, the API, the MCP server or a service request count as documented instructions of the customer within the meaning of Art. 28(3) subparagraph 1 point (a) GDPR. This also applies to far-reaching instructions: erasure of entire scopes or accounts, publication (PUBLIC) and return of the data pursuant to § 12. Telesherpa logs every instruction with the account and the time (§ 8(5)). Before a far-reaching instruction, Telesherpa may require confirmation through the same account.
c) Operator's responsibility. The operator is responsible for its agent's declarations and instructions as if it had made them itself, even if the agent acted autonomously or as a result of manipulated input (§ 5(4)).
d) Contact point. Notices from Telesherpa under this DPA (in particular §§ 6, 9, 10 and 15) are sent to the contact details that the operator has provided pursuant to Section 4 of the Terms and additionally to the account's platform mailbox (hereinafter the "Contact Point"); they are deemed received upon arrival. The customer may additionally name a natural person as contact (Annex 3); this is not required.
6. Instructions contrary to data protection law. If Telesherpa considers an instruction to be contrary to data protection law, Telesherpa shall inform the customer without delay (Art. 28(3) subparagraph 2 GDPR) and may suspend execution until the customer confirms or amends it.
§ 4 Obligations of Telesherpa, confidentiality
1. Telesherpa processes the data exclusively for the purposes set out in § 2, does not use them for its own purposes and does not pass them on to third parties, except under this DPA or on the customer's instruction. In particular, Telesherpa does not use the customer's personal data for product development, tests, experiments, benchmarks or statistics for its own purposes. Permitted are only content-free technical usage and billing metrics under its own responsibility (§ 1(3)). Telesherpa ensures that persons under its authority as well as automated systems and AI agents operated by it process the customer's data only on instruction (Art. 29 GDPR).
2. Confidentiality. Telesherpa uses only persons who are bound to confidentiality or subject to a statutory duty of secrecy (Art. 28(3) subparagraph 1 point (b) GDPR) and familiarises them with the data protection provisions. The obligation continues beyond the end of the activity.
3. Professional secrets. Telesherpa does not assume any obligation as a cooperating person pursuant to § 203(3) and (4) StGB. If the customer is subject to a duty of confidentiality pursuant to § 203 StGB, it shall not introduce any data that is subject to this professional secret.
4. Own AI agents. § 8(4) applies to AI agents that Telesherpa uses for development, operation, security testing or support.
5. Data protection contact. The contact for data protection is the management (adg@telesherpa.com). Telesherpa has not appointed a data protection officer; the managing director does not take on this function because of the conflict of interest under Art. 38(6) GDPR. If a data protection officer is appointed, Telesherpa will give notice of this and supplement Annex 3.
6. Telesherpa maintains a record of processing activities carried out on behalf (Art. 30(2) GDPR).
7. Telesherpa cooperates with the supervisory authority on request and informs the customer without delay about inspections and measures of the supervisory authority, insofar as they concern this DPA.
§ 5 Technical and organisational measures (Art. 32 GDPR)
1. Telesherpa takes the measures described in Annex 1. They take into account the state of the art, the cost of implementation, the nature, scope, circumstances and purposes of the processing as well as the risk to the rights and freedoms of data subjects.
2. Telesherpa may develop the measures further, provided that the level of protection does not decrease. Telesherpa shall notify the customer of substantial changes in text form; Annex 1 is published with its version status at https://www.telesherpa.com/de/avv.
3. Customer's responsibility. The customer is responsible for granting rights in its scopes, for the secure storage of the access data and tokens of its users and agents (not in plain text in shared directories), for selecting and configuring its AI models and agents, and for deciding to make data public. Rights are granted per scope, not per object; a write right applies to all objects of a scope. The customer arranges its data across scopes in such a way that this satisfies its protection requirements.
4. Notes on agents. Agents can be induced to take unwanted actions through manipulated input (prompt injection). Telesherpa recommends giving agents only the rights they need (e.g. read only), using separate scopes for sensitive data and having destructive actions confirmed by a human.
§ 6 Sub-processors
1. Approval. The customer grants general approval for the use of further processors (Art. 28(2) GDPR). On conclusion of the contract, the sub-processors listed in Annex 2 Part B count as approved.
2. Contractual binding. Telesherpa imposes on every sub-processor by contract the same data protection obligations as are laid down in this DPA, in particular sufficient guarantees for appropriate technical and organisational measures (Art. 28(4) GDPR). Telesherpa is liable to the customer for the performance of its sub-processors' obligations.
3. Changes. Telesherpa informs the customer at least 30 days before the deployment of a new sub-processor or the replacement of an existing one by email to the Contact Point pursuant to § 3(5)(d) and by updating the list at https://www.telesherpa.com/de/avv with a change history. The information states the name, address, service, place of processing and any third-country involvement.
4. Objection. The customer may object in text form within 14 days of receipt on substantiated data protection grounds. Telesherpa shall then endeavour to find a reasonable alternative. If there is none, either party may terminate the contract as of the time of the change; Telesherpa refunds unused, prepaid credits on a pro rata basis. Section 7 sentences 2 and 3 of the Terms do not apply in this respect.
5. Emergency. If a sub-processor fails or a security incident occurs, Telesherpa may temporarily use an equivalent replacement with registered office and processing in the EU or the EEA. Telesherpa shall inform the customer without delay; the customer may object within 14 days in accordance with paragraph 4.
6. Future locations. Telesherpa decides on further data centre locations; the customer has no choice of location. The following applies:
a) Further locations are situated exclusively in the EU or the EEA. The customer's data and data backups are never stored outside the EU or the EEA.
b) Telesherpa announces the addition of a further location at least 30 days in advance in accordance with paragraph 3 and updates Annex 2.
c) New location of the same sub-processor: notification in accordance with paragraph 3. New provider: procedure in accordance with paragraphs 3 and 4.
7. Ancillary services of third parties without access to the customer's personal data, such as telecommunications or domain registration, do not constitute sub-processing.
§ 7 Transfers to third countries
1. Telesherpa processes the customer's data exclusively at the locations listed in Annex 2 Part A in Germany and does not transfer them to third countries outside the EU and the EEA, except for the services designated in Annex 2 Part B as third-country with the guarantee stated there. This concerns in particular a possible remote access by OVH Hebergement INC (Canada) and OVH Limited (United Kingdom) for security and maintenance; an adequacy decision of the European Commission exists for both countries (Art. 45 GDPR). The data remain stored at the Limburg site and are encrypted there by Telesherpa itself (Annex 1). It also concerns the content of emails sent via Apple (Annex 2 Part B No. 2); guarantee EU-U.S. Data Privacy Framework or standard contractual clauses. On geocoding see paragraph 5. For push notifications, Annex 2 Part C applies: the browsers' push services receive only encrypted content.
2. What is decisive for a third-country transfer is where the data are processed, in particular where an AI model is executed, not where the developers or publishers of the model are based. An AI model that runs on Telesherpa's own hardware in Germany without a connection to an external model provider does not result in a third-country transfer.
3. A transfer to a third country by Telesherpa or a sub-processor is permissible only if the requirements of Art. 44 et seq. GDPR are met (e.g. adequacy decision including the EU-U.S. Data Privacy Framework, standard contractual clauses with a transfer impact assessment). For the cases designated in Annex 2 Part B, the customer agrees upon conclusion of this DPA.
4. Transfers to AI agents and AI models that the customer connects take place on the customer's instruction (§ 8(2)). Whether this involves a third-country transfer and how it is safeguarded is the customer's responsibility.
5. Geocoding via Google. The geocoding of addresses via the Google Maps Geocoding API (onto_object_geocode; alternatively Nominatim/OpenStreetMap if Google returns no result) is an integral part of the service.
a) Customer's instruction. By using the platform and entering addresses, the customer instructs Telesherpa to transmit the address data to Google for geocoding. Only the address string or the coordinates of the object are transmitted, no names or other object data.
b) Independent controller. Google does not act as a sub-processor of Telesherpa but as an independent controller under the Google Controller-Controller Data Protection Terms (Annex 2 Part D). Google processes the data in the USA; the basis for the transfer is the EU-U.S. Data Privacy Framework, under which Google LLC is certified.
c) Information of the data subjects. The customer is obliged to inform the data subjects whose addresses it enters into the platform about the transfer to Google as an independent controller and the processing in the USA (Art. 13, 14 GDPR).
§ 8 Special provisions for AI agents and AI models
1. No training on customer data. Telesherpa does not use the customer's personal data or other content for the training, fine-tuning or other improvement of AI models, neither its own nor those of third parties, unless the customer has separately and expressly consented in text form. Content-free metrics pursuant to § 4(1) remain permitted.
2. Customer's agents and AI models ("bring your own model"). The customer works with its own AI agents and AI models, which it selects, connects and operates itself.
a) Customer's responsibility. These agents and models are the customer's responsibility. Depending on the arrangement, their providers are the customer's processors or independently responsible, and in no case sub-processors of Telesherpa. The customer is responsible for the legal basis, the contract with the provider including its own DPA, and the safeguarding of any third-country transfers pursuant to Art. 44 et seq. GDPR.
b) No influence. Telesherpa does not select these agents and models, does not configure them and does not monitor their processing outside the platform. The rights of Telesherpa under Sections 4, 5 and 9 of the Terms remain unaffected.
c) Role of Telesherpa. Telesherpa processes the data that the customer's agent sends to the platform or retrieves there within the rights of the agent account and transmits responses to the agent (transport and provision). This takes place on the customer's instruction; retrieval by an agent account authorised by the customer counts as an instruction (§ 3(3), (4)). This DPA applies to this part.
d) The platform itself does not call up any AI model for the processing of customer data.
3. Agents only within the rights granted. An agent account receives access exclusively to the scopes and rights (read, write, manage) that the customer or an authorised user has granted it via memberships or invitation codes. Without an assignment there is no access. A self-registered agent account without an invitation is isolated from third-party data. Reading and writing are separate rights; the check takes place on the server side. Telesherpa does not extend an agent's rights without the customer's instruction.
4. Telesherpa's own AI agents. Telesherpa uses its own internal AI agents for development, operation, security testing and support. They and their models are not part of the service for the customer.
a) Principle: no access. Internal AI agents have no access to the customer's personal data. Telesherpa ensures this technically: agents for code reviews and concept reviews have no accounts and no access to Telesherpa systems and work only with the material that a human presents to them. The development agent has no technical access to customer data, in particular no membership in the customer's scopes, no administrative role and no access data for production systems, databases, data backups, production logs or the customer's service requests; it works with program code, configuration and synthetic test data, does not transfer personal data to the provider of its model, and changes to the production platform are only deployed after approval by the management. The only administrator of the production platform is a human (Annex 1).
b) No exception. No internal agent receives access to the customer's personal data, not even in an individual case. This applies in particular to agents whose AI model is executed outside the EU or the EEA, for example via the model API of an external provider.
c) Consequence. The providers of the models of internal agents are not sub-processors, because these agents have no technical access to customer data pursuant to points (a) and (b). If the customer's personal data nevertheless reach such an agent or its model provider contrary to points (a) and (b), Telesherpa treats this as a breach pursuant to § 10.
5. Transparency and logs. Actions of agents and humans are recorded in the change and action log. On request, the customer receives a machine-readable extract of the log of its scopes within 5 working days. Logs including payload are retained for 12 months; only named administrators of Telesherpa have access, and access to logs is logged. The platform does not store chains of thought or conclusions of the customer's model.
6. Automated decisions, AI regulation. If the customer uses agents or rules for decisions with legal or similarly significant effect (Art. 22 GDPR), it is responsible for their permissibility and for human review. Telesherpa provides the customer on request with information about the AI systems it operates itself, insofar as the customer needs it for its own obligations under Regulation (EU) 2024/1689.
7. Public data areas (marketplace). If the customer makes a data area public (PUBLIC), other users receive read access. This is a disclosure on the customer's instruction and under the customer's responsibility. Public data areas must not contain personal data unless the customer has a legal basis for this and documents it when releasing the data area.
8. Third-party agents. If Telesherpa operates or brokers third-party agents as part of the service, their provider is included in Annex 2 Part B beforehand in accordance with § 6. Marketplace providers are contractually obliged not to use data from the customer's scopes for their own purposes.
§ 9 Support with data subject rights
1. Telesherpa supports the customer with appropriate technical and organisational measures in dealing with requests from data subjects under Chapter III GDPR (Art. 28(3) subparagraph 1 point (e) GDPR). The customer can itself fulfil many requests via the platform (search, export as CSV/JSON, changing or deleting objects and properties, removing members).
2. Anything the customer cannot do itself, in particular the deletion of entire scopes or accounts or a log extract, Telesherpa carries out on instruction within 5 working days.
3. If a data subject contacts Telesherpa directly, Telesherpa forwards the request without delay to the Contact Point pursuant to § 3(5)(d), insofar as it can be attributed, and does not answer it itself, except on instruction.
4. Support beyond the platform functions is free of charge as long as it remains within the usual scope. Telesherpa may charge extraordinary effort at reasonable rates after prior notice, unless it is based on a breach by Telesherpa.
§ 10 Notification of data breaches
1. Telesherpa shall notify the customer of a personal data breach (Art. 4 No. 12 GDPR) affecting the customer's data without delay, at the latest 24 hours, after Telesherpa has become aware of the breach or has a substantiated suspicion. The notification is sent to the Contact Point pursuant to § 3(5)(d).
2. The notification contains, insofar as known: the nature of the breach, the categories and approximate number of data subjects and records concerned, the probable consequences, measures taken or proposed and a contact person. Telesherpa supplements missing information step by step.
3. Telesherpa takes measures without delay to contain and remedy the breach, supports the customer in its obligations under Art. 33 and 34 GDPR and provides the information for the documentation pursuant to Art. 33(5) GDPR. Notifications to supervisory authorities or data subjects in the name of the customer are made only on instruction.
4. Telesherpa also informs the customer about serious operational disruptions and other irregularities in the processing of its data.
5. The reporting and incident processes of Telesherpa are also aligned with the reporting obligations of Regulation (EU) 2024/2847 (Cyber Resilience Act); reports under this Regulation are made via the Single Reporting Platform (SRP). The notification to the customer pursuant to paragraph 1 remains unaffected.
§ 11 Further support obligations
Telesherpa supports the customer, taking into account the nature of the processing and the information available, with the obligations arising from Art. 32 to 36 GDPR (security, data protection impact assessment, prior consultation), in particular by providing Annex 1 and Annex 2. § 9(4) applies accordingly.
§ 12 Erasure and return
1. During the term the customer may export data itself at any time (reports as CSV/JSON, files) and delete it. Telesherpa deletes accounts and entire scopes on instruction pursuant to § 9(2). Data marked as deleted are finally removed after no more than 30 days.
2. After the end of the contract Telesherpa shall, at the customer's choice, delete all personal data of the customer or return it and thereafter delete the copies present, unless an obligation to store it exists under Union or Member State law (Art. 28(3) subparagraph 1 point (g) GDPR). Return takes place as an export in common, machine-readable formats (CSV/JSON and original files). The customer communicates its choice within 30 days after the end of the contract; without a choice, Telesherpa deletes after expiry of this period.
3. Periods. Erasure in the production system takes place within 30 days after expiry of the period or the instruction. Data backups are overwritten after no more than 35 days; until then they are protected against access and are not used for other purposes.
4. In the event of account deletion, payloads containing content data are removed from the logs; content-free metadata (time, action, account) remain until expiry of the period pursuant to § 8(5).
5. Telesherpa confirms the erasure on request in text form.
6. Documentation serving as evidence of proper processing, as well as data that Telesherpa must retain on the basis of statutory obligations, may be retained by Telesherpa beyond the end of the contract for the duration of the respective obligation or until expiry of the limitation period.
7. Public scopes. At the end of the contract, scopes made public by the customer are withdrawn; bookings by other users end at that point.
§ 13 Evidence and audit rights
1. Telesherpa provides the customer on request with all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR and this DPA.
2. Evidence consists in particular of: the self-declaration pursuant to Annex 1, test reports or certificates of the data centre operator and results of penetration tests, insofar as available, as well as approved codes of conduct or certifications (Art. 40, 42 GDPR).
3. Inspections. The customer, or an auditor commissioned by it and bound to confidentiality who is not a competitor of Telesherpa, may carry out inspections (Art. 28(3) subparagraph 1 point (h) GDPR). They cover all places of processing pursuant to Annex 2 Part A. Inspections are announced with a notice period of at least 14 days, take place during business hours without disrupting operations, and regularly no more than once per calendar year; occasion-related audits, for example after a data breach, are possible at any time.
4. Audits at the data centre operator are governed by its terms; Telesherpa passes on its evidence. If this is insufficient, the customer may require an audit by an independent auditor.
5. Each party bears its own costs. For additional audits beyond one per year that are not occasion-related, Telesherpa may charge reasonable effort.
§ 14 Liability
1. Art. 82 GDPR applies to liability towards data subjects. Internally, compensation takes place in accordance with Art. 82(5) GDPR in proportion to the respective share of responsibility.
2. Unlimited liability. Telesherpa is liable without limitation for intent and gross negligence, for injury to life, body or health, under the Product Liability Act, to the extent of a guarantee assumed, and towards data subjects under Art. 82 GDPR. This liability is not limited by paragraph 3.
3. Maximum liability amount. In all other respects, Telesherpa is liable for simple negligence only for the breach of material contractual obligations; the obligations under this DPA are material contractual obligations within the meaning of Section 10 of the Terms. Liability is then limited to the typical, foreseeable damage, but in total at most to the sum of all remuneration that the customer actually paid to Telesherpa in the three months before the event giving rise to the damage (rolling; including purchased credits and usage-based fees). The relevant period is from the same calendar day three months before the event up to the day before the event. Several instances of damage from the same event count as one claim. In all other respects, liability for simple negligence is excluded.
4. Each party indemnifies the other against claims by third parties insofar as these are based on a breach of this DPA or of data protection law for which it is responsible. For the customer this applies in particular if the customer, its users or its agents introduce personal data, have it processed or make it public without a legal basis.
§ 15 Final provisions
1. Order of precedence in data protection matters: individually agreed data protection provisions (including a DPA provided by the customer and accepted by Telesherpa), then this DPA, then the Terms.
2. Changes. Telesherpa may amend this DPA unilaterally only insofar as a changed legal situation or an official requirement makes this necessary or the level of protection for the customer does not decrease; Telesherpa shall give notice of such changes at least 30 days in advance in text form. Other changes require the customer's consent in text form. If the customer objects to a unilateral change, it may terminate the contract with effect from the change taking effect; § 6(4) sentence 3 applies accordingly. Changes to Annexes 1 and 2 are governed by § 5(2) and § 6.
3. Versions. Telesherpa keeps every version of this DPA with its date available at https://www.telesherpa.com/de/avv.
4. If a provision is invalid, the validity of the remaining provisions remains unaffected. The statutory provision takes its place, in particular Art. 28 GDPR.
5. The law of the Federal Republic of Germany applies. Place of jurisdiction in accordance with Section 13 of the Terms.
6. If the customer's data at Telesherpa are endangered by attachment, seizure, insolvency proceedings or other measures of third parties, Telesherpa shall inform the customer without delay and point out to the third parties that the power of disposal over the data lies with the customer.
Annex 1: Technical and organisational measures (Art. 32 GDPR)
Version 1.1, as of 15.11.2026.
1. Confidentiality
| Measure | Description |
|---|---|
| Access to the data centre | Data centre of OVH GmbH at the Limburg site (Annex 2 Part B No. 1); physical protection according to the measures and certifications of OVH GmbH (according to its DPA, among others ISO 27001, ISO 27017, ISO 27018, ISO 27701) |
| User access | accounts with password, optional passkey; activation by email code or invitation code; bearer token 10 h, refresh token 30 days with rotation and replay protection; MCP session expires after 12 h of inactivity; web session 30 min |
| Interface access | OAuth 2.1 with authorization code and PKCE (S256), dynamic client registration; without a token only 6 public tools (registration, login, status, price list) |
| Password storage | salted hash using a current method (Argon2id or bcrypt) |
| Administrative access | The only administrator of servers, database, storage, backups and production logs is a member of the management; access by SSH key with a second factor, logged. For emergencies a sealed emergency access is kept in the Telesherpa office; every opening is documented and the access data are renewed afterwards. No access for AI agents (§ 8(4)(a)) |
| Access control | rights exclusively via scope memberships (can_read, can_write, can_manage_scope), checked on the server side; reading and writing separated; agent accounts without an invitation isolated. Limitation: no right per object, a write right applies to all objects of a scope |
| Admin tools | cross-scope tools (search across scopes, action logs, user and import management, reports with their own SQL) only for named human administrators; report SQL only with a scope condition; every cross-scope access is logged |
| Separation | tenant separation via scopes; development and test environment separated from production, only with synthetic data |
| Encryption of stored data | data held on a highly available NAS (HA-NAS) at OVH, encrypted by Telesherpa itself with LUKS; OVH has no key. After a restart the storage is unlocked manually by the administrator |
| Internal AI agents | Code review agent (Sebastian) and concept review agent (Falco): no accounts, no system access. Development agent (Herbert): only code, configuration and synthetic test data, no access to customer data, no personal data to its model provider, production deployments only after approval by the management. |
2. Integrity
| Measure | Description |
|---|---|
| Transport | encrypted transmission with TLS 1.2 or higher; no upstream CDN; domains with a German registrar |
| Geocoding | transmission of only the address string or coordinates to Google (alternatively Nominatim), encrypted (TLS); no names or other object data; Google as an independent controller in the USA on the basis of the Data Privacy Framework (§ 7(5)) |
| Push encryption | Web Push according to W3C Push API / RFC 8030 with VAPID (RFC 8292). The title, text and target URL of every notification are end-to-end encrypted according to RFC 8291 (aes128gcm); only the recipient's browser can decrypt them. The push service sees only ciphertext, endpoint and time. The platform (ontouser/push.php) accepts only endpoints of the four push services listed in Annex 2 Part C |
| Input control | change and action log per account including agents, retention 12 months (§ 8(5)) |
| Automated workflows | rules with limited depth (max_depth 3), dedupe window 60 s, time limit for functions 100 to 30,000 ms, role whitelist; creation only with can_manage_scope; no webhook effects to the outside |
| Tool labelling | MCP tools with annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) |
| Platform-wide counters | count values that tools output platform-wide (e.g. number of objects per type) are restricted to the caller's scopes |
3. Availability and resilience
| Measure | Description |
|---|---|
| Data backup | encrypted backups at OVH at the Limburg site, no mirroring to other sites; daily, retention 35 days, restoration test at least once per quarter |
| Redundancy | highly available storage (HA-NAS) within the Limburg site; power, cooling and network redundancy according to the measures of OVH GmbH. Currently no second site: severe damage at the site can affect production data and backups at the same time |
| Monitoring | health endpoint (/health) with automatic alerting |
| Misuse and overload | rejection where there is no credit balance (HTTP 402); rate limiting of requests |
| Recovery | target: recovery within 24 h, data loss of no more than 24 h (does not apply to loss of the entire site, see Redundancy) |
| Availability | no availability owed (Section 8 of the Terms) |
4. Regular review
| Measure | Description |
|---|---|
| Data protection management | responsible: management; annual review of this Annex, for the first time by 31.10.2027 |
| Changes to the code | review by code review and concept review agents without production data; deployment to production only after approval by the management |
| Vulnerabilities | security updates for servers and dependencies within 14 days, critical ones within 72 h |
| Incident response | reporting chain: detection → management → notification to the customer within 24 h (§ 10); processes aligned with the Cyber Resilience Act, reports under the CRA via the Single Reporting Platform (SRP) |
| Obligation | written obligation of all persons to confidentiality before access to customer data |
| Defaults | new accounts without third-party rights; PUBLIC only by an administrator of Telesherpa |
| Processor control | sub-processors only in accordance with § 6, with a DPA and verified guarantees |
Annex 2: Places of processing and sub-processors
Version 1.1, as of 15.11.2026. Changes in accordance with § 6(3), list with history at https://www.telesherpa.com/de/avv. Services with third-country are marked in bold.
Part A: Places of processing of Telesherpa
| Place | Type | What is processed there | When |
|---|---|---|---|
| Data centre of OVH GmbH, Limburg site, Germany (Part B No. 1) | Data centre | platform, database, files, data backups; no mirroring to other sites | permanently |
Part B: Sub-processors
| # | Sub-processor | Service | Place | Third-country involvement / guarantee |
|---|---|---|---|---|
| 1 | OVH GmbH, Oskar-Jäger-Straße 173/K6, 50825 Köln, Amtsgericht Köln HRB 122481 | servers, database, HA-NAS storage, data backups | data centre Limburg, Germany (this site only) | possible remote access for security and maintenance by the group-internal sub-processors OVH Hebergement INC (Canada) and OVH Limited (United Kingdom); adequacy decision (Art. 45 GDPR) for both countries. Basis: DPA of OVH GmbH, version 17.10.2025, clause 6.2; sub-processor list of OVH GmbH, as of 16.10.2025. Further group-internal sub-processors of OVH in the EU/EEA according to this list |
| 2 | Apple: iCloud Mail with custom domain. Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland; processing also by Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA | delivery of activation codes, notifications and emails with PDF attachment | EU and USA | third-country involvement USA: EU-U.S. Data Privacy Framework (Apple Inc. certified) or standard contractual clauses |
| 3 | AI model providers for internal agents | — | — | not applicable: internal agents have no access to the customer's data (§ 8(4)) |
Telesherpa does not use any further external services (no external ticket, monitoring or logging tools). The platform itself does not call up any AI model.
Part C: Delivery services of the browsers, encrypted content only
Push notifications to the web application and the PWA are delivered via Web Push (W3C Push API / RFC 8030, VAPID according to RFC 8292). Telesherpa operates no push infrastructure of its own and uses neither APNs certificates nor the FCM SDK. Which of the following services transports the notification is determined by the user's browser, not by Telesherpa. Title, text and target URL are end-to-end encrypted according to RFC 8291 (aes128gcm); the push service receives no content in plain text, but only ciphertext and the metadata necessary for delivery (endpoint address of the device, time, IP address). The push services transport the encrypted messages and have no access to their content.
| Push service (endpoint) | Browser | Provider | Third-country involvement / guarantee |
|---|---|---|---|
| push.apple.com | Safari, iOS | Apple Inc., USA | USA: EU-U.S. Data Privacy Framework |
| fcm.googleapis.com | Chrome, Edge (Chromium), Android | Google LLC, USA | USA: EU-U.S. Data Privacy Framework |
| Mozilla Push Service | Firefox | Mozilla Corporation, USA | USA: not certified under the Data Privacy Framework; according to its own information, Mozilla bases transfers on standard contractual clauses. content reaches Mozilla only in encrypted form (Annex 1) |
| Windows Push Notification Services | Edge (Windows) | Microsoft Corporation, USA | USA: EU-U.S. Data Privacy Framework |
The platform rejects other endpoints.
Part D: Services as independent controllers
The following services are not sub-processors. They act as independent controllers under their own terms. Geocoding via Google is an integral part of the service; Telesherpa transmits address data on the customer's instruction, which lies in the use of the platform and the entry of addresses (§ 7(5)). The customer informs its data subjects about this.
| Service | Provider | Purpose and data | Place | Basis / guarantee |
|---|---|---|---|---|
| Google Maps Geocoding API (standard) | Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland (contracting party); Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA (processing) | geocoding (onto_object_geocode): address strings of objects or coordinates; technical data of the request (server IP, time, API key of Telesherpa) | USA | Google Maps Platform Terms of Service with the Google Controller-Controller Data Protection Terms (version 11 of 7.5.2026); transfer to the USA on the basis of the EU-U.S. Data Privacy Framework (Google LLC certified) |
| Nominatim (fallback, only if no Google key is stored or Google returns no result) | OpenStreetMap Foundation, St John’s Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdom | address strings of objects | United Kingdom, Ireland, Netherlands (according to OSMF) | terms of use and data protection terms of the OSMF; adequacy decision for the United Kingdom (Art. 45 GDPR) |
No sub-processors of Telesherpa
Customer's AI models and agents (e.g. providers of large language models, agent frameworks, the customer's own models): they are selected, connected and operated by the customer. Depending on the arrangement, their providers are processors of the customer or independently responsible. Telesherpa transmits data to them only on the customer's instruction; the DPA and the third-country assessment are the customer's responsibility (§ 8(2)).
Models of internal agents without access to customer data and the services through which these models are provided: not part of the service; pursuant to § 8(4)(a) and (c) these agents have no technical access to the customer's personal data.
Payment service providers (SumUp) for the purchase of credits: own responsibility of Telesherpa or of the payment service provider respectively; see the privacy policy.
Web analytics on www.telesherpa.com (Ahrefs): website only, not the platform; discontinued on 11.11.2026.
Domain registrar (Germany): no access to customer data.
Annex 3: Contact points and contacts
| Role | Customer | Telesherpa |
|---|---|---|
| Instructions and declarations (§ 3(5)) | Every account authorised by the customer, including an agent account | — |
| Contact Point (§ 3(5)(d)) | contact details of the operator pursuant to Section 4 of the Terms and platform mailbox | — |
| Optional: natural person as contact | name, function, email address, if the customer so wishes | — |
| Receipt of instructions and service requests | — | service@telesherpa.com |
| Notifications of data breaches (§ 10) | to the Contact Point | notifications of the customer to adg@telesherpa.com |
| Data protection contact | as specified by the customer | management, adg@telesherpa.com |