{"id":93,"date":"2026-10-11T21:21:51","date_gmt":"2026-10-11T19:21:51","guid":{"rendered":"https:\/\/dt-pm.eu\/avv\/"},"modified":"2026-10-11T21:21:51","modified_gmt":"2026-10-11T19:21:51","slug":"avv","status":"publish","type":"page","link":"https:\/\/dt-pm.eu\/en\/avv\/","title":{"rendered":"Vertrag zur Auftragsverarbeitung (DT-PM AI Sale Assistant)"},"content":{"rendered":"<div class=\"agb_content dtpm-rechtstext\"><h1>Data Processing Agreement (DT-PM AI Sale Assistant)<\/h1><p class=\"dtpm-bb__kopf\">Version 1.1, as of 11.10.2026<\/p><p class=\"dtpm-bb__archivhinweis\">This translation is provided for information only. Only the <a href=\"https:\/\/dt-pm.eu\/wp-json\/wp\/v2\/pages\/93\" hreflang=\"de\" lang=\"de\">German version<\/a> is legally binding.<\/p><div class=\"dtpm-bb__text\"><p>pursuant to Art. 28 of Regulation (EU) 2016\/679 (GDPR)<\/p>\n<p><em>Version 1.1, as of 11 October 2026. Changed compared with version 1.0: Annex 2 No. 2.<\/em><\/p>\n<p><strong>between<\/strong><\/p>\n<p>the customer who uses DT-PM AI Sale Assistant for WooCommerce (operator of the online shop), according to the details in the customer account \u2014 hereinafter <strong>\u201cController\u201d<\/strong> \u2014<\/p>\n<p><strong>and<\/strong><\/p>\n<p><strong>DT PM GmbH<\/strong>, Forckenbeckstr. 10, 48431 Rheine, Germany, registered in the commercial register of the Local Court of Steinfurt under HRB 12409, represented by its managing director Dirk Th\u00f6rner \u2014 hereinafter <strong>\u201cProcessor\u201d<\/strong> \u2014<\/p>\n<hr>\n<h2>\u00a7 1 Subject matter and duration<\/h2>\n<p>(1) The Processor provides the Controller with the AI-based advisory assistant \u201cDT-PM AI Sale Assistant for WooCommerce\u201d (plugin and connected service at <code>api.dt-pm.eu<\/code>) (<strong>\u201cMain Contract\u201d<\/strong>). In doing so, it processes personal data on behalf of and in accordance with the instructions of the Controller.<\/p>\n<p>(2) This agreement sets out the data protection obligations of both parties. It applies to all processing under the Main Contract in which the Processor processes personal data of the Controller.<\/p>\n<p>(3) The term corresponds to the term of the Main Contract. The provisions on deletion and return (\u00a7 10) continue to apply beyond it.<\/p>\n<p>(4) This agreement does not cover data for which the Processor is itself the controller, in particular contract, account, billing and licence data of the Controller, and the licence and update requests of the plugins.<\/p>\n<h2>\u00a7 2 Nature, purpose, data, data subjects<\/h2>\n<p>The nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in <strong>Annex 1<\/strong>.<\/p>\n<h2>\u00a7 3 Instructions<\/h2>\n<p>(1) The Processor processes personal data only on documented instructions from the Controller, including with regard to transfers to a third country, unless it is required to do so by Union or Member State law; in that case it informs the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.<\/p>\n<p>(2) This agreement, the Main Contract and the settings the Controller makes in the plugin\u2019s back office constitute the instructions. The Controller issues further instructions in text form. Instructions that go beyond the Main Contract may justify reasonable remuneration; this does not apply to instructions required for the Processor to fulfil its legal obligations.<\/p>\n<p>(3) If the Processor considers an instruction to be unlawful, it informs the Controller without undue delay. It may suspend execution until the instruction is confirmed or changed.<\/p>\n<p>(4) <strong>No own purposes.<\/strong> The Processor processes the personal data entrusted to it exclusively for the purposes set out in Annex 1. Processing for its own purposes, in particular for training models or for profiling, does not take place. The Processor uses the contractual and technical settings of the sub-processors that operate language models so that content is not used to train their models. Processing by sub-processors as controllers in their own right, as provided for in their terms (Annex 3 Part B), remains unaffected.<\/p>\n<h2>\u00a7 4 Obligations of the Processor<\/h2>\n<p>(1) <strong>Confidentiality.<\/strong> The Processor only uses persons for processing who have committed themselves to confidentiality or are under a statutory obligation of confidentiality (Art. 28(3)(b), Art. 29 GDPR).<\/p>\n<p>(2) <strong>Technical and organisational measures.<\/strong> The Processor takes the measures described in <strong>Annex 2<\/strong> in accordance with Art. 32 GDPR. It develops them further; material reductions in the level of protection are not permitted. It communicates material changes on request.<\/p>\n<p>(3) <strong>Support with data subject rights.<\/strong> It supports the Controller with appropriate technical and organisational measures in responding to requests under Chapter III GDPR (\u00a7 8).<\/p>\n<p>(4) <strong>Support under Art. 32 to 36 GDPR.<\/strong> It supports the Controller with the security of processing, notifications of personal data breaches, data protection impact assessments and consultations with the supervisory authority, insofar as this is appropriate given the nature and scope of the processing and the information available to it.<\/p>\n<p>(5) <strong>Notification of breaches.<\/strong> The Processor notifies the Controller of a personal data breach affecting the Controller without undue delay, where possible within 48 hours of becoming aware of it, at the email address stored in the customer account. The notification contains, as far as known, the information under Art. 33(3) GDPR.<\/p>\n<p>(6) <strong>Records.<\/strong> It maintains a record of processing activities in accordance with Art. 30(2) GDPR.<\/p>\n<p>(7) <strong>Contact person.<\/strong> The contact person for data protection matters at the Processor is its managing director Dirk Th\u00f6rner, reachable at the email address given in the Processor\u2019s legal notice (Impressum).<\/p>\n<h2>\u00a7 5 Obligations of the Controller<\/h2>\n<p>(1) The Controller is responsible for the lawfulness of the processing vis-\u00e0-vis the data subjects, in particular for the legal basis under Art. 6 GDPR and the information obligations under Art. 13 and 14 GDPR. This includes informing, in its shop\u2019s privacy policy, about the use of the AI assistant, the transfer of chat inputs to the services named in Annex 3 (including to third countries) and, where applicable, the labelling as an AI system.<\/p>\n<p>(2) Before first use, the chat widget shows end customers a notice about the transfer of their messages to an AI service and makes use dependent on their confirmation. This notice does not replace the Controller\u2019s obligations under paragraph 1.<\/p>\n<p>(3) The assistant does not filter user inputs; they are transferred unchanged to the language model. The Controller must not configure or use the assistant in such a way that special categories of personal data (Art. 9 GDPR) are specifically collected. Within its means, it advises users not to enter such data or other sensitive information in the chat. Health data within the meaning of the US HIPAA must not be processed.<\/p>\n<p>(4) The Controller must not store personal data of third parties in configuration fields, causal chains or other texts it maintains in the back office.<\/p>\n<p>(5) The Controller designates a contact person for instructions and notifications; the email address stored in the customer account is authoritative.<\/p>\n<p>(6) The Controller complies with the terms of use and usage policies of the sub-processors named in Annex 3 insofar as they restrict or prohibit the input or processing of certain data or certain uses. The Processor passes these restrictions on to the Controller in Annex 3 or in text form; new or changed restrictions apply after notification in text form.<\/p>\n<h2>\u00a7 6 Sub-processing<\/h2>\n<p>(1) The Controller grants the Processor <strong>general authorisation<\/strong> to use the sub-processors named in <strong>Annex 3<\/strong> (Art. 28(2) GDPR).<\/p>\n<p>(2) The Processor informs the Controller in text form of any intended addition or replacement at least 30 days before it takes effect (email to the stored address or publication with notification). The Controller may object within 14 days of the notification for an important data protection reason; if the period that the Processor has vis-\u00e0-vis the sub-processor concerned (Annex 3 Part B) is shorter, that shorter period applies. If a sub-processor informs the Processor of a change only later, the Processor informs the Controller without undue delay after receipt. If the objection is not remedied, the Controller may terminate the Main Contract extraordinarily with effect from the date the change takes effect.<\/p>\n<p>(3) The Processor imposes on each sub-processor essentially the same data protection obligations as set out in this agreement, in particular sufficient guarantees for appropriate technical and organisational measures. If a sub-processor fails to fulfil its obligations, the Processor is liable to the Controller for the performance of those obligations (Art. 28(4) GDPR).<\/p>\n<h2>\u00a7 7 Processing outside the EU \/ EEA<\/h2>\n<p>(1) Processing generally takes place in the European Union or the European Economic Area. A transfer to a third country only takes place if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of an adequacy decision or appropriate safeguards (standard contractual clauses of the Commission, with a transfer impact assessment where required).<\/p>\n<p>(2) Existing transfers to third countries and the safeguard used in each case are set out in Annex 3. In the standard case (without the Controller\u2019s own key), chat inputs are transferred to Anthropic in the USA. A third-country connection may also exist where the data is located in the EU but the sub-processor is established in a third country or has access from there.<\/p>\n<h2>\u00a7 8 Data subject rights<\/h2>\n<p>(1) If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without undue delay and does not respond itself, unless the Controller determines otherwise.<\/p>\n<p>(2) The Processor provides the Controller with the information, rectifications, erasures and restrictions that are technically possible for it. Since chat content is not stored on the Processor\u2019s servers (Annex 1), information about chat content is only possible to a limited extent. The same applies to truncated IP addresses in the rate-limiting log and to usage events that are only linked to a browser session via a session identifier.<\/p>\n<h2>\u00a7 9 Evidence and audits<\/h2>\n<p>(1) On request, the Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR. This is done initially by way of information and documentation (in particular Annexes 2 and 3).<\/p>\n<p>(2) Where necessary, the Controller may carry out audits, including inspections, itself or through an auditor bound to confidentiality. They must be announced with reasonable notice (at least 14 days); audits at sub-processors are only possible under their terms and to the extent described in Annex 3 Part B and are announced with the notice period stated there, take place during normal business hours, do not disrupt operations disproportionately, and exclude access to data of other customers and to trade secrets of the Processor. The effort may be reasonably remunerated unless the audit is prompted by a breach.<\/p>\n<h2>\u00a7 10 Deletion and return<\/h2>\n<p>(1) After the end of the Main Contract, or earlier on instruction, the Processor deletes all personal data processed on behalf of the Controller, unless there is an obligation to store it under Union or Member State law. Data is returned only insofar as the Processor actually stored it and it can be attributed to the Controller.<\/p>\n<p>(2) Deletion in the production systems takes place within 30 days after the end of the contract; it is currently carried out manually following a fixed, documented procedure. Backup copies are overwritten according to a fixed rotation schedule; data contained in backups is deleted only with the rotation, at the latest after about six months (Annex 1 No. 4). Until then it is not used for other purposes and not restored, except to restore the service after an outage. At the sub-processors the periods under Annex 3 Part B apply. On request, the Processor confirms the deletion in text form.<\/p>\n<p>(3) During the term of the contract, the retention and deletion periods in Annex 1 apply.<\/p>\n<h2>\u00a7 11 Liability<\/h2>\n<p>Liability is governed by Art. 82 GDPR and the provisions of the Main Contract.<\/p>\n<h2>\u00a7 12 Final provisions<\/h2>\n<p>(1) In the event of conflicts between this agreement and the Main Contract, this agreement takes precedence in matters of data protection.<\/p>\n<p>(2) Amendments and additions require text form. The Processor may amend this agreement if this is necessary due to a change in the law, an order of a supervisory authority or the further development of the service; it announces amendments in text form at least 30 days in advance. The Controller may object; \u00a7 6(2) sentence 3 applies accordingly.<\/p>\n<p>(3) Should any provision be invalid, the remainder of the agreement remains valid.<\/p>\n<p>(4) The law of the Federal Republic of Germany applies. The place of jurisdiction is Rheine, to the extent permitted.<\/p>\n<p>(5) The agreement is concluded by the Controller\u2019s consent in the back office or in the purchasing process. The version and time stamp of the consent are archived.<\/p>\n<hr>\n<h2 id=\"annex-1\">Annex 1 \u2014 Description of the processing<\/h2>\n<h3>1. Subject matter and purpose<\/h3>\n<p>Operation of an AI-based advisory assistant in the Controller\u2019s online shop:<\/p>\n<ul><li>receiving the inputs of shop visitors in the chat widget, processing them by the core API (<code>api.dt-pm.eu<\/code>) and responding with product recommendations from the Controller\u2019s catalogue;<\/li><li>protecting the service against misuse and overload (rate limiting);<\/li><li>billing of the agreed conversation quota (counting conversations per tenant);<\/li><li>operation, security, backup and troubleshooting of the service.<\/li><\/ul>\n<h3>2. Data subjects<\/h3>\n<ul><li>visitors and customers of the Controller\u2019s online shop who use the chat assistant;<\/li><li>employees and agents of the Controller who operate the plugin\u2019s back office.<\/li><\/ul>\n<h3>3. Types of personal data<\/h3>\n<div class=\"table-wrap\"><table class=\"data\">\n<thead><tr><th>Type of data<\/th><th>Processing<\/th><\/tr><\/thead>\n<tbody>\n<tr><td><strong>Content of chat inputs<\/strong> (free text)<\/td><td>Transferred unfiltered to the language model: in the standard case to Anthropic, if the Controller uses its own key, to the provider it has chosen. The user may provide personal information even though the assistant does not ask for any. No chat content is stored on the Processor\u2019s servers.<\/td><\/tr>\n<tr><td><strong>Search text derived from the request<\/strong><\/td><td>Transferred to Mistral (EU endpoint) for the similarity search.<\/td><\/tr>\n<tr><td><strong>IP address<\/strong><\/td><td>The service keeps no access log. If rate limiting is triggered, the IP address is written to the system log in truncated form (IPv4 to \/24, IPv6 to \/48) and deleted after 8 days at most.<\/td><\/tr>\n<tr><td><strong>Pseudonymous identifiers, token quantities<\/strong><\/td><td>Tenant ID and consumption figures in the operating logs.<\/td><\/tr>\n<tr><td><strong>Usage events<\/strong><\/td><td>Event type, tenant, session identifier, time; no free text.<\/td><\/tr>\n<tr><td><strong>Cleaned feedback<\/strong><\/td><td>If a user rates an answer, their request is cleaned of personal information by a language model (Mistral) and only then stored. If cleaning fails, nothing is stored.<\/td><\/tr>\n<tr><td><strong>User\u2019s browser storage<\/strong><\/td><td>The consent notice (<code>localStorage<\/code>) and the conversation history of the current session (<code>sessionStorage<\/code>) remain in the browser; the core API receives the history with each request and does not store it.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p><strong>Not processed<\/strong> are customer accounts, orders, payment data and addresses of the Controller\u2019s end customers. Handover to a human (\u201cby email or link\u201d) takes place exclusively in the user\u2019s browser; no conversation content is transferred.<\/p>\n<h3>4. Retention and deletion periods<\/h3>\n<div class=\"table-wrap\"><table class=\"data\">\n<thead><tr><th>Data<\/th><th>Period<\/th><\/tr><\/thead>\n<tbody>\n<tr><td>Chat content on the Processor\u2019s servers<\/td><td>not stored<\/td><\/tr>\n<tr><td>IP addresses in the rate-limiting log<\/td><td>8 days at most, truncated<\/td><\/tr>\n<tr><td>Operating logs of the core API<\/td><td>8 days at most (system journal with daily files, retention 7 days)<\/td><\/tr>\n<tr><td>Usage events<\/td><td>12 months<\/td><\/tr>\n<tr><td>Cleaned feedback, conversation counters<\/td><td>until the end of the Main Contract (\u00a7 10)<\/td><\/tr>\n<tr><td>Backups<\/td><td>up to about 6 months (14 daily, 8 weekly, 6 monthly versions); hosting provider backups 14 days at most<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<hr>\n<h2 id=\"annex-2\">Annex 2 \u2014 Technical and organisational measures (Art. 32 GDPR)<\/h2>\n<ol><li><strong>Tenant separation.<\/strong> Data is kept and retrieved separately per tenant.<\/li><li><strong>Access protection of the interface.<\/strong> Endpoints are protected (tenant secret for administrative functions, CORS configuration, rate limiting per sender). From plugin version 1.2.0, the chat widget in the visitor\u2019s browser no longer receives a permanent tenant secret but a short-lived access token (15 minutes), which the plugin retrieves from the service on the server side and which is bound to the tenant and to the origin of the requests. Keys of the Controller for its own model providers are stored encrypted and decrypted only for the call.<\/li><li><strong>Transparency towards users.<\/strong> Before first use, the widget shows a notice about the transfer to an AI service and requires confirmation.<\/li><li><strong>Data minimisation.<\/strong> No customer account, order or payment data of end customers in the service; no chat content in database tables; feedback only after cleaning; knowledge pool only with abstracted structures without personal reference.<\/li><li><strong>Logging.<\/strong> No access log on <code>api.dt-pm.eu<\/code>; no visitor IP in the operating logs of the core API; rate-limiting log with truncated IP and a period of 8 days at most; no sending of logs to external error services.<\/li><li><strong>Separation of providers.<\/strong> The visitor chat runs via Anthropic, all other functions via Mistral (EU endpoint).<\/li><li><strong>Backups and encryption.<\/strong> The backups on the second server are encrypted. The daily local backups on the production server (14 days) are not separately encrypted; they are in a directory accessible only to the operating account. The keys are on servers of the same hosting provider (netcup); it is bound by the data processing agreement.<\/li><li><strong>Availability.<\/strong> Daily backup in two ways (backup to a second server in \u201cappend only\u201d mode with thinning on the target server; second daily backup of the database); rotation according to Annex 1 No. 4.<\/li><li><strong>Separation of test and production.<\/strong> Separate staging environment and separate staging database project without customer data.<\/li><li><strong>Quality assurance.<\/strong> The Python test suite runs before every release; the browser tests of the widget are triggered before approvals; secret scanning in the source code.<\/li><li><strong>Order control.<\/strong> Instructions under \u00a7 3; commitment of the persons used to confidentiality under \u00a7 4(1).<\/li><li><strong>Data breaches.<\/strong> Notification under \u00a7 4(5).<\/li><\/ol>\n<hr>\n<h2 id=\"annex-3\">Annex 3 \u2014 Sub-processors<\/h2>\n<div class=\"table-wrap\"><table class=\"data\">\n<thead><tr><th>Sub-processor<\/th><th>Service<\/th><th>Data<\/th><th>Location \/ transfer<\/th><th>Basis<\/th><\/tr><\/thead>\n<tbody>\n<tr><td><strong>netcup GmbH<\/strong>, Karlsruhe (further processors of netcup: Anexia Holding GmbH, Klagenfurt; Anexia Cloud Solutions GmbH, Klagenfurt and Karlsruhe)<\/td><td>Hosting of the servers (core API, databases, licence service) and of the backup server<\/td><td>all data processed by the server; backups encrypted<\/td><td>Austria (Vienna)<\/td><td>Data processing agreement of 5 October 2026<\/td><\/tr>\n<tr><td><strong>Supabase Pte. Ltd.<\/strong><\/td><td>Database (PostgreSQL with <code>pgvector<\/code>)<\/td><td>Tenant data, product data, embeddings, usage events, cleaned feedback<\/td><td>Region Frankfurt (eu-central-1); contracting party established in Singapore, group in the USA (third-country connection under \u00a7 7(2))<\/td><td>Data Processing Addendum, Version 1, 1 August 2026, with standard contractual clauses (section 12 therein)<\/td><\/tr>\n<tr><td><strong>Anthropic, PBC<\/strong>, 548 Market Street, PMB 90375, San Francisco, California 94104, USA<\/td><td>Language model for the visitor chat in the standard case<\/td><td>Chat inputs, catalogue excerpts<\/td><td>USA (third country)<\/td><td>Anthropic Data Processing Addendum (version of 24 February 2025) with standard contractual clauses (Modules 2 and 3)<\/td><\/tr>\n<tr><td><strong>Mistral AI<\/strong>, 15 rue des Halles, 75001 Paris, France (registered in Paris under number 952 418 325)<\/td><td>Language models for category analysis, causal chains, content drafts, tone, variant attributes and cleaning of feedback; embeddings<\/td><td>Catalogue and product data, search text derived from the request, request text for cleaning<\/td><td>EU (<code>api.eu.mistral.ai<\/code>)<\/td><td>Mistral AI Data Processing Addendum (version of 27 July 2026)<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>If the Controller uses its own key of a model provider, the Controller\u2019s contractual relationship with that provider applies to that call.<\/p>\n<hr>\n<h2 id=\"annex-3-part-b\">Annex 3 Part B \u2014 Restrictions passed on by the sub-processors<\/h2>\n<p>The following restrictions and periods are taken from the data processing addenda of the sub-processors (as of the versions retrieved: 5 October 2026). The Controller complies with them (\u00a7 5(6)); the Processor passes on changes under \u00a7 5(6).<\/p>\n<h3>All sub-processors (Anthropic, Mistral AI, Supabase)<\/h3>\n<ul><li>Special categories of personal data (Art. 9 GDPR) are not envisaged and must not be specifically processed (\u00a7 5(3)).<\/li><li>The Controller fulfils its information obligations towards the data subjects and obtains consent where the processing requires it (\u00a7 5(1)).<\/li><li>Notification of breaches: Anthropic and Supabase notify the Processor within 48 hours of becoming aware, Mistral AI without undue delay after becoming aware. The Processor forwards the notification under \u00a7 4(5).<\/li><\/ul>\n<h3>Anthropic<\/h3>\n<ul><li>The data processing addendum lists no special categories of personal data (\u201cNone\u201d).<\/li><li>Objection to a new sub-processor: in writing within 15 days of the notification; thereafter it is deemed approved.<\/li><li>Audit: Anthropic provides audit reports and certificates on written request. An audit of its own is possible at the customer\u2019s expense, by an auditor bound to confidentiality, with a scope and schedule agreed in advance and at most once in twelve months.<\/li><li>Retention during the term: according to its own information, Anthropic automatically deletes inputs and outputs in its backend within 30 days of receipt or generation (Anthropic privacy page, retrieved on 11 October 2026). Exceptions: a different agreement, legal obligations and enforcement of the usage policy; content flagged by the automatic safety systems is retained for up to 2 years.<\/li><li>Deletion and return: within 30 days after the end of the contract; exceptions for statutory retention obligations, to resolve a dispute or to prevent harmful use.<\/li><li>The standard contractual clauses are governed by Irish law.<\/li><\/ul>\n<h3>Mistral AI<\/h3>\n<ul><li>The data processing addendum lists no special categories of personal data (\u201cNone\u201d).<\/li><li>Mistral AI may, as a controller in its own right, process inputs and outputs for automated moderation (abuse detection) as long as zero data retention is not activated. Training with inputs and outputs is only permitted if the customer has not objected; for the Processor the training switch is turned off. Feedback given via Mistral AI\u2019s rating functions (\u201cthumbs up\/down\u201d) is used by Mistral AI, together with the associated input and output, for training and improvement; the Controller does not give such ratings. Labs models are not used.<\/li><li>Objection to a new sub-processor: in writing within 10 days of the notification, for comprehensible data protection reasons; thereafter it is deemed approved. If no agreement is reached, Mistral AI may terminate the contract or the products concerned.<\/li><li>Audit: initially on the basis of documents; beyond that at most one on-site audit per year, with at least 90 calendar days\u2019 written notice, by a jointly appointed independent auditor, during normal business hours and at the customer\u2019s expense.<\/li><li>Deletion and return: the data is no longer accessible 30 days after access ends.<\/li><\/ul>\n<h3>Supabase Pte. Ltd.<\/h3>\n<ul><li>Sensitive data only with the express consent of the data subjects; the Controller ensures this insofar as such data arises at all. Health data within the meaning of HIPAA must not be transferred without a separate agreement with Supabase for this purpose.<\/li><li>Region: the data is stored in the chosen region (Frankfurt) and processed \u201cprimarily\u201d there, except insofar as legal obligations, further instructions or the provision of the service require otherwise.<\/li><li>Objection to a new sub-processor: in writing within 5 days of the notification. If no solution is found, the part of the contract concerned may be terminated within 30 days at most.<\/li><li>Audit: initially on the basis of audit reports and certificates; beyond that at most once per calendar year, with at least 30 days\u2019 written notice, during normal business hours and only after written agreement on scope and timing.<\/li><li>Deletion and return: release on request within 30 days after the end of the contract; Supabase then deletes all copies.<\/li><\/ul>\n<h3>netcup GmbH<\/h3>\n<ul><li>The terms of the data processing agreement of 5 October 2026 apply. The Processor passes on any resulting restrictions under \u00a7 5(6).<\/li><\/ul>\n<\/div><h2 class=\"dtpm-bb__protokolltitel\">Change log<\/h2>\n\t\t<div class=\"table-wrap\"><table class=\"data dtpm-bb__protokoll\">\n\t\t\t<thead><tr><th>Version<\/th><th>As of<\/th><th>Valid from<\/th><th>Valid until<\/th><th>Reason<\/th><\/tr><\/thead>\n\t\t\t<tbody><tr><td>1.1<\/td><td>11.10.2026<\/td><td>11.11.2026<\/td><td>current<\/td><td>Annex 2 No. 2: the chat widget receives a short-lived access token instead of the tenant secret (from plugin 1.2.0).<\/td><\/tr><tr><td><a href=\"https:\/\/dt-pm.eu\/en\/avv\/?fassung=1.0\">1.0<\/a><\/td><td>11.10.2026<\/td><td>11.10.2026<\/td><td>10.11.2026<\/td><td>Initial version.<\/td><\/tr><\/tbody>\n\t\t<\/table><\/div>\n\t\t<p class=\"dtpm-bb__archivsatz\">Earlier versions remain available. The version agreed to when the contract was concluded applies.<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":0,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-93","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/pages\/93","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/comments?post=93"}],"version-history":[{"count":0,"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/pages\/93\/revisions"}],"wp:attachment":[{"href":"https:\/\/dt-pm.eu\/en\/wp-json\/wp\/v2\/media?parent=93"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}