> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/conversation-intelligence/conversation-intelligence-en/data-protection.md). # Data protection Conversation Intelligence processes potentially personal data. Here you can find out what you need to consider before and during use as an operator. The data comes from both your employees and your callers. As the customer, you are responsible for ensuring that use complies with the applicable data protection requirements. sipgate provides you with the technical tools for this, but the legal assessment and implementation are your responsibility. General information about AI features in the sipgate app can be found in the article [Data protection and AI features in the sipgate app](https://help.sipgate.de/cloud-telefonanlage/sipgate-nutzen/die-sipgate-app/datenschutz-und-ai-funktionen-in-der-sipgate-app).
Can I use Conversation Intelligence for performance monitoring? No. Conversation Intelligence is deliberately designed so that it cannot be used to monitor or evaluate the individual performance of individual employees. The product provides only aggregated business insights, no automated evaluations or scoring of individual persons. Circumventing this product design in order to monitor or evaluate individuals is not permitted.
How do I inform my employees? Before you activate Conversation Intelligence for a channel, you must inform the affected users (agents) in accordance with **Art. 13 GDPR** about the use, in particular that calls are transcribed and analyzed using AI and which data fields are collected in the process. Depending on the circumstances, their consent may also be required. As soon as Conversation Intelligence is activated for a channel, your employees will automatically see a corresponding notice when making phone calls via the sipgate app.
What applies to co-determination in the company? The introduction of Conversation Intelligence may touch on matters subject to co-determination, for example because employees' call data is processed. Therefore, clarify early and comprehensively with your employee representatives whether, and in what form, participation, co-determination or information rights exist under the Works Constitution Act or comparable regulations. This applies regardless of the fact that the product itself does not enable individual performance monitoring.
How do I inform callers? Callers must also be informed in an appropriate manner about the processing of their call data, for example by means of an announcement at the beginning of the call.
What legal basis do I need? For the processing of the call content, transcripts and custom fields extracted from them, you need a sound legal basis under **Art. 6(1) GDPR**. Also check whether a **data protection impact assessment** under **Art. 35 GDPR** is required for your use case.
How do I design my own custom fields in compliance with data protection law? If you define your own [Custom Fields](broken://pages/f5356f5e4741b153b3ec3ac8a330295c3b2cc309) fields, you are solely responsible for ensuring that they are compatible with applicable legal requirements, in particular data protection and employment law requirements. This applies both to fields suggested by sipgate and to fields you define yourself. In particular, avoid fields that allow conclusions to be drawn about the individual performance of individual employees.
How do I delete data? Learn how to delete individual call data or have it deleted automatically after a period of time in the article [Delete call data](broken://pages/d88f82b979701bcffdf03153c415a28c5f96c88d).
Who is responsible for what? sipgate is your processor and, in the context of Conversation Intelligence, provider of an AI-based product. The data protection responsibility lies with you as the operator of the AI-based product. sipgate does not review or advise on whether your specific use, including individual custom fields, is permissible under data protection, labor or co-determination law. You must carry out this assessment yourself.
--- # 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.de/conversation-intelligence/conversation-intelligence-en/data-protection.md?ask=&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.