Data deletion instructions

How to request deletion

A user or a business asks for deletion by contacting the operator. The privacy contact is [TODO: privacy contact email]. Support is [TODO: support email]. Phone is [TODO: phone number].

This website cannot accept the request. There is no form, and no button on this page deletes data. If the contact details above are still placeholders, a working channel has not been published yet.

What to include

Include the account email, the person’s name, the company name, and whether the request covers one user, a whole company workspace, or WhatsApp and Meta connection data.

Also include a way to confirm that the requester controls the account or is allowed to speak for the company. Flowmora may ask for more information before acting. Do not send a WhatsApp access token or a password in the request.

Account removal is different from disconnecting Meta

Removing a user stops that person from signing in. Removing a company workspace is a request to delete that company’s CRM records. Neither of those steps is the same as disconnecting WhatsApp.

Disconnecting WhatsApp means the company asks to remove the saved Cloud API connection so Flowmora stops using that WhatsApp Business account. Message history already stored in the CRM remains until a separate deletion request for those records is completed.

A company admin can also change WhatsApp settings inside the CRM. Changing those settings is not, by itself, a completed deletion of historical messages.

WhatsApp and Meta data

A business can ask Flowmora to remove the WhatsApp identifiers, tokens, and message records Flowmora stores for that company. Meta may still keep data on Meta’s own systems under Meta’s policies. Flowmora cannot delete data that only Meta holds.

People can also remove an app from their Facebook or Meta settings where Meta offers that control. That Meta-side removal is separate from deleting the company’s CRM records.

What happens after a request

The operator reviews the request, confirms it is entitled to be actioned, and then deletes or restricts the relevant records it holds. The product does not do this automatically when someone opens this page.

This draft does not promise a response time. The schedule is [TODO: retention schedule].

Retention exceptions

Verified exceptions, such as a record that must be kept for a legal claim or a statutory duty, are [TODO: verified retention exceptions]. No exception is claimed until it has been confirmed both legally and operationally.

This page is not a deletion callback

Meta’s app settings can ask for a data deletion instructions page, a data deletion callback, or both, depending on the product. This address is the public instructions page. It returns this explanation to any visitor, including a review crawler, without signing in.

A data deletion callback is a different thing: an API endpoint that receives Meta’s signed request and returns a confirmation code and a status URL. Flowmora’s API does not provide that callback today. If the selected Meta integration requires one, it has to be built on the API, not on this static website.