All guides

Account and data deletion

Objective. Choose the correct deletion path for a bot, workspace, account, or connected WhatsApp number and know what each path affects.

Prerequisites

  • Workspace and account details for any email deletion request.

Choose the deletion scope

Start with Data deletion for the trust-page policy. This guide turns that policy into the operator actions below.

  1. 1To remove one bot, use that bot’s Delete action in Fluenta. Its deletion cascade removes that bot’s flows and conversations.
  2. 2Workspace deletion is handled by email request. Send the account email address and workspace name to [email protected]. Deleting a workspace cascades to its bots, flows, and conversations.
  3. 3Account deletion is also an email request, not a self-service button. Send the account email address and workspace name to [email protected].

Understand the automatic retention purge

  1. 1A scheduled job purges expired conversation data after 90 days; no deletion request is needed for that retention process to run.
  2. 2For an expired conversation, the purge deletes its conversation session and related outbound and inbound jobs, messages, turn diagnostics, conversation notes, conversation review events, and conversation signals.
  3. 3Orders are retained in anonymised form. For an order tied to an expired conversation, the purge nulls phone, customer_text, meta_message_id, linked_session_id, conversation_id, and meta_catalog_id.
  4. 4For an orphan order that reaches the retention cutoff, the purge nulls phone, customer_text, meta_message_id, linked_session_id, and catalog_id.
  5. 5Audit events for conversation.identity_revealed are deleted with the expired conversation data.

Disconnect a WhatsApp number separately

  1. 1Remove the WhatsApp credentials in Fluenta to disconnect the number from the bot.
  2. 2Separately revoke the access token in the Meta app that owns it. Removing Fluenta credentials does not revoke a token held in your Meta account.
  3. 3Deleting a Fluenta bot or workspace does not delete the connected WhatsApp Business Account or phone number from Meta. Manage that Meta data in your own Meta account.
Expected result. The requested deletion scope is clear, any remaining Meta action is handled separately, and the team knows which conversation data is automatically removed or anonymised at retention.

Troubleshoot deletion requests

A WhatsApp number was disconnected in Fluenta but its access token remains active.
Revoke the token separately in the Meta app that owns it. Fluenta and Meta are separate systems for this action.
There is no button to delete a workspace or account.
Email [email protected] with the account email address and workspace name. Workspace and account deletion are request-based today.
A conversation needs deletion before the automatic retention window.
Use the automatic retention process for the standard 90-day lifecycle. If the request needs a different scope or timing, contact the privacy address before deleting a broader bot, workspace, or account.
A user asks for a self-service data export before deletion.
Self-service data export is not available. Send an export request with the account email address and workspace name to the privacy address.

Related guides