User Data Deletion Instructions

Last updated: 16 September 2026

Use this page to request deletion of information held by Talkalize SDN. BHD. You can submit a request without signing in or having a Talkalize account.

1. Send your request

Email info@talkalize.com with the subject Data Deletion Request. If the link does not open your email application, copy the address into your preferred email service.

Account holders: send from your registered email if possible, identify your business or workspace, and say which data you want deleted or whether you want the account closed. Include the connected WhatsApp number only if needed to identify the connection.
Individuals who messaged a business: identify the business, the WhatsApp number you used and the information or conversation concerned. You do not need to know a workspace ID or WABA ID.

Send only enough information to locate your records and reply to you. Do not send passwords, access tokens, payment-card details or identity documents with your initial request.

2. Choose the scope

Disconnect WhatsApp: marks a connection inactive where that control is available. It does not erase the stored token or history, revoke Meta permissions, cancel billing or close your Talkalize account.
Delete stored data: request removal of specified contacts, messages, media or other workspace information. Deleting a conversation in the inbox removes the associated contact and message records, but is not a complete erasure of attachments, logs, campaign records or copies elsewhere.
Close a Talkalize account: explicitly request account closure and deletion of its workspace information. Account closure needs support coordination; there is no single self-service action that erases all associated data.

For recurring billing, also use the cancellation process described in our Terms of Service. Include any unresolved subscription or wallet issue in your closure request. Sending a deletion email is not an automatic billing cancellation or refund.

3. Verification and processing

Requests require review. We may ask you to confirm control of the registered email or relevant phone number, or your authority to act for the workspace. If you cannot use the registered email, explain that so an alternative verification method can be considered. Information about other people will not be supplied merely because someone knows a business name or phone number.

The review identifies the requested records, your authority, any customer instructions needed and any applicable retention requirement. Deletion can involve separate work on active records, media storage, integrations, logs and backups. Acknowledgement of a request does not mean deletion is complete.

Ask for a status update by replying to the same email thread. Completion confirmation should identify the data removed, any information retained and its reason, and any backup copies or third-party actions still outstanding. There is no fixed acknowledgement or completion deadline published on this page; timing depends on verification, scope and applicable requirements.

4. Credentials and future access

Disconnecting is not an immediate stop for every operation. Previously queued campaign messages may still be sent, and incoming events may still be logged or update delivery and template records. Ask support to review pending campaigns and event handling as well as the connection when requesting a complete stop.

To withdraw access, remove Talkalize's access to the relevant assets in Meta's business or integration settings, or ask us for help with a managed connection. Request removal of stored connection credentials as part of deletion or closure. Disconnecting in Talkalize alone leaves those credentials stored and does not revoke the token at Meta.

Stopping future collection also requires addressing active permissions and event delivery. Include this in your request so the connection and integrations can be reviewed. Removing previously stored data alone does not prevent new messages or events from creating records while the connection remains authorized.

5. Retained records and backups

Some invoice, payment and wallet transaction records may be needed for an applicable accounting obligation or an unresolved payment dispute. Specific records relevant to a legal preservation obligation may also need to remain. An exception must be identified for the affected information; it is not a blanket reason to keep all messages or credentials. Applicable Meta Platform deletion requirements must also be considered.

Backups, diagnostic logs and stored attachments are separate from the inbox database. Do not assume that deleting an inbox item immediately removes those copies. Backup expiry and removal need to be confirmed for the systems involved; no fixed backup rotation or expiry period is promised here. Ask for remaining copies, their purpose and expected removal timing to be included in the response.

6. Information in a customer's workspace

If you communicated with one of our business customers, contact that business first. It decides how your information is used in its workspace and may need to instruct us to remove it. You can also use the email method above; we can help identify the relevant workspace and coordinate the request after verification. A request about your own information does not require closure of the business's entire account.

7. Meta and other copies

Deleting Talkalize data does not automatically delete a Facebook account, WhatsApp account, WhatsApp Business Account (WABA), or information held by Meta. It also does not erase messages already delivered to recipients, customer exports or copies in customer-connected systems. Use those services' own privacy tools or contact the relevant business for those copies.

For questions, email info@talkalize.com. Our Privacy Policy explains the information we process and our role.