Data Deletion Policy
Data Deletion Policy | Omnibot
Data Deletion

Omnibot Data Deletion Policy

How to remove your Omnibot account and understand what happens to your information.

Last updated: November 10, 2025

Overview

This policy explains the options available to administrators and end users of Omnibot for deleting accounts, workspaces, and associated data. It also details residual data that may remain for legal, security, or operational reasons. Please review our Privacy Policy for additional context on data handling.

Self-Service Account Deletion

Workspace Owners

  1. Sign in to Omnibot as a workspace owner or administrator.
  2. Navigate to Settings > Account and choose Delete Workspace.
  3. Confirm the deletion request. You may be asked to verify your identity via email.
  4. Deletion requests are queued immediately; processing typically completes within 30 days.

When a workspace is deleted, all user accounts within that workspace lose access, and associated data is scheduled for removal as outlined below.

Individual User Accounts

  1. Users may request personal account deletion via in-app settings or by emailing support@airbot.cloud.
  2. We will verify the request and revoke access within 7 days.
  3. Personal data tied to the account is deleted or anonymized, while workspace-level content (e.g., conversations owned by a team) may remain accessible to other authorized users.

API-Based Deletion

Customers may automate deletion using our REST API. Authenticated users can call DELETE /api/v1/users/me to remove their profile or DELETE /api/v1/workspaces/:workspaceId (admin only) to purge an entire workspace. API calls are subject to the same verification and retention rules described here.

Meta (Facebook/Instagram) Data Deletion & Deauthorization

In compliance with Meta’s Platform Terms, Omnibot hosts dedicated endpoints to respond to deauthorization and user-initiated deletion requests originating from Facebook or Instagram experiences. If you remove the Omnibot app from Facebook, Meta sends a deauthorization notice to /api/v1/facebook/compliance/deauthorize, which immediately revokes stored tokens and disables the related workspace channel. When you trigger a data-deletion request through Facebook’s interface, Meta calls /api/v1/facebook/compliance/deletion-request and we delete or anonymize the conversations, contacts, and messages tied to your Page-scoped ID.

How Facebook users can track deletion

  1. Initiate the deletion request from the Facebook app settings (or by uninstalling Omnibot from your Page/Inbox experience).
  2. Meta forwards the request to Omnibot and we respond with a confirmation code plus a status URL.
  3. Visit https://omni-gw.airbot.cloud/api/v1/facebook/compliance/deletion-status/<confirmationCode> to view the latest status (pending, processing, or completed). The page also notes when associated data was deleted.
  4. If you misplaced the confirmation code, contact support@airbot.cloud with your Page ID and screenshots, and we will re-send the status link.

These automated flows complement our manual support channels. If you manage data outside Omnibot (exports, BI systems, or downloaded archives) you remain responsible for deleting those copies. Workspace owners can monitor incoming requests from the Admin > Compliance view or via the email alerts we send when Meta notifies us.

Data Removed Upon Deletion

  • User profile information (name, email, authentication IDs).
  • Workspace configuration, channels, automations, and custom settings.
  • Conversation transcripts, AI responses, attachments, and knowledge base content.
  • Integration tokens, OAuth credentials, and API keys generated by the workspace.
  • Analytics dashboards, message metrics, and usage logs tied to the workspace.

Deleted data is purged from active systems and scheduled for removal from backups within 30 days, unless otherwise required by law.

Data Retained Temporarily

We may retain limited data for the durations listed below:

  • Audit & Security Logs: IP addresses, event metadata, and system logs retained up to 90 days to investigate fraud or abuse.
  • Billing & Transaction Records: invoices, payment confirmations, and tax documentation retained for the statutory period required by Egyptian law (typically 7 years).
  • Support Tickets: correspondence with Airbot support retained for up to 24 months to resolve ongoing issues.

Retained records are isolated from production systems and kept solely for the purposes described above. They are deleted or anonymized once no longer required.

Third-Party Integrations

When you delete a workspace or disconnect an integration, Omnibot revokes stored OAuth tokens and sends unsubscribe calls to providers such as Meta (Facebook/Instagram). Our compliance endpoints automatically share confirmation codes and deletion status URLs with Meta so affected users can verify completion. You may also need to remove app access from provider dashboards or delete exports you created outside Omnibot to fully complete the process.

Restoring Deleted Data

Once deletion is finalized, the data cannot be restored. If you need to recover content, contact support@airbot.cloud within 14 days of submitting the deletion request. We cannot guarantee recovery after that window.

Assistance & Data Subject Requests

If you require assistance or are an end user submitting a privacy request, email support@airbot.cloud. Include your workspace ID, business name, or Meta confirmation code so we can locate the request quickly. We respond within 30 days and coordinate with the relevant workspace owners as needed.

Contact

For questions about this policy or to escalate a deletion request, contact Airbot at:

  • Email: support@airbot.cloud
  • Address: 10 Street branching off 82 Street, Maadi, Cairo 4212011, Egypt