Version 1.1 — Effective Date: May 20, 2026 Public
The table below lists the third-party sub-processors that Resolon LLC ("we" or "us") engages to help deliver the Service. Each sub-processor receives only the minimum Personal Data necessary for its designated function (data-minimization principle) and is bound by data-protection obligations no less protective than those in our Data Processing Agreement.
Change notice: We will give Customers at least 30 days' prior written notice of any intended addition or replacement of a sub-processor by updating this list and, where the Customer has subscribed to sub-processor notifications, by email to the Customer's designated contact. To subscribe, email privacy@leadvalidatorpro.com.
| Sub-processor | Purpose / function | Data received | Jurisdiction | Privacy policy |
|---|---|---|---|---|
| Enformion Enformion LLC |
Primary identity verification; reverse-phone and person-search lookups used to correct and enrich lead contact data. | Name, phone number, email, mailing address, lead attributes needed to resolve identity. | United States | enformion.com/privacy-policy |
| IPQS IPQualityScore, LLC |
Phone-number fraud and risk scoring; disposable-email and IP-risk checks. | Phone number, email address, IP address (where relevant). | United States | ipqualityscore.com/privacy-policy |
| Smarty Smarty, LLC (formerly SmartyStreets) |
Property-address validation, standardization, rooftop geocoding, and property-attribute enrichment. | Street address, city, state, ZIP. No name, phone, or email is sent. | United States | smarty.com/legal/privacy-policy |
| Stripe Stripe, Inc. |
Payment processing, subscription billing, invoice hosting, and customer-portal self-service. | Customer-account billing contact, company name, card-tokenized payment method, invoice history, webhook events. We do not store the PAN. | United States (global processing networks) | stripe.com/privacy |
| Claude AI Anthropic, PBC |
AI-assisted disposition, flag generation, and (when enabled) deep-research enrichment via the Claude model family. | Lead attributes needed to score the lead. No payment data. Anthropic does not train on API data by default. | United States | anthropic.com/legal/privacy |
| Sentry Functional Software, Inc. d/b/a Sentry |
Error monitoring, exception tracking, performance diagnostics. | Error metadata, stack traces, environment fingerprints. Server-side PII scrubbing removes email, phone, Stripe IDs, JWT tokens, session cookies, and lead PII before events are sent. | United States | sentry.io/privacy |
| Render Render Services, Inc. |
Application hosting, managed Postgres, background workers, managed daily snapshots. | All Personal Data Processed under the DPA is stored on Render infrastructure (US-East region). | United States | render.com/privacy |
| Cloudflare Cloudflare, Inc. |
DNS, Web Application Firewall, Zero Trust Access, Turnstile bot-protection, global CDN / edge security, and inbound email Worker for lead-intake routing. | Request metadata (IP, user agent, request path), Turnstile tokens, Zero Trust session metadata, inbound lead email contents (when the Email Worker route is used). | Global (routes via nearest edge PoP) | cloudflare.com/privacypolicy |
| WorkOS WorkOS, Inc. |
Identity, password storage, session management, MFA (TOTP), SSO, and audit logs (SOC 2 Type II). | Subscriber email address, hashed password, session tokens, IP and User-Agent at authentication time. No Lead Subject data. | United States | workos.com/legal/privacy |
| Resend Resend, Inc. |
Transactional email delivery for product notifications (password resets, lead-ready alerts, trial drip, billing receipts). | Recipient email address, message subject and body (which may include lead identifiers per Customer-configured notification templates), delivery telemetry (opens, bounces, suppressions). | United States | resend.com/legal/privacy-policy |
| Telegram Telegram Messenger Inc. |
Operational alerting to Customer-administered Telegram chats (lead-ready notifications, operator health alerts). Telegram is used only for operational notifications, not for transmitting Personal Data about Lead subjects beyond the content the Customer configures. | Message contents configured by the Customer (may include lead verdict, score, and contact identifiers). | Global (Telegram Bot API) | telegram.org/privacy |
| Google Maps Google LLC (a subsidiary of Alphabet Inc.) |
Address geocoding (street-to-coordinates) and Street View imagery for property verification. | Street address, city, state, ZIP. No name, phone, or email is sent. | United States (global service) | policies.google.com/privacy |
We transmit only the minimum data each sub-processor needs to perform its function:
For transfers originating in the EEA, UK, or Switzerland, we rely on the Standard Contractual Clauses (Module 2, Controller-to-Processor) annexed to European Commission Implementing Decision (EU) 2021/914 and, for UK-origin transfers, the UK International Data Transfer Addendum. Details are in the Data Processing Agreement, Section 13.
Questions about sub-processors: privacy@leadvalidatorpro.com.