LegalHub

Data Deletion Instructions

Last updated: November 17, 2026

1. Who to contact

If you contacted an agency through Facebook, Instagram, a form or another channel, ask that agency, as controller of its client/lead processing, to delete the relevant information from LegalHub. For processing controlled by LegalHub, or assistance identifying the responsible organisation, contact VALENTYN VERBELCHUK, trading as LegalHub CRM, at office@legalhubcrm.com.

Provide only the information necessary to find the records, such as the agency name, the contact details or account you used and a short explanation of the requested deletion. Do not send passwords, access tokens, App Secrets, full client exports or unnecessary identity documents. Reasonable verification may be needed before data is disclosed or deleted.

2. Disconnecting is separate from deletion

An authorised tenant administrator can disable the exact Lead Ads Page/form binding. The service operator manages its server-side token and, where appropriate, removes only the dedicated App’s relevant Page subscription or authorisation. Messenger and Instagram have separate controls and must not be disabled merely to disconnect Lead Ads.

Disconnection stops subsequent import for that binding; it does not automatically delete existing Leads, internal notifications, receipts, diagnostic copies or backups. OFF is not a retained queue and does not promise automatic backfill.

3. Scope of a deletion request

Available CRM deletion controls and operator-assisted procedures are different. Identify the organisation and records concerned, and where known the Page/form or CRM Lead reference. The controller assesses the request and lawful retention exceptions; LegalHub assists where it is processor. Where the interface lacks the required control, request service-level assistance instead of assuming the related data was erased.

  • Consider the relevant Lead/client records, messages, notes, attachments and linked records within the authorised scope.
  • Consider related internal notifications, direct lead references in delivery receipts, diagnostic exports and any operator-held copies separately.
  • A minimal keyed deduplication record can be necessary and justified to prevent duplicate import. The adapter’s manual 30/366-day receipt eligibility rules are described in the Privacy Policy; they are not an automatic deletion of the Lead or all related records.
  • Provider-held logs/backups and independent Meta records have separate controls and contractual or legal retention. A CRM deletion does not erase those copies immediately.

4. Response and remaining copies

Where GDPR applies, the controller responds without undue delay and normally within one month of receiving the request. A permitted extension of up to two further months requires notice and reasons within the first month. This is a response deadline, not a promise that every provider backup is physically erased immediately.

The response should distinguish deleted active records from any retained category, its justification and the applicable retention period or criteria. If erasure is refused or limited, the controller explains the reason and available complaint/remedy options. Restoring a backup does not justify resuming use of records subject to an applicable deletion decision; that decision must be reconciled before use.

5. Own synthetic review and historical QA

For the operator’s own review of LegalHub CRM Lead Ads App 1627116975561049, contact the same privacy address and identify the session or owned Page/form. Do not submit a real client’s details to the review form. The isolated database, notifications, credentials, diagnostics and copies are considered separately.

The approved manual closure procedure is: temporary local credential copies within 24 hours, review data/copies within 7 days, and the deidentified outcome report within 30 days after the session’s recorded closure. It does not erase independent Meta/provider records or extend earlier QA deadlines. Historical QA Apps and their standalone QA notices do not authorise processing customer production data in the review environment.

Only the selected, redacted final video required for an open Meta App Review has a separate purpose-based period: until the final decision or withdrawal, with a manual necessity check every 7 days and deletion of operator-held copies within 7 days after review closure. Raw recordings, credentials and the database retain their original shorter deadlines. Deleting a local video does not delete Meta’s submitted copy.

6. Related documents

The Privacy Policy explains roles, purposes, recipients, international processing, retention and rights.