Skip to content
Home / Data Processing Agreement (DPA)

Data Processing Agreement (DPA)

Binding version, adopted unchanged from our collection of legal texts. Questions about it are answered at datenschutz@zepdesk.de.

Version 1.2.0 Valid from 2026-11-23 Provider: ZeptronIT UG (haftungsbeschränkt), Harmsdorf

This English text is a convenience translation. The legally binding version is the German original.

Data Processing Agreement (DPA) pursuant to Art. 28 DSGVO (GDPR) for the use of ZepDesk. As of: 2026-11-20

Preamble

This Data Processing Agreement (hereinafter "DPA") specifies the parties' data protection obligations arising from the provision and use of the ZepDesk platform agreed in the main contract ("usage contract").

The controller within the meaning of Art. 4 No. 7 DSGVO (GDPR) is the Customer, hereinafter "Client".
The processor within the meaning of Art. 4 No. 8 DSGVO (GDPR) is ZeptronIT UG (haftungsbeschränkt), hereinafter "Contractor".

§ 1 Subject Matter and Duration of the Order

(1) The subject matter of the processing is the provision of the SaaS platform ZepDesk, including the associated storage, processing and provision of the data entered by the Client.

(2) The nature and purpose of the processing are, in each case via the web interface, the programming interface and the ZepDesk app for Android and iOS:

  • ERP and accounting functions, customer management, quotes, invoices, delivery notes, reporting and receipt recognition;
  • payroll, insofar as the Client uses it;
  • payment transactions: retrieval of account balances and transactions, the matching of payments with invoices and receipts and the creation of SEPA files for the credit transfer of net wages and for direct debits, which the Client itself submits to its bank;
  • sending emails from the platform;
  • the transmission of tax data to the tax authorities on the Client's instruction, insofar as the Client has given the Contractor a transmission mandate for this (§ 5b);
  • the transmission of data to social insurance institutions and their receiving offices and the retrieval of their responses in the Client's name, insofar as the Client has given the Contractor a transmission mandate for this (§ 5a);
  • the handover of documents to recipients named by the Client, such as its tax advisor, in each case only after the Client's approval in the individual case;
  • the retrieval of data from third-party services that the Client connects itself, and the transmission of data to them (§ 5 para. 4).

(3) Duration: The duration corresponds to the term of the usage contract plus a 30-day grace period for the data export.

§ 2 Scope, Nature and Purpose of the Collection, Processing and Use

(1) Types of data:

  • Master data (name, address, email, phone) of the Client's end customers, suppliers, members and employees
  • Communication data from the invoicing and quotation process
  • Contract and billing data
  • Bank and payment data: bank details (IBAN, BIC, account holder), account balances and transactions, amounts and remittance information
  • Data on SEPA direct debit mandates: mandate reference, date of signature, type of scheme (Core or B2B), time of the first and the last collection, notes and the signed mandate as a file, as well as the Client's creditor identifier
  • Employee data for payroll, insofar as the Client uses it: tax identification number, tax class and other wage tax deduction characteristics, social insurance number, health insurance fund and social insurance status, date of birth, nationality, marital status and number of children, pay, absences, garnishments and occupational pension schemes
  • Content data from documents, attachments and notes
  • Receipt images and voice recordings for speech recognition (“dictation”)
  • Tax data and records of approvals and transmissions to the tax authorities
  • Data for social insurance, insofar as the Client gives a transmission mandate (§ 5a): establishment numbers, notifications, contribution statements and applications with the employees' data, the financial accounting data for the electronically supported employer audit, the responses of the institutions and records of approvals and transmissions
  • Credentials for third-party services that the Client connects (access authorizations from a login with the provider, API keys), logs of connecting and refreshing such access (Annex 1 No. 6.2) and records of approvals of handovers to named recipients

(2) Special categories of personal data (Art. 9 para. 1 DSGVO): If the Client uses payroll, the Contractor also processes on its behalf

  • the religious affiliation (denomination) of employees and their spouses or civil partners, insofar as it is required for church tax, and
  • health data: periods of incapacity for work, of receipt of sickness benefit or transitional benefit (Übergangsgeld), of maternity protection and of care leave, in each case with start and end and the subsidies and reimbursements calculated from them.

