Data Deletion Instructions

To help us identify and verify the requested records promptly, please provide:

1. Full name and contact email associated with your account or interactions.
2. The WhatsApp phone number used, including full international country code (e.g., +1...).
3. The participating business name or WhatsApp workspace you communicated with.
4. Scope of deletion: whether you are requesting deletion of individual customer conversation data, a workspace account, or both.
5. Context: approximate dates and times of the interactions, if known.

We will acknowledge your request and may ask for reasonable additional confirmation to verify identity, authority over a business workspace, or control of the relevant phone number or email. This protects users against unauthorized or malicious deletion.

If a participating business acts as the data controller for customer records, we may coordinate with that business to authorize and execute the deletion. The 30-day fulfillment period begins once identity and scope verification is complete.

Once a valid deletion request is verified and approved, we permanently delete or irreversibly anonymize data within the requested scope, including:

• Customer contact identifiers, tags, custom fields, and profile preferences;
• WhatsApp conversation messages, transcripts, and related service metadata held by Convoza;
• Lead pipeline history, order references, fulfillment notes, and customer support tickets;
• Business workspace configuration, AI knowledge bases, and authorized-user records when a full workspace deletion is requested; and
• Operational logs and cached telemetry no longer required for system security or legal compliance.

Note: Deleting records from Convoza does not automatically delete independent records stored directly by Meta/WhatsApp, third-party payment processors, or the merchant's external business systems.

We may retain minimal, strictly limited information where required or permitted by applicable law, including:

• Tax, billing, and financial transaction audit records;
• Security and fraud-prevention telemetry;
• Evidence required to establish or defend legal claims;
• Records of consent or opt-out preferences (e.g. suppression list to prevent future messaging); and
• A minimal confirmation hash proving that the deletion request was fulfilled.

Encrypted disaster-recovery backups are purged automatically through standard backup rotation schedules and are protected against ordinary operational access.