Blaze data deletion request

1. How to submit a request

Email privacy@blaze.do with the subject “Data deletion request”. Identify the relevant Blaze service, business or account and associated email or number that helps locate the data. Explain whether you request deletion of particular personal data, a connection or an entire account. You do not need a direct Blaze account to submit a request.

Do not include passwords, access codes, tokens or complete identity documents in your initial message. Requests may concern data received through Meta, WhatsApp or other Blaze services. The route is available to everyone using Meta integrations regardless of country.

2. Proportionate verification

Existing information will be used first to verify identity, account control or representation. If further information is needed, only what is necessary will be requested through an appropriate channel. Excessive information that makes exercising rights impracticable will not be required. A business administrator cannot indiscriminately request deletion of data beyond their authority.

If reasonable verification is not possible, we will explain what is missing and available options. Verification of a rights request will not become new marketing permission or a general requirement to provide credentials.

3. What happens after receipt

Receipt will be recorded, a tracking reference assigned, scope and the responsible entity determined, and relevant steps communicated by email. If the request is ambiguous, a specific clarification will be sought without unnecessarily delaying parts that can be addressed.

Where Blaze processes data for a business, it will coordinate with the controller and provide agreed assistance. Where Blaze determines the processing purpose, it will decide the request within its own scope. The entity receiving payment or issuing an invoice does not automatically determine who handles every category.

4. Scope and effects

Deletion may affect profiles, contacts, histories, content or related features according to the service and validated request. Others' rights will be checked and relevant effects explained, such as loss of access or inability to recover content. An individual's request will not erase an entire organization's resources without authority and scope verification.

Canceling a subscription, disconnecting Meta or WhatsApp and deleting data are different operations. A request does not automatically delete copies held by other businesses as independent controllers or cancel their contracts. You may also need to contact the business sending messages or the relevant provider.

5. Timing and follow-up

Requests will be addressed diligently within the period required by applicable law. Any permitted extension will be communicated with its reason and revised expectation. No universal 30-day response or instant deletion upon email receipt is promised.

You can request an update by replying to the request thread or emailing privacy@blaze.do. Final confirmation will distinguish completed deletion, outstanding actions and legitimately retained data. For full or partial refusal, the reason and available review or complaint routes will be explained.

6. Legitimate retention

Records strictly necessary for tax or accounting obligations, a valid legal requirement, defense of claims, proportionate fraud prevention or minimal evidence of handling the request may be retained according to applicable law. An exception does not authorize keeping all data or continuing marketing use.

Each exception will have a documented purpose, restricted access and end criterion. When it ends, appropriate deletion or anonymization will follow. No jurisdiction-specific fiscal retention years are set without validation.

7. Providers and backups

Deletion will be propagated to systems and providers acting for the controller within the applicable scope. In backups without granular deletion, data will remain outside ordinary use until documented rotation unless legitimately retained. If a backup is restored, the operational procedure will be followed to reapply recorded deletions before normal use resumes.

Where relevant, we will explain the service’s applicable backup retention period and export or recovery options and time limits. Recovery of permanently deleted data is not guaranteed.

8. Requests forwarded by Meta

These instructions may serve as the public deletion-request route. They do not themselves constitute an automatic callback. If Blaze enables a Meta callback, it must verify the signed request, locate the correct data, initiate a real operation and provide a confirmation code and truthful status page without exposing personal information.

9. Contact and review

Privacy and deletion: privacy@blaze.do. Contractual matters: legal@blaze.do. The privacy policy identifies Blaze entity roles and the channel for requesting applicable legal information. Effective date and last updated: October 2, 2026. You may use complaint routes available under applicable law.