If the Client instructs the Contractor to retrieve its employees' incapacity for work data from the health insurance funds (§ 5a, § 109 SGB IV), their details are added: start and end of the incapacity for work or of an inpatient stay, the date of the medical finding, the marking as a first or follow-up notification and the indication whether the incapacity for work is based on an accident at work or another accident.

Periods of incapacity for work also come from HR software that the Client connects, if the Client switches on the retrieval of these periods there (§ 5 para. 4).

ZepDesk does not record a severe disability. Free-text fields such as notes and remarks contain such details only if the Client enters them there. In individual cases, account transactions, booking texts, receipts and tax certificates may allow conclusions about special categories, for example contributions to a trade union or a religious community or an account for sickness benefit subsidies; ZepDesk does not analyze them for this. The measures of Annex 1 apply to the data under this paragraph, in particular the restriction of access to the Administration and Tax roles (No. 6.1), the logging of changes (No. 6.2) and, for transmission, No. 6.5.

(3) Categories of data subjects:

  • Employees and users of the Client
  • Employees and former employees of the Client and, insofar as required for wage tax and social insurance, their spouses or civil partners and children
  • Customers, prospects, suppliers and members of the Client
  • Payees and payers, account holders and signatories of direct debit mandates
  • Contact persons of the recipients to whom the Client hands over documents
  • Other business partners of the Client whose data is recorded

(4) Purpose: Operation of the ERP, accounting, payroll and payment functions and of the transmissions for the Client in accordance with § 1 para. 2.

§ 3 Obligations of the Contractor

The Contractor undertakes:

  1. to process data exclusively on the documented instructions of the Client. Instructions are given in particular through the provisions of this agreement, through specific individual instructions of the Client, or through functions that the Client controls itself via the platform. The creation of a SEPA file, the approval of a handover to a named recipient or of a transmission to the tax authorities or to social insurance institutions, the connection of a third-party service, switching on an automation for a connection and consenting to a developer app by the Client are also instructions.
  2. to comply with the technical and organizational measures (TOM) referred to in Art. 32 DSGVO in accordance with Annex 1 of this agreement.
  3. to obligate all persons engaged in data processing to confidentiality (Art. 28 para. 3 lit. b, Art. 29, Art. 32 para. 4 DSGVO) and to inform the persons who can handle responses of the social insurance institutions of the obligations under § 78 para. 1 SGB X before their first access (§ 78 para. 2 SGB X).
  4. to inform the Client without undue delay in the event of data breaches (Art. 33 para. 2 DSGVO), so that the Client can fulfill its own notification obligations under Art. 33 DSGVO.
  5. to support the Client in fulfilling requests and claims of data subjects (Art. 12 et seq. DSGVO).
  6. to support the Client with data protection impact assessments and consultations with the supervisory authorities (Art. 35, 36 DSGVO); for the processing under § 2 para. 2 and § 5a, it provides the Client on request with a description of the processing, its risks and the measures under Annex 1.
  7. after completion of the provision of the processing services, to return or delete all personal data at the Client's choice, unless there is an obligation to store the data under Union law or the law of the Member States.

§ 4 Obligations of the Client

The Client is the controller within the meaning of Art. 4 No. 7 DSGVO. In particular, the Client is obliged:

  • to ensure the lawfulness of the processing (legal basis, obtaining consents where applicable), and for data under § 2 para. 2 also a legal basis under Art. 9 para. 2 DSGVO, for data of its employees as a rule Art. 9 para. 2 lit. b DSGVO;
  • to safeguard the rights of data subjects (access, rectification, erasure, objection) and to inform its employees about the processing of their data in accordance with Art. 13 and 14 DSGVO, including transmissions under § 5a;
  • to issue instructions clearly and in documented form;
  • to conclude with third-party services it connects, and with recipients to whom it has documents handed over, the agreements that data protection law requires for its relationship with them;
  • to inform the Contractor without undue delay if it detects errors or irregularities in the processing.

§ 5 Sub-Processing Relationships

(1) The Client consents to the use of the following sub-processors:

