Legal
Subprocessors
Last updated: April 27, 2026 · Leadspresso LLC · Miami, Florida
Leadspresso uses the third-party service providers listed below ("Subprocessors") to deliver our platform. Each Subprocessor is bound by its own privacy policy and data processing terms.
Notification of changes. We will provide at least thirty (30) days' advance notice via email to account-administrator email addresses on file before adding a new Subprocessor that processes Client or Lead data. You may object to a new Subprocessor by emailing support@leadspresso.com within the notice period; if we cannot reasonably accommodate your objection, your sole remedy is to terminate your subscription, which we will effect without further charge.
Current Subprocessor list
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Google Ads campaign management; Google Business Profile services | Account business information; OAuth tokens; campaign performance data | United States (global infrastructure) | |
| Meta Platforms | Facebook and Instagram advertising campaign management via the Marketing API | Account business information; OAuth tokens; campaign performance data | United States (global infrastructure) |
| Stripe | Subscription billing and payment processing | Account holder name, email, billing address; payment card data (held by Stripe, not Leadspresso) | United States |
| Twilio | Call tracking number provisioning; inbound call routing and recording; transactional SMS to Clients | Tracking phone numbers; inbound caller phone numbers; call recordings; Client mobile numbers for SMS alerts | United States |
| Resend | Transactional email delivery (welcome, password reset, lead alerts, weekly summary, payment failures) | Recipient email addresses; email body content | United States |
| Supabase | Application database (PostgreSQL); user authentication; object storage for client assets | All Client and Lead data stored by the platform | United States (us-east-1) |
| Anthropic | AI-generated ad copy and landing page content via the Claude API | Business context only (business name, type, city, state, budget, channel) — no end-customer personal data is sent | United States |
| OpenAI | AI-generated hero images for landing pages via the GPT-Image API | Business context for image prompts — no end-customer personal data is sent | United States |
| Pexels | Stock image fallback for landing pages | Image search queries (business-context keywords only) | European Union (Germany) — transfers from EEA/UK governed by SCCs |
| Unsplash | Stock image fallback for landing pages | Image search queries (business-context keywords only) | Canada |
| PostHog | Product analytics and feature usage telemetry | Authenticated Client user IDs; page views; feature events; technical session data | United States (US Cloud) |
| Sentry | Error monitoring and crash reporting | Error stack traces; request metadata; technical session context | United States |
| Vercel | Application hosting, deployment, and edge networking | Request logs; technical metadata for traffic served to and from the platform | United States (global edge network) |
Hosting and primary data location
Application infrastructure and the primary database are hosted in the United States. International transfers from the EEA, UK, or Switzerland are governed by the Standard Contractual Clauses (and the UK International Data Transfer Addendum where applicable), supplemented by reliance on the EU-US Data Privacy Framework where the recipient is certified. Where SCCs apply, Module 2 (Controller to Processor) governs Client-to-Leadspresso transfers and Module 3 (Processor to Sub-processor) governs Leadspresso-to-Sub-processor transfers.
Contact
Leadspresso LLC
Principal place of business: Miami, Florida
Registered agent: c/o Northwest Registered Agent
7901 4th St N, Suite 300
St. Petersburg, FL 33702, United States
support@leadspresso.com