LeadForm legal

Subprocessors Directory

LeadForm uses a focused set of infrastructure and product providers to operate the contractor revenue workflow.

Last updated: June 1, 2026

Providers may process data in the United States or other regions where they operate. Customers should review connected third-party tools they enable, especially HubSpot, Calendly, advertising platforms, and analytics tools added to their funnel.

Current subprocessors

Supabase

Authentication, Postgres database, storage, and server-side data operations

Core

Data: Account, workspace, form, submission, and operational data

Vercel

Application hosting, deployments, edge runtime, and platform security

Core

Data: Application traffic, logs, edge/runtime telemetry

Lemon Squeezy

Hosted checkout, subscriptions, merchant of record, tax, invoices, and billing webhooks

Billing

Data: Checkout, customer, subscription, tax, invoice, and webhook data

HubSpot

HubSpot contact creation, updates, notes, HubSpot avance, and integration readiness

Optional integration

Data: CRM contact properties, sync status, portal identifiers, and OAuth tokens

Google

OAuth sign-in and related account authentication services

Optional auth

Data: Authentication identifiers and profile data when Google login is enabled

Calendly

Post-submit booking and scheduling flows configured by the customer

Optional integration

Data: Scheduling context when a workspace embeds or links scheduling

Customer-enabled tools

  • If a contractor connects HubSpot, LeadForm sends CRM context according to that workspace configuration.
  • If a contractor embeds Calendly or another scheduling flow, homeowners may interact directly with that provider.
  • If a contractor adds external pixels or analytics later, the contractor should update notices and consent settings before launch.

Paid traffic without blind spots

Build a contractor funnel with consent, routing, HubSpot follow-up, and launch checks.

Start building