Sub-processor Service Location
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen Data center: servers, databases, object storage for files and backups, network Germany (Falkenstein)
Scaleway SAS, 8 rue de la Ville-l’Évêque, 75008 Paris AI-assisted receipt recognition (reading uploaded receipts) and speech recognition (“dictation”) France (Paris)
ALL-INKL.COM, Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf Sending emails from the platform, insofar as the Client has not set up its own mailbox for sending Germany (Dresden)
finAPI GmbH, Adams-Lehmann-Straße 44, 80797 München Account information service (retrieval of account balances and transactions), insofar as the Client connects a bank account Germany

For receipt recognition, the uploaded receipt (as an image, or as the text contained in the file) is transmitted to Scaleway in order to read out supplier, date, amounts, tax rates and a suggested account assignment. For speech recognition, the recording is transmitted via the Contractor's management platform in Falkenstein to Scaleway in order to turn it into text. Scaleway processes both in a data center in Paris; no transfer to a third country occurs. The results are suggestions and are reviewed and approved by the Client. The Contractor processes and stores all other data in Germany.

finAPI provides access to the bank account as a payment service provider authorized and supervised by the German Federal Financial Supervisory Authority (BaFin) (account information service under the German Payment Services Supervision Act, ZAG). The Client enters the bank credentials and the confirmation towards the bank exclusively in finAPI's form or with its bank; the Contractor does not receive them. Insofar as finAPI fulfills its own statutory obligations as a payment service provider, it processes the data under its own responsibility in accordance with its terms and privacy notices.

(2) The Contractor will announce new sub-processors in text form at least 30 days before their use. The same applies if a sub-processor is to take over a service not named in paragraph 1. The Client can object within 14 days; in this case, the Client can terminate the contract extraordinarily.

(3) The Contractor contractually obligates the sub-processors to a level of protection that at least corresponds to that of this DPA.

(4) Third-party services that the Client connects itself. Services with which the Client itself has a contract and which it connects in ZepDesk with its own access or names as a recipient are not sub-processors within the meaning of this agreement, in particular:

  • its online shops, marketplaces, point-of-sale systems and payment services, such as Shopify, WooCommerce, Ecwid, Billbee, Stripe, PayPal, PayPal Point of Sale (formerly Zettle), SumUp and its own Mollie account;
  • its file storage services from which it has files taken over as receipts, such as Google Drive, OneDrive and Dropbox;
  • its previous or additional accounting software from which it has data imported, such as Lexware Office and sevDesk;
  • its HR software from which it has data imported for payroll, such as Personio;
  • providers of AI language models that it connects in the AI assistant with its own login, such as an account with OpenAI or Anthropic, or with its own key;
  • the targets of webhooks it creates, such as Make, Zapier or its own systems;
  • apps of developers to which it consents in ZepDesk through its Administration (ZepDesk Developers); the developer processes the data as its processor or as an independent controller, as stated for the app;
  • its bank, if it connects it directly with its own key, such as Qonto;
  • recipients to whom it has documents handed over, in particular its tax advisor, who processes them under its own responsibility;
  • the tax authorities to which it has tax data transmitted (§ 5b);
  • the social insurance institutions and their receiving offices to which it has data transmitted (§ 5a).

The Contractor retrieves data from these services and transmits data to them only insofar as the Client has instructed it to do so: by switching on the connection, by creating the webhook, by consenting to a developer app or by approving the individual handover. The Client itself is responsible for its relationship with these services; its contracts with them and their terms apply. If the Client disconnects a connection, the Contractor no longer retrieves anything there.

