Privacy & data protection

Who is responsible?

LeadButton is a product of MDware. For the leads and analytics you collect through your widget, you are the data controller and LeadButton (MDware) acts as your processor under a data processing agreement (DPA). For your account and billing data, MDware is the controller.

Questions about privacy? Email privacy@leadbutton.app.

What data do we process?

We process as little as possible. Concretely, three kinds of data:

• Lead data your visitors submit (e.g. name, email, phone, message) — you decide which fields you ask for.
• Widget events (widget opened, reply clicked, lead submitted) for your analytics — first-party and optionally cookieless.
• Account and billing data (email, organisation, plan, payment status via Stripe).

Where is your data stored?

All lead and analytics data is stored in the EU on Supabase (AWS eu-west-1, Ireland), with tenant isolation via row-level security.

We use a short list of sub-processors, each under a GDPR data-processing agreement: Supabase (database, hosted in AWS eu-west-1, Ireland), Vercel (site and widget hosting), Resend (lead email delivery) and Stripe (billing). The full sub-processor list and our DPA are available on request; we update the list before making any change.

Cookies and tracking

The widget itself sets no tracking cookies and only starts when a visitor clicks it. Widget analytics can run fully cookieless. See our cookie policy for the details.

Your rights (GDPR)

Under the GDPR you have the right to access, rectification, erasure, restriction, objection and data portability. You can export leads as CSV and, on request, have your account and data deleted.

For requests about your visitors' data you are the point of contact; we support you as your processor. Email privacy@leadbutton.app.

How long do we keep it?

We keep leads for as long as your account is active, or until you delete or export them. After cancellation we delete lead and analytics data within 90 days, unless the law requires us to keep something longer (e.g. billing records).

Security

Data is encrypted in transit (TLS) and at rest. Access is role-based; agency sub-users see only the sites they’re authorised for, never billing or other clients’ leads. Webhooks are signed with HMAC-SHA256.

Changes

We update this policy when the product or the law requires it. We announce material changes in advance in the back office. The date at the top shows the last update.