Data Deletion Instructions

Overview and scope

These instructions apply to personal data processed through the BestBulkSMS website, customer accounts, bulk and personalised SMS, WhatsApp Business Platform connections, message templates, recipient records, delivery reports, wallets, payments, APIs, support, security and related services.

A deletion request does not automatically require deletion of every record. We delete information when there is no continuing lawful, contractual, financial, security or dispute-related reason to retain it. Where erasure is not appropriate, we may restrict processing, remove direct identifiers or retain only the minimum required record.

Read the Privacy Policy for broader information about processing, security and privacy rights.

Prepare a structured deletion request

The builder below does not save or upload your information. It prepares a structured email in your default email application. Review the message before sending it.

Choose the correct request type

The information needed to locate data depends on how you interact with BestBulkSMS.

Delete a BestBulkSMS customer account

Account closure stops ordinary use. A deletion request additionally asks us to erase or anonymise eligible personal data and explain any records that must remain.

1. Review outstanding SMS and WhatsApp wallet balances, scheduled messages, disputes and active integrations.
2. Cancel or complete pending activity where the platform allows it.
3. Revoke API keys and disconnect systems that should no longer access the account.
4. Email the privacy team from the registered address and request account closure plus deletion of eligible data.
5. Complete identity or authority verification.
6. Retain the confirmation email and request reference.

Delete WhatsApp connection and Meta-related data

BestBulkSMS customers connect their own Meta Business Portfolio, WABA, phone number, profile and templates. We may store connection identifiers, encrypted customer tokens, synchronised profile and phone information, template cache, webhook events and message records.

Disconnecting versus deleting

Recommended procedure

1. Sign in and open WhatsApp Business Accounts.
2. Select the connected business and use the available disconnect action.
3. Remove or revoke BestBulkSMS in relevant Meta/Facebook business settings where it appears.
4. Email the privacy team with the business name, display phone and safe connection reference.
5. Request deletion of eligible locally held connection and messaging data.

Requests from SMS or WhatsApp recipients

If a BestBulkSMS customer sent you a message, contact the identified sender or business first where practical. That business normally determines why it collected your number and sent the message. BestBulkSMS assists with records in its systems and may investigate abuse or suppression requests directly.

Information that helps locate the record

• The telephone number that received the message.
• The sender ID, WhatsApp business name or sending organisation.
• The approximate date and time of the message.
• A screenshot or short description, with unnecessary sensitive information covered.
• Whether the request is deletion, correction, suppression, objection or an abuse complaint.

Abuse, spam or impersonation

State clearly if the message involved suspected spam, fraud, phishing, impersonation, harassment or unlawful marketing. Relevant evidence may be preserved during investigation.

Delete API and integration data

API integrations may create key metadata, permissions, public prefixes, request IDs, client references, endpoint logs, rate-limit events, message records and security diagnostics.

1. Revoke every active API key before shutting down the integration.
2. Remove secrets from environment variables, secret managers, servers and development systems.
3. Stop automated jobs and scheduled requests using the key.
4. Request deletion of eligible integration metadata and linked records.
5. Identify a key only by name, creation date or public prefix—never send the complete key.

What deletion normally covers

The exact outcome depends on the data category, account role, request scope, applicable law and whether another customer controls the data.

Records we may need to retain

We retain only information reasonably necessary for a valid continuing purpose, which may include:

• Accounting, tax, VAT, invoice, refund and financial-reporting obligations.
• Fraud prevention, account security, abuse investigation and service integrity.
• Telecommunications, consumer-protection, court, regulatory or lawful government requirements.
• Proof of recipient consent, opt-out, suppression, complaint or sender authorisation.
• Outstanding balances, payment disputes, chargebacks, unpaid liabilities or refunds.
• Legal claims, contractual enforcement, investigations or preservation notices.
• Minimal deletion-audit records needed to show that a request was received and completed.

Retained information is limited, access-controlled and not used for unrelated marketing or ordinary messaging after closure.

Identity and authority verification

Verification protects data from deletion by an unauthorised person. We request only information reasonably necessary for the request's type and sensitivity.

How the request is processed

1. Send the request: Use the structured email button or write directly to the privacy email. State the request type and enough information to locate the data.
2. We acknowledge and classify it: The request is classified as an account, connection, recipient, API, correction, restriction or other privacy request.
3. We verify identity and authority: We may confirm the registered email, phone number, account ownership, message evidence or representative authority.
4. We locate and review the records: We identify active-system data, customer-controlled data, legal retention requirements, processors and relevant backups.
5. We delete, anonymise or restrict: Eligible information is erased, irreversibly anonymised or restricted. Credentials are revoked and connections are disabled where requested.
6. We confirm the outcome: You receive confirmation, a description of any retained categories and the reason for retaining them.

We respond within the period required by applicable law. Complex requests, third-party dependencies, legal holds or identity issues may require additional information or time. We explain any permitted extension or limitation.

Backups, messaging providers and third parties

Backups

Data deleted from active systems may remain in protected backups until the backup cycle expires. Backups are isolated from ordinary use. If restored for disaster recovery, applicable deletion controls are re-applied where feasible.

SMS networks and gateways

SMS delivery can involve networks and messaging providers. We send deletion or restriction instructions to processors where appropriate, but independent network records may be governed by their own legal obligations.

Meta and WhatsApp

Meta and WhatsApp process business assets, account data and message events under their own terms and privacy practices. Use Meta's controls for data or assets held directly by Meta.

Customer-controlled copies

A customer may have exported recipient lists or reports to its own systems. That customer is responsible for copies it independently controls.

Remove BestBulkSMS access from Meta or Facebook

Where BestBulkSMS appears in your Meta/Facebook connected apps, business integrations or Apps and Websites settings, remove or revoke access. Menu names may differ by account type and interface.

1. Open the Meta or Facebook account that authorised BestBulkSMS.
2. Go to Settings and locate Apps and Websites, Business Integrations or the corresponding connected-app area.
3. Locate the BestBulkSMS WhatsApp application or integration.
4. Choose Remove, Revoke or Disconnect and confirm the action shown by Meta.
5. Sign in to BestBulkSMS and open WhatsApp Business Accounts to confirm the connection is disconnected.
6. Send a deletion request if you also want eligible BestBulkSMS-held connection and messaging data erased.

Limits, exceptions and important effects

• Deletion may permanently remove message history, templates, reports, API access and support context.
• Account closure may prevent access to wallet, invoice, delivery and compliance information.
• A request cannot require us to alter another person's records or delete data we must legally preserve.
• We may limit a manifestly unfounded, excessive, fraudulent, unverifiable or legally prohibited request while explaining the reason.
• Deleting BestBulkSMS data does not automatically delete copies held by a customer, network operator, payment processor, Meta, WhatsApp or lawful authority.
• Where a record contains information about multiple people, we protect everyone's rights and confidentiality.

Contact, complaints and regulatory rights

Related documents