Data retrieved. Only what the respective connection needs is retrieved, in particular payments, refunds, fees withheld and payouts from payment services, additionally the sales receipts with items and payments from point-of-sale systems, orders with line items, prices and taxes as well as the name, email address and billing address of the buyers from online shops, and booked appointments with the name and contact details of the person booking from scheduling tools, and from HR software the name, entry date, leaving date, weekly hours and position of the employees and, only if the Client switches it on, approved periods of incapacity for work with start and end, without remarks and without the type of absence. From PayPal Point of Sale, these are the movements of the balance (time, amount, type and identifiers) and the sales receipts with items and payments, including the reference number of a card payment and an invoice number typed in there. From file storage services, it is the files the Client designates for this, each with name, size, time of last change, checksum and content: from Google Drive only files and folders that the Client shows ZepDesk in Google's picker, together with their identifier and type and the display name of the Google account; from OneDrive the folder the Client names; from Dropbox the folder “Apps/ZepDesk” with the path of the files, together with the name and email address of the Dropbox account, which Dropbox always provides. The permission Microsoft grants for OneDrive covers all files of the account; the Contractor reads only the named folder. The Contractor writes to the Client's account with the service only if the Client itself switches on an automation for this at the connection, and only what this automation describes there, such as marking a time entry as billed or moving a booked receipt into a folder. Every automation is off by default. If the Client disconnects a connection that is based on a login with the service, the Contractor revokes the access there insofar as the service allows revoking this access alone via its interface. With Google, there is no revocation, because there it would end all access of the same person to ZepDesk, including for other companies. Otherwise, the Client can revoke the access in its account with the service.

Where the credentials are kept. A key that the Client enters for a service is kept encrypted by the Contractor in the Client's instance. If the Client logs in with the service, the access token is likewise kept encrypted in its instance. If the login runs via the Contractor's connection service (connect.zepdesk.de), the connection service keeps the authorization including the refresh token encrypted for as long as the connection exists (Annex 1 No. 6.2) and gives the instance only the currently valid access token.

If the Client enters a key on the input page of the connection service, the connection service only passes it through: it stores it encrypted, the Client's instance collects it and keeps it as described above, and right after collection the Contractor deletes the connection in the connection service, or, if that fails, at the latest in the next hourly clean-up run. The key is finally removed there after about one day at most; until then it remains stored in encrypted form. In the encrypted backups created during this time it remains until these are deleted after 30 days (Annex 1 No. 6.3).

The connection service communicates with the service only to complete the login, to refresh the token and, where provided for, to check an entered key once for validity. The revocation upon disconnection is sent by the Contractor's management platform. The data itself is retrieved by the instance. For a connection based on a login, the Contractor records on its management platform the provider, the account with the provider, the customer, the instance, the permissions granted and the times of connecting and disconnecting. In addition, the connection service keeps logs of connecting, refreshing and errors in doing so for no more than 14 days (Annex 1 No. 6.2).

The connection service runs on the server of the Contractor's management platform at Hetzner Online GmbH in Falkenstein; its backups are kept there and in the object storage of Hetzner Online GmbH in Falkenstein, its logs only on this server. It is based on the free software Nango, which the Contractor operates itself. The manufacturer of Nango receives neither credentials nor any other data: the components that could send data to it, its own login interface and usage statistics, are not in operation. No further sub-processor arises from this.

(5) Likewise not sub-processors are Mollie B.V., which only collects the Contractor's fees, and Let’s Encrypt (Internet Security Research Group, USA), which issues TLS certificates and receives only domain names for this purpose. If the Contractor itself provides access to an AI provider, paragraph 2 applies to that provider.

§ 5a Transmission to Social Insurance

(1) Subject matter. If the Client gives the Contractor a separate transmission mandate, the Contractor transmits data in the Client's name to social insurance institutions and their receiving offices and retrieves their responses, in each case to the extent stated in the transmission mandate, in particular:

  • the financial accounting data for the electronically supported employer audit via the Data Centre of the Pension Insurance (Datenstelle der Rentenversicherung) to the competent pension insurance institution (§ 28p para. 6a SGB IV);
  • notifications, contribution statements and applications from payroll to the health insurance funds and the other competent bodies (§§ 28a, 28f SGB IV, Expenditure Compensation Act);
  • the retrieval of incapacity for work data from the health insurance funds (§ 109 SGB IV).

In doing so, the Contractor acts as a third party within the meaning of § 95 para. 1 sentence 3 and § 109 para. 1 sentence 4 SGB IV and appears towards the receiving offices as sender with its own certificate. The Client remains the party obliged to report; it remains fully liable towards the institutions for fulfilling its obligations (§ 95 para. 1 sentence 3 SGB IV).

