> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Closing your account

> How to ask for your account to be closed, what is deleted from your workspace, and what to export first.

Closing an account is done by email. There is no button in the console. Write to [contact@deepblocker.ai](mailto:contact@deepblocker.ai) from the workspace owner's address and ask for the workspace to be closed.

> [!WARNING]
>
> Deleted data cannot be recovered. Export what you need first.

## Before you write

* Export the results you want to keep. The auditor pack and the printable report are the two documents built for this. See [Export for auditors](https://docs.deepblocker.ai/vishing/results/auditor-pack.md) and [The workspace Reports page](https://docs.deepblocker.ai/vishing/results/reports-page.md).
* Tell your team. Members lose access when the workspace goes. See [Invite your team and roles](https://docs.deepblocker.ai/account/team.md).
* Check your licence term and notice period. See [Buying and renewing](https://docs.deepblocker.ai/account/billing.md).

## Steps

**1. Write to us**

Email [contact@deepblocker.ai](mailto:contact@deepblocker.ai) from the workspace owner's address. Include the workspace name, shown on the **Workspace** tab of the Account page. See [Your workspace](https://docs.deepblocker.ai/account/workspace.md).

**2. We confirm what will be deleted**

The deletion is checked in a dry run first. It lists what would go: how many campaigns, calls, contacts, attackers, voices, recordings and research profiles. Nothing is deleted at this step.

**3. We delete**

Once you confirm, the deletion runs and we tell you when it is done.

## What is deleted

| Data | What goes |
| - | - |
| Cloned voices | The voice at the voice provider, its stored sample, and our record |
| Campaigns | Every campaign, with its queue and the memory the caller built up |
| Recordings | Every call recording in storage |
| Call results and transcripts | Every result and every transcript |
| People | The whole contact list |
| Attackers | Every attacker persona |
| Research profiles | Every target exposure profile |

Deletion runs per workspace. Nothing in another workspace is touched.

## What this does not cover

* Executive voice consents are withdrawn by the executive through their own consent link. See [Clone an executive's voice with consent](https://docs.deepblocker.ai/vishing/executive-voice-consent.md).
* Recordings are deleted after 90 days in any case. See the [FAQ](https://docs.deepblocker.ai/vishing/faq.md).
* For a request about your own personal data, such as access or erasure, write to [privacy@deepblocker.ai](mailto:privacy@deepblocker.ai). The [privacy policy](https://deepblocker.ai/privacy) sets out your rights.

## Problems

> [accordion] I am not the workspace owner
>
> Ask the owner to send the request, or copy them in. The owner is the person who created the workspace.

> [accordion] I only want some data gone, not the account
>
> Say so in the email. Deleting one campaign, voice or profile is done from the console; write to us for anything else. See [Support and contact](https://docs.deepblocker.ai/support.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.