> 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/delete-call-data.md).

# Delete call data

Here you can find out how to automatically delete call data from Contact Center, AI Agents and Conversation Intelligence after a retention period or delete it individually manually.

As a provider, sipgate provides you with the tools that allow you, as the operator, to easily and independently fulfill your legal obligations, in particular the right to erasure under Art. 17 GDPR.

#### Which data does this article apply to?

This article applies exclusively to **Call Events**, which are created as part of Contact Center, AI Agents and Conversation Intelligence and stored in the Data Hub.

This data is completely independent of the inboxes stored in your sipgate user account (the “app”). You manage the inboxes in the app (outgoing, missed and accepted calls, faxes, SMS and voicemail transcripts) via a separate setting: [app.sipgate.com/settings/dialog/eventlistLifetime](https://app.sipgate.com/settings/dialog/eventlistLifetime).

Deleting Call Events in the Data Hub has no effect on Call Events in the app, and vice versa. If you want to make sure that no data about a call exists anywhere, you must check both locations separately and delete them if necessary.

#### What is included in a Call Event?

When a Call Event is deleted, it is **completely** deleted, not just individual components. This includes in particular:

* the transcript
* the recording, provided the call was recorded via the cloud telephone system
* extracted values from custom fields
* all other data derived from the call that is stored in the Data Hub

There is no intermediate layer that remains after deletion. A deleted Call Event no longer exists in any of the forms mentioned.

#### How does automatic deletion after the retention period work?

You can set a retention period: Open **Conversation Intelligence → Settings** and click in the **Results** section at **Saving results** on the gear icon. Once this period has expired, the affected Call Events are automatically and permanently deleted (hard-delete) without any manual action required.

* The setting currently applies **account-wide**, meaning uniformly for all Channels and AI Agents. An individual period per channel or agent is not yet possible.
* The default value is 24 months, but it can be configured freely.

<figure><img src="https://702748557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcPbcWJCrFgi79rVOgXbo%2Fuploads%2FDmQ0kknudD1u42ztKgvS%2F10-einstellungen-speichern-von-ergebnissen.png?alt=media&amp;token=abffa44a-79fb-4a74-8220-3f7a8863e193" alt=""><figcaption></figcaption></figure>

#### How do I manually delete individual calls?

You can delete individual calls at any time, specifically and immediately, for example if an end customer asserts their right to erasure under Art. 17 GDPR.

{% stepper %}
{% step %}

## Find the relevant call

Find the relevant call in the [Data Hub](broken://pages/1bf15d74eaab346d3bdd1fccf8e4b74dd27ca815), e.g. using the filter function by phone number, date or contact.
{% endstep %}

{% step %}

## Select “Delete”

Open the menu (three dots) in the call’s row and select **Delete**.
{% endstep %}

{% step %}

## Confirm the permanent deletion

You will be warned several times that the deletion **is permanent** before it is carried out.
{% endstep %}

{% step %}

## Call Event is removed

After confirmation, the Call Event is completely and irretrievably removed.
{% endstep %}
{% endstepper %}

This function is self-service: you do not need support from sipgate Support. This is especially relevant when an end customer requests deletion from you, because you can handle the request directly and without detours via sipgate yourself.

#### What does “permanently deleted” mean?

Both automatic and manual deletion are hard-deletes: The data is irretrievably removed. There is no option to restore it and no backup copy that sipgate could access. Therefore, make sure you really want to delete it before confirming a deletion.

#### What is my role as controller?

In terms of data protection law, sipgate is the processor for you. You yourself are the controller vis-à-vis your end customers. If an end customer requests deletion of their data from you, you are generally responsible for fulfilling this request. The functions described in the Data Hub provide you with the technical means to do this without having to contact sipgate. More on [Data protection](broken://pages/825b447ea55cbbf11355bd3143c076c3cf10c133).

#### Good to know

* **No log yet:** The Data Hub currently does not provide a viewable log of when which Call Events were deleted. If you need to document for internal record-keeping or audit purposes when you carried out which deletion, please keep this yourself for now, e.g. in a separate deletion log.
* **Account-wide period:** Automatic deletion can currently only be set for the entire account, not separately per channel or AI agent.
* **Independent of the app:** Deletion in the Data Hub does not affect the inboxes in your sipgate user account.
* **No partial deletion:** It is not possible, for example, to delete only the recording or only the transcript of a call and keep the rest. Deleting a Call Event always affects all associated data together. This also applies to recordings you created via the cloud telephone system.

#### Frequently asked questions

<details>

<summary>Do I need to contact sipgate if an end customer requests deletion of their data?</summary>

No. You can search for and delete the relevant call yourself in the Data Hub.

</details>

<details>

<summary>Can a deletion be undone?</summary>

No. Both automatic and manual deletions are final (hard-delete).

</details>

<details>

<summary>Does deletion also affect my call lists in the sipgate app?</summary>

No. Both systems are independent of each other and must be managed separately.

</details>

<details>

<summary>Is there proof that a deletion took place?</summary>

Currently not in the Data Hub itself. If you need proof, please document the deletion independently, for example in a separate deletion log.

</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.de/conversation-intelligence/conversation-intelligence-en/delete-call-data.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.