> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/privacy-terms-and-conditions-and-dpa/faq-datenschutz.md).

# Privacy FAQ

### AI Regulation (AI Act)

<details>

<summary>Is the AI Agent GDPR-compliant</summary>

Yes, all data is processed and hosted in the EU.

</details>

<details>

<summary>Which provisions of the EU AI Act apply to AI agents, and which risk category do they fall into?</summary>

sipgate AI Agents generally fall under the "limited risk" category pursuant to Art. 50 of the AI Regulation. For systems in this category, transparency obligations apply primarily. The AI Regulation classifies systems for direct interaction with natural persons (such as voice agents) as subject to transparency obligations, but not as high-risk systems.\
The AI Act has been in force since 1 August 2024; the transparency obligations under Art. 50 apply from 2 August 2026.

</details>

<details>

<summary>Must the AI Agent actively point out at the start of a conversation that it is an AI-supported dialogue, and in what form?</summary>

Yes. Under Art. 50(1) of the AI Act, providers of AI systems intended for direct interaction with natural persons must design them so that those persons are informed that they are interacting with an AI system. The notice must be clear, unambiguous, and transparent, at the latest at the first interaction. An exception exists only if this is obvious from the context. sipgate ensures by default that the AI Agent outputs a pre-formulated notice (greeting text) at the beginning of each conversation, which clearly discloses the AI-supported nature of the dialogue. This notice is technically fixed at the start of the conversation and cannot be skipped. The notice must be reproduced in the stated wording regardless of language setting and meets accessibility requirements.

</details>

<details>

<summary>What fines can be imposed for violations of the AI Act's transparency obligations?</summary>

Violations of the transparency obligations under Art. 50 of the AI Act can be punished in accordance with Art. 99(4) of the AI Act with fines of up to EUR 15 million or 3% of the company's global annual turnover (whichever is higher). The fines are imposed by national supervisory authorities. It should be noted that responsibility for complying with the transparency obligations lies with the operator of the AI system (the customer), while sipgate, as the provider of the AI system, provides the technical prerequisites.

</details>

### Data protection (GDPR)

<details>

<summary>Which legal basis applies to the processing of conversation data by the AI Agent?</summary>

The processing of conversation data can be based, for example, on Art. 6(1)(a) GDPR (consent) or Art. 6(1)(b) GDPR (performance of a contract), depending on the specific use case. For inbound calls in customer service, processing may be necessary for performance of a contract or for taking steps prior to entering into a contract.

</details>

<details>

<summary>Is the caller's voice biometric data within the meaning of Art. 9 GDPR, and does a company therefore require explicit consent for this?</summary>

The human voice can be classified as biometric data within the meaning of Art. 4 No. 14 and Art. 9 GDPR if it is processed with special technical procedures for the unique identification of a person. The key factor is the purpose of the processing: if the voice is used merely for speech recognition and conversation handling (without biometric identification), Art. 9 GDPR does not apply. sipgate AI Agents use voice data exclusively for conversation processing, not for biometric identification. Explicit consent under Art. 9(2)(a) GDPR is therefore not strictly required.

</details>

### Data processing

<details>

<summary>Does sipgate use our customers' data for training or machine learning?</summary>

No. sipgate does not use customer data for training AI models or machine learning. This is contractually excluded with all AI providers (in particular OpenAI). The data is used exclusively to provide the commissioned services and is deleted or anonymized after processing. This arrangement is part of the technical and organizational measures and documented in the DPA.

</details>

<details>

<summary>Can sipgate indemnify us against liability towards third parties, especially in the event of violations of the AI Act and GDPR?</summary>

An indemnification by sipgate is not предусмотрed, as the customer, as controller, is generally responsible for the lawful use of the AI Agent. This corresponds to the legal allocation of roles under the GDPR and the AI Act.\
sipgate does, however, undertake to provide the technical and organizational prerequisites for lawful use and to support the customer in complying with its obligations within the framework of the DPA provisions. The systems provided are generally designed so that they can be used in compliance with the GDPR:\
\
(1) In our data processing agreement (DPA), the details of data processing are regulated. With our subcontractors and partners, corresponding agreements are in place that ensure lawful data processing.\
\
(2) We also point out that the assistant clearly points out, or can point out, at the beginning of each conversation that it is an AI (for more information, see our [Privacy policy](https://firebasestorage.googleapis.com/v0/b/ai-frontdesk-web-static/o/datenschutzerklaerung.pdf?alt=media\&token=bf03f619-6dfa-402d-8396-2db340462f10) as well as in the [data processing agreement](https://firebasestorage.googleapis.com/v0/b/ai-frontdesk-web-static/o/auftragsverarbeitungs-vertrag.pdf?alt=media\&token=1e567ab2-d173-4b8e-b557-68c85ea66416))\
\
For cases in which a violation is attributable to errors or breaches of duty by sipgate, sipgate is liable in accordance with the contractual liability provisions.

</details>

### Liability & responsibility

<details>

<summary>Who is liable if the AI Agent makes mistakes, provides incorrect information, or violates the AI Regulation or the GDPR?</summary>

Liability is determined by the allocation of roles between controller and processor: The customer, as operator of the AI Agent, is the controller within the meaning of the GDPR and the AI Act and is therefore generally responsible for lawful use. This includes, in particular, compliance with transparency obligations, lawful data processing, and ensuring that the AI Agent is configured appropriately for its intended purpose. sipgate is liable as processor for breaches of duty in the context of processing on behalf of a controller (Art. 82 GDPR).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sipgate.com/documentation/en/privacy-terms-and-conditions-and-dpa/faq-datenschutz.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