(2) Approval. The Contractor transmits only what the Client has approved in ZepDesk in the individual case. Only a human can approve, not an API key and not the AI assistant. With the transmission mandate, the Client instructs the retrieval of the responses and their delivery into the Client's instance; they run as long as the mandate exists.

(3) Recipients. The social insurance institutions, the Data Centre of the Pension Insurance and the other receiving and forwarding offices are recipients to which the Client has data transmitted, and not sub-processors (§ 5 para. 4). The Contractor's certificate is issued by ITSG GmbH (Informationstechnische Servicestelle der Gesetzlichen Krankenversicherung); for this it receives details about the Contractor, but no data from the notifications and no data of the Client's employees.

(4) Purpose limitation and secrecy. § 78 SGB X applies at the Client to the responses of the institutions and their receiving offices, in particular the incapacity for work data. The Contractor processes them only to deliver them to the Client and to keep them available in the Client's instance, and only for the purpose for which the institutions transmitted them (§ 78 para. 1 sentence 1 SGB X). It keeps them secret to the same extent as the institutions themselves (§ 78 para. 1 sentence 3 SGB X, § 35 SGB I). It does not analyze them and does not use them for its own purposes. They do not reach the AI assistant, nor any provider the Client has connected there.

(5) Storage in the transmission service. The Contractor transmits via a transmission service of its own in its Kubernetes cluster at Hetzner Online GmbH (§ 5 para. 1). No consignment is stored there unencrypted on a data carrier. A consignment remains stored in encrypted form until the receiving office has confirmed or rejected it, a response until the Client's instance has collected it; the service then deletes it. For evidence, only details of the consignment remain: instance, establishment number, procedure, file number, checksum, identifier at the receiving office, status and times, for as long as the Contractor retains the transmission mandate.

(6) Identification. Before the Contractor transmits for the Client, it identifies the Client and the persons who give the transmission mandate on its behalf, at the level of assurance that the receiving offices require of a reporting office (Meldestelle). The Contractor processes these details under its own responsibility; its privacy policy provides further information.

(7) End. If the Client revokes the transmission mandate or the main contract ends, the Contractor no longer transmits anything for the Client.

§ 5b Transmission to the Tax Authorities

(1) Subject matter. If the Client gives the Contractor a transmission mandate in ZepDesk under § 87d para. 1 AO, the Contractor transmits the tax data named therein to the tax authorities with its own certificate as data transmitter. The Client remains the taxpayer. The transmission mandate governs subject matter, approval, identification and termination; this Agreement additionally governs the processing of the Client's data.

(2) Approval. The Contractor transmits only a data record to which a person of the Client has expressly consented in ZepDesk, and only in exactly the version consented to. Only a human can approve, not an API key and not the AI assistant. Until the tax authorities have accepted a first transmission for the Client, the Contractor additionally approves each transmission; in doing so it checks only whether it matches the transmission mandate (Client, tax number, data type), not its content.

(3) Storage. The Contractor transmits via its own service in its Kubernetes cluster at Hetzner Online GmbH (§ 5 para. 1). It deletes the transmitted file and the responses of the tax authorities on its management platform 30 days after handing them over to the Client's instance; in the instance they remain with the Client.

(4) Records. The Contractor records the details of the Client's identification and of each transmission under § 87d para. 2 AO as a controller in its own right and retains them for five years, starting after the end of the year of the last transmission; the transmission mandate and its privacy policy provide further details.

(5) End. If the Client revokes the transmission mandate, its validity expires or the main contract ends, the Contractor no longer transmits anything for the Client.

§ 6 Technical and Organizational Measures (TOM), Annex 1

6.1 Confidentiality (Art. 32 Abs. 1 lit. b DSGVO)

  • Physical access control: The servers are located in data centers of Hetzner Online GmbH in Falkenstein (Germany), which are certified to ISO/IEC 27001. Hetzner secures physical access. The Contractor does not operate its own server rooms.
  • System access control: Users log in via the central login with a password, depending on the setting with a second factor (confirmation code by email or authenticator app); the login pages are protected against automated login attempts. Passwords are stored only as a salted hash (PBKDF2-SHA256). Only administrators of the Contractor have administrative access to servers, cluster and databases. The connection service can be reached from outside only through an upstream proxy that lets through solely the paths for logging in with the service, entering a key and returning, and throttles requests per address of the caller. Its components are bound only to the loopback address of the server; its programming interface requires a secret key. Its administration interface can be reached only by persons logged in to the Contractor's management platform with the System Manager role: the management platform issues a ticket for this that is valid for 60 seconds and only once and is bound to user and session; access ends after 8 hours at most, upon logout or when the role is withdrawn. Staff do not receive an account of their own in the connection service. Its database and its log storage are attached solely to internal networks without a connection to the outside.
  • Data access control: Role-based permission system within the customer instance; the Client assigns the roles. Employee data and payslips, including the data under § 2 para. 2, are accessible in the instance only to the Administration and Tax roles; the Read-only role sees only totals without reference to individuals. SEPA files for the credit transfer of net wages and for direct debits can be created only by a human with the Administration role who is signed in via the browser or the ZepDesk app; an API key, an MCP access and the AI assistant cannot do so. Handovers to named recipients are likewise approved only by a human with the Administration role, not by an API key and not by the AI assistant. Transmissions to the tax authorities are approved only by a human (§ 5b para. 2). Whoever holds the Administration role alone additionally confirms the approval of a handover with a one-time code. A payment is executed only once the Client itself submits the file to its bank. The Contractor accesses the instance only for maintenance, troubleshooting or on instruction. In the connection service, staff with the System Manager role set up the connections to the services; only they read the logs of the connection service. They are instructed not to change the Client's connections, not to copy tokens from them and to view them only where necessary for a test or a fault. They are not permitted to delete a connector, which would end all connections to that service.
  • Separation control: For each Client, its own namespace in the Kubernetes cluster with its own network rules (incoming connections only via the central ingress, no connections between instances), its own database schema on the shared database server with its own database user that may only access this schema, and its own path in the object storage for files and backups. In the connection service, each connection carries the customer and the instance; an access token is given only to the instance for which the connection was created.

6.2 Integrity (Art. 32 Abs. 1 lit. b DSGVO)

  • Transfer control: Connections to the platform only encrypted (TLS 1.2 or 1.3; the servers reject older versions). Stored credentials for third-party services are encrypted in the instance with the key of the respective instance. In the Contractor's connection service (§ 5 para. 4), the credentials are stored centrally and encrypted with AES-256-GCM; the key is kept separately from the service's database and never in its backups. Three different keys apply to the credentials, to the backups and to the access to the object storage. A monitoring check verifies every five minutes that the connection service runs with its key and reports otherwise (No. 6.3). If the Client disconnects a connection, the connection service permanently deletes the credentials after about one day at most; the same applies to a key passed through after its collection (§ 5 para. 4). They remain in the encrypted backups until these are deleted after 30 days. For the paths for logging in and entering a key, the access logs of the web server on the server of the management platform contain neither authorization codes nor session tokens.
  • Logs of the connection service: The connection service logs connecting, refreshing and errors in doing so in a separate store on the server of the management platform: times, service, identifier of the connection, success or error including the error message of the service, and for a login the redirect address to the service and the one-time return code, which is used up with the return. If a service gives an unreadable response to a token request, this response including the token may appear in the log. The Contractor does not pass names or email addresses of users to the connection service. Each entry is deleted after 14 days at most; two independent deletion runs ensure this. The logs are in no backup, cannot be reached from outside, and only the System Manager role can read them via the administration interface (No. 6.1). Unlike the credentials, they are not encrypted at rest; they are protected by the access rights on the server.
  • Input control: Changes to receipts, bookings, master data and payroll data are logged with time and user; approvals of transmissions to the tax authorities are stored with the consenting person, a checksum of the file and the transmission record. Approvals of handovers are stored with person, time and a checksum of the approved content. A changed bank account of a business partner only takes effect once the Administration role confirms it; until then, payments to that partner are blocked. Every request to the administration interface of the connection service is logged with the user of the management platform, every change there additionally with user, time and type of change in the audit log of the management platform, as are opening it and every refused access; secrets never appear there.

6.3 Availability and Resilience (Art. 32 Abs. 1 lit. b DSGVO)

  • Availability control: Daily automatic backup of each instance (database and files) to the object storage in Falkenstein; a daily check reports when no new backup has arrived there for an instance for more than two days. The application runs in a Kubernetes cluster with several nodes; the status page status.zepdesk.de shows the state of the services.
  • Backup of the connection service: Nightly backup of its database, encrypted with AES-256 under a key of its own that is not the key of the credentials; neither of the two keys reaches the object storage. Each backup is cross-checked after writing. A copy goes off-site to the object storage of Hetzner Online GmbH in Falkenstein, into an area of its own next to the backups of the instances; it is checked against its checksum after uploading. In the object storage, the copies are deleted after 30 days, and so are the backups on the server, where the seven most recent always remain.
  • Backup of the management platform: The databases on the server of the management platform are backed up on this server every six hours.
  • Alerting: If one of these backups or an off-site copy fails, if the monitoring of the connection service finds an error or if the watchdog of the management platform itself fails, the server automatically reports this by email to the Contractor's operations.
  • Recoverability: Restoration is made from the daily backup. In the event of damage, changes since the last backup may be lost. Restoring the connection service from the object storage has been tested.

6.4 Procedures for Regular Review (Art. 32 Abs. 1 lit. d DSGVO)

  • Documented procedures for security incidents and data breaches
  • Review and adjustment of this annex in case of significant changes to the platform

6.5 Transmission to Social Insurance (§ 5a)

In addition to Nos. 6.1 to 6.4, the following applies to transmission as soon as the Contractor offers it:

  • Encryption: Consignments are signed and encrypted in accordance with the social insurance requirements for data transmission (§ 95 para. 1 sentence 2 SGB IV). Between the instance and the transmission service and from the service to the receiving offices, there are only encrypted connections (TLS 1.2 or 1.3).
  • Access: The transmission service runs in a separate, isolated area of the cluster and cannot be reached from outside. It accepts consignments only from instances for which a valid transmission mandate exists; an instance transmits only under its Client's establishment number and receives only that Client's responses. The key to the certificate is kept only in the transmission service and, separately from it, as an encrypted backup; the management platform cannot read it.
  • Storage and logs: No plain text on data carriers; consignments and responses are stored encrypted and deleted in accordance with § 5a para. 5. Logs name the field and the record, never their content. The management platform sees only statuses and counters, no employee data.
  • Traceability: For each consignment, the approving person, the time, a checksum of the content, the identifier at the receiving office and the status are stored.
  • Purpose limitation: Responses do not reach the AI assistant and are not analyzed (§ 5a para. 4). Anyone at the Contractor who can handle them has been informed beforehand of the obligations under § 78 SGB X (§ 3 No. 3).

§ 7 Client's Audit Rights

(1) The Client has the right to verify the Contractor's compliance with its data protection obligations by means of random checks. Upon request, the Contractor provides suitable evidence (e.g. TOM documentation, certificates of the sub-processors).

(2) On-site inspections by the Client are permitted with reasonable advance notice (min. 14 days), during normal business hours and while safeguarding operational procedures. The Client bears the costs of the on-site inspection itself.

§ 8 Liability

The parties are liable for damages arising from the processing of data within the meaning of this DPA in accordance with Art. 82 DSGVO. The limitation of liability in § 9 of the main contract (GTC) remains unaffected, insofar as it is permitted under the DSGVO.

§ 9 Final Provisions

(1) This DPA ends upon termination of the main contract. Data protection obligations that by their nature continue beyond the termination of the contract (in particular deletion obligations) remain unaffected.

(2) In the event of conflicts between this DPA and the main contract, the DPA takes precedence in matters of data protection.

(3) German law applies.

Order processing under Art. 28 DSGVO.

Legal texts are not an end in themselves: every version is versioned, dated and traceable. The process behind it in four steps.

STEP 1
Order placed
STEP 2
Measures agreed
STEP 3
Sub-processors named
STEP 4
Signed in the account
AUDIT TRAIL ................

The binding version is the one stated above with its effective date.