Amazon Web Services EMEA SARL
- Purpose
- Main infrastructure for Gateway and MCP
- Processing location
- Frankfurt, Germany
- Scope
- Product hosting; also our own support and administration systems.
Klardaten Trust Center
How we protect your DATEV data.
Learn how your DATEV data is transferred, who can access it and which safeguards apply to Gateway and MCP.
Updated: 27 September 2026
- Hosted in FrankfurtMain infrastructure for Gateway and MCP
- Professional secrecy · § 203Contractual commitments to protect professional secrets
- DPA and security measuresDocuments available without registration
Your DATEV system is not exposed to the public internet.
Controlled access
Data requests require an approved connection and the corresponding permissions.
Encrypted transfer
The connection between your DATEV environment and Klardaten is encrypted.
You choose the recipient
The application you authorize receives the requested data. The connection and configured profile determine its access.
When you connect an AI application, the application you choose receives the requested data.
The path between DATEV and your application
Klardaten connects your DATEV system to the application you authorize. The connection and the configured profile’s permissions determine which data it can retrieve.
Your DATEV environment
DATEV system and connector
Connection initiated by the connector
Encrypted
Klardaten
API / MCP
Checks access and forwards requests
Encrypted
Your application
Receives the requested data
Credentials stored only locally
Access requires authorization
Approved by you
Technical details
TLS · TCP 443
The connector establishes the encrypted connection to Klardaten. Requests and responses travel over this connection. You do not need to open a port for incoming connections in your firewall.
Your DATEV and Windows credentials are stored exclusively on your local Windows system — never by Klardaten. When you set up a profile through Klardaten, the credentials are transmitted to your connector.
Your DATEV system: DATEVconnect in your environment
Klardaten connector: Runs on your Windows system
TLS / HTTPS
Access is limited to the authorized DATEV connection. The DATEV permissions of the configured user profile apply.
Does this make my DATEV data publicly accessible on the internet?
No. The connector does not expose your DATEV server to the public internet. It establishes an encrypted, outbound connection to Klardaten. Data requests require an authorized connection and use the permissions of the configured profile.
The authorized connection, profile and permissions determine which data an application can retrieve.
With MCP, the AI application you choose receives the inputs and results of tool calls. Whether it stores this data, where it processes it and how it uses it depend on your agreements and settings with the provider.
Optional document search keeps extracted text and a search index locally on the connector host. Retrieved passages are sent through Klardaten to your connected application; disabling search retains the local index.
Common questions from tax firms
Does connecting an AI application automatically send it all my client data?
No. Connecting alone does not transfer your entire DATEV data set. The AI application retrieves data through individual requests and receives the results. The configured DATEV/Windows profile limits what it can access. A profile with broad permissions also allows broader requests; use only the permissions needed for the intended task.
Can the AI provider use my client data to train its models?
Clarify directly with your chosen AI provider whether and how your data may be used for model training. Its contractual terms and the settings of your specific service apply.
Privacy and your chosen AI providerCan MCP also change data in DATEV?
MCP supports reading data and selected write operations. Available actions depend on the DATEV module and the configured profile’s permissions. Certain write permissions need additional approval when connecting. Write operations are logged. The product scope lists the supported functions for each module.
Read and write functions by DATEV moduleSecurity measures in detail
Find details about each safeguard below. The contractually agreed measures are set out in Annex 2 of the data processing agreement.
Encryption and credentialsEncrypted connections and exclusively local storage of your DATEV and Windows credentials.
Your DATEV and Windows credentials are stored exclusively on your local Windows system — never by Klardaten. When you set up a profile through Klardaten, the credentials are transmitted to your connector. The connector protects stored credentials with Windows DPAPI. Its connection to Klardaten uses TLS. The contractual TOMs describe encryption, key management and access protection requirements. Your Windows system also needs protection against unauthorized access.
Authentication and access permissionsSigning in and being authorized to use a DATEV connection are separate checks.
Applications authenticate with the Gateway API using JWT access tokens with refresh tokens or API keys sent as bearer credentials. Access to a specific customer instance also requires the corresponding authorization. The selected connection and configured DATEV/Windows user profile determine which DATEV data is accessible. Profiles and service accounts should have only the permissions needed for the integration. If several people use the same technical profile, they all have that profile’s permissions. Certain MCP write permissions need additional approval when connecting. Write operations are recorded in the audit log.
Customer separation and internal accessAccess is tied to the authorized customer instance and profile.
Klardaten checks access permissions for each requested customer instance. Signing in alone does not grant access to other customer connections. Within a connection, the DATEV permissions of the configured profile apply. The contractual TOMs require individual user accounts, multi-factor authentication and permissions based on responsibilities for Klardaten production systems. Any access to customer content during support or incident handling must have a specific purpose. It is controlled and logged and, where required, authorized by the customer or based on a documented instruction.
Monitoring, backups and security updatesOur documented measures describe how we monitor operations, back up data and respond to incidents.
The TOMs describe centralized system and security-event monitoring, redundant backups across separate availability zones and regular recovery tests. Security patches are prioritized by severity and operational risk. These infrastructure backups do not replace backups of your own DATEV environment. The detailed contractual controls are available in Annex 2 of the DPA.
Confidentiality and organizational measuresThe contractual TOMs also cover permissions, devices and confidential information.
They cover confidentiality commitments and documented instructions, role-based permissions and access reviews. They also describe device encryption, screen locks and protected access to production systems. The complete measures are set out in Annex 2 of the DPA.
Privacy when using our products
Our privacy policy explains how we process data for the website, customer accounts, support and billing. Its section on Gateway and MCP describes product data, connection records and retention periods.
DATEVconnect Gateway
DATEV connections, permissions and technical operational data.
Product privacy noticeDATEVconnect MCP Server
Connections to your chosen AI applications, tool calls and sessions.
Product privacy noticeHosting and subprocessors
We operate the main Gateway and MCP infrastructure on AWS in Frankfurt. This overview distinguishes product hosting from other services listed in Annex 3 of the DPA.
Hetzner Online GmbH
- Purpose
- Backup infrastructure and internal test systems
- Processing location
- Nuremberg, Germany (Annex 3)
- Scope
- Subprocessor listed in the contract; use depends on the agreed service.
Microsoft Ireland Operations Limited
- Purpose
- Microsoft Azure / Azure OpenAI
- Processing location
- Germany / EU, potentially Sweden or France (Annex 3)
- Scope
- Planned for Klarvos. Klarvos is still in development.
We have an agreement with each of these subprocessors to protect professional secrecy under Section 203 of the German Criminal Code.
The DPA provides for at least 30 days’ notice before a new or materially changed subprocessor is used. Customers may object on substantial data protection grounds. Required contractual safeguards are put in place before processing starts.
An AI application you choose receives data as your selected recipient. This does not automatically make it a Klardaten subprocessor. Services used for our website, support and contract administration are described in the privacy policy.
Privacy for the website, contact and customer accountsContract documents
When processing DATEV data on your firm’s behalf, Klardaten acts as a processor. The DPA governs instructions, safeguards, and return and deletion of data when the engagement ends. The PDFs contain German and English versions.
For tax firms, the supplementary agreement under Section 203 of the German Criminal Code covers professional secrets, including client, tax and accounting information. It supplements the DPA. Both documents are available below for your records and review by your IT or data protection adviser.
Data processing agreement (DPA)Version: 1 July 2026 · TOMs in Annex 2, subprocessors in Annex 3 · PDFTechnical and organizational measuresVersion: 1 July 2026 · Annex 2 of the DPA, from page 12 · PDFProfessional secrecy obligationsVersion: 19 August 2026 · Supplementary commitments under Section 203 StGB · PDFPrivacy notices for our productsData categories, recipients, connection records and retention for Gateway and MCP
Report security incidents and vulnerabilities
Our documented procedure for security incidents sets out how we assess incidents, pass them to the responsible teams, document them and notify affected customers. Affected customers are informed without undue delay and supported with their notification obligations. If you suspect a vulnerability, email info@klardaten.com. Include the affected product, the time and the steps needed to reproduce the issue. Please do not send passwords, access tokens or client data. We will agree on a suitable way to exchange confidential information.
info@klardaten.com