Data Deletion

ASAS · Last updated 27 September 2026.

1. If you are a business's customer

If you messaged, booked with, or were recorded by a business using ASAS, ask the business to delete your information first. It decides what to keep and can review your record and request its erasure in its workspace. You can also email admin@asaswebs.com with the business's name, the contact method you used, and the information your request concerns. Please do not send an identity document or extra health information in your first message. We will route the request to the business and assist it, or handle information for which we are directly responsible.

2. If you connected a Meta account as a business user

If you used Meta login to connect a Facebook Page, Instagram account or WhatsApp Business Account to ASAS, you can disconnect it in the business's settings or remove ASAS from your Meta settings. You can request deletion of connection data through Meta's process or by contacting us. This process concerns the authorisation you gave the ASAS app; it does not erase the business's customer conversations or patient records. If you only messaged the business through a Meta channel, use the customer process in section 1.

3. Meta requests and status

When ASAS receives a signed Meta deletion request, it verifies and records the request and returns a confirmation code and status link. The status may remain “received” while matching connections are checked. If ASAS can identify a matching connection grant, it attempts to revoke the grant and mark the channel for reconnection. If a grant cannot be inspected or none matches, the request remains for human review; a confirmation code does not mean all your information was erased. The status page shows the processing outcome, or that no matching record was found after review, without displaying the business or its data. Removing the app in Meta withdraws authorisation on Meta's side, but does not necessarily create a request to delete the business's records.

4. Identity checks and customer requests

Before a customer record is erased, the business or ASAS, depending on who handles the request, checks the requester's identity and connection to the record or authority to act for someone else. We may ask for confirmation through a contact method known to the business or limited additional information, and consult the business where needed. A Meta request's signature confirms its source through Meta; it does not establish ownership of a business's customer records. We will tell you when work within our scope is complete, if more information is needed, or if a restriction prevents deletion.

5. Scope and limits

A business can request erasure of customer information from active ASAS records, including contact details, messages and linked clinical information where those features are used. Some records may be deleted; others may be detached or de-identified to preserve appointment, accounting and audit records. Information needed for a legal obligation, dispute, or evidence of consent or opt-out may be retained; an active legal hold may temporarily prevent erasure. Backups are not immediately edited record by record: they expire under their retention cycle, and erasure must be reapplied after a restore. Copies held by the business, Meta or another provider are subject to those parties' policies and responsibilities; the business must address them where applicable.

There is no single completion period for every request. We will explain the outcome, what was done within our scope, or why it is delayed through an appropriate contact method, as applicable law requires. Questions: admin@asaswebs.com.