Start free
Account & data deletion

Account and data deletion policy

Effective date: 26 May 2026

This page explains how to delete a LEADARO account or workspace, what happens to the underlying data on deletion, and how end customers (leads) of an operator can have their personal data removed. It complements the Privacy Policy and the GDPR notice.

LEADARO is a multi-tenant SaaS platform. Two distinct deletion paths exist:

  • Operator-initiated — a workspace owner deletes their LEADARO account or asks LEADARO to delete the workspace.
  • End-customer-initiated — a lead or end customer asks to have their personal data removed from a workspace that captured them.

Because the operator is the Data Controller for the leads inside their workspace, the two flows are handled differently — see below.

Today, account and workspace deletion is processed by request to support — a self-service "delete my account" button is on the roadmap but is not yet shipped as the canonical operator flow. To delete an account:

  • Email office@thebrandoers.com from the address registered on the LEADARO account, with subject line "Delete my LEADARO account".
  • Include the workspace ID(s) you want deleted. If you own multiple workspaces, list each one explicitly — we will not assume you want the entire portfolio deleted.
  • We confirm receipt within 2 business days. We then send a final 48-hour confirmation email; the deletion proceeds only after you reply to confirm.

If the requesting address is not the registered account address, we will email the registered address to authenticate the request before proceeding.

Upon confirmed deletion, the following data is removed from the production database:

  • Lead records — names, phone numbers, email addresses, qualification answers, custom fields, tags, stage history.
  • Conversation transcripts across every channel — WhatsApp, Messenger, Instagram DM, SMS, voice transcripts, chatbot transcripts, email threads sent through the platform.
  • Call recordings stored by Twilio (where retained) — deletion is requested from Twilio.
  • Bookings created on the platform's calendar.
  • Notes, tasks, audit events attached to leads.
  • AI Brain configuration, knowledge base entries, flow templates, custom prompts.
  • Integration credentials — encrypted refresh tokens are deleted; we additionally request revocation from each connected third-party provider (Google Ads, Meta, WhatsApp Cloud, Postmark, Twilio) where the provider supports server-side revocation.
  • Production database — deletion completes within 30 days of confirmed request. In practice we target a 7-day soft-delete window followed by a hard delete, but the contractual maximum is 30 days.
  • Supabase database backups — daily backups retained for 7 days (point-in-time recovery is not currently enabled). Deleted rows expire from the daily-backup window within 7 days; we do not access backups for any purpose other than disaster recovery, and we do not selectively restore deleted records on operator request.
  • Better Stack operational logs — request-level operational logs (request ID, timestamp, status code, no PII payload) expire on a 90-day rolling schedule.
  • Invoices and tax records — retained for 10 years as required by Romanian fiscal law (Article 25 of Law 82/1991). Personally identifying information on invoices is the minimum required by tax authorities (operator name, address, CUI / tax ID).

If you are a lead or end customer (e.g. you submitted a contact form on a clinic's website that uses LEADARO, or you replied to a WhatsApp message that the clinic sent through LEADARO), your relationship is with the operator (the clinic, the agency, etc.), not with LEADARO directly. Your fastest deletion path is:

  • Contact the operator (the business that captured your data) and ask them to delete your record. They can do so in seconds inside their LEADARO workspace.
  • If you cannot identify the operator or they are unresponsive, email office@thebrandoers.com with as much context as possible (the website you submitted on, your name and phone number, an approximate date). We will route your request to the correct workspace and assist its owner in fulfilling it. Article 28(3)(e) GDPR requires us to do so as the Processor.

We acknowledge end-customer deletion requests within 5 business days and aim to complete them within the 30-day window that GDPR allows.

If a Google account user revokes LEADARO's OAuth grant (either inside LEADARO at Settings → Integrations → Google Ads → Disconnect, or directly from myaccount.google.com/permissions), the following happens immediately:

  • The encrypted refresh token is deleted from the integration record.
  • Any in-flight scheduled jobs that would have called the Google Ads API for that workspace are halted.
  • Subsequent API calls fail with invalid_grant and the integration is marked needs_reauth; no further Google API data flows in until the user re-authorizes.
  • Previously imported Google Ads lead form submissions remain in the workspace's lead pipeline as the operator's business data (per Limited Use, they continue to belong to the operator). To remove those records, follow the workspace-deletion or per-lead-deletion paths above.

Meta (Facebook Login). If you connected Meta to a workspace and later remove the LEADARO app from your Facebook account (Settings → Apps and Websites), or submit a data deletion request from Facebook, Meta calls our deauthorization and data-deletion endpoints with a signed request. We then immediately disconnect every Meta connection that was authorized with your account (Lead Ads, Messenger, Instagram DM, WhatsApp Cloud): the user access token, the Page tokens and the asset catalog are deleted from the workspace record. Facebook shows you a confirmation code and a link to our status page, where you can check what was done. Leads captured through those channels are the operator's business data and are not your Facebook data; to remove them, use the end-customer path above. The same disconnect runs when an operator clicks Disconnect on the Meta integration inside LEADARO.

We may retain limited data beyond the timelines above only when:

  • Required by a legal obligation (tax, accounting, anti-fraud);
  • Required to comply with a binding legal order (court order, regulatory request);
  • Necessary to defend legal claims under Article 17(3)(e) GDPR — for the duration of the limitation period.

Where an exception applies, only the strict minimum needed for the obligation is retained, and access is restricted to the personnel handling the matter.

All deletion requests, status questions and follow-ups should be sent to office@thebrandoers.com. For end-customer deletion requests, also see the GDPR notice for the full list of data-subject rights.