Privacy Policy

Effective Date: April 16, 2026  ·  Last Updated: August 5, 2026

LeadCatch LLC ("Company," "we," "us," or "our"), a Tennessee limited liability company, respects your privacy. This Privacy Policy explains how we collect, use, store, and protect information when you use our website (leadcatch.homes) and our AI-powered lead conversion services for roofing contractors (the "Service").

Two roles: for our own website visitors, prospects, and clients, we act as the business deciding how data is used. For the homeowner leads of our roofing-contractor clients, we act as a service provider / processor — we handle that data only on the client's behalf and instructions, to deliver the Service.

1. Information We Collect

Information Clients Provide

• Account and onboarding information: Name, email address, phone numbers (including an owner cell number for urgent escalations), business name and address, service area, business hours, services offered, contractor license number, insurance carriers accepted, pricing information, and calendar account email
• Billing information: Payment card details (processed and stored by Stripe; we do not store card numbers)
• Integration credentials: OAuth tokens and connection details for your calendar and lead sources
• Customer lists you upload: If you provide a list of your existing customers (for example, a suppression or reactivation list), you are responsible for having the right to share it

Information From Clients' Leads (Homeowners)

• Lead contact data: Name, phone number, email address, and property address as provided by the lead through calls, texts, web forms, and other connected sources
• Job details: Roof issue or damage description, urgency, insurance-related details the lead volunteers, and preferred appointment times
• Conversation data: The content of SMS, email, and voice conversations between our AI assistant ("Alex") and leads
• Appointment data: Dates, times, and service types booked through the system

Calls, Transcripts, and Recordings

• AI-answered business calls: When our AI assistant answers an inbound call to a client's business line, the call is recorded and transcribed, and the recording and transcript are stored so we can qualify the lead, book the appointment, and give the contractor full context. Every caller, in every state, on every such call, hears the same fixed spoken announcement before any audio is captured: “Just so you know, this call is recorded and transcribed for quality, and you're speaking with an AI assistant, not a live person.” That announcement is a fixed pre-recorded line played automatically at the start of the call — it is not spoken by the AI, it cannot be shortened or skipped, and it finishes playing before the audio connection that carries your voice to us is opened. If you would rather not be recorded, or would rather not speak with an AI assistant, you can end the call at that point
• Our own outbound calls to businesses: Outbound calls we place to businesses through our own calling system may be recorded and transcribed, and where they are, the recording and transcript are stored so we have an accurate record of the conversation. Recording is off by default and turned on only when we can affirmatively prove, from the business's own recorded state, that the business sits in a one-party-consent state; where we cannot prove that, or where the business sits in a state that requires every party's consent, the call still goes through but is not recorded at all. On every call we do record — in every state, including the ones where no law requires it — the person who answers hears a spoken announcement before the conversation begins: “Before we begin: this call is recorded. This is LeadCatch calling. You can reach us back at 615-527-8675. If you would rather not be recorded, please say so, or hang up now.” If you object, we end the call rather than continue recording, and you can hang up at that point instead
• Calls to our business line, and sales or consultation calls: Calls placed to our own business number, and sales or consultation calls we conduct with you, may be recorded for quality and training purposes. Where a call is recorded, you are notified — either by an automated spoken notice before the call connects, or verbally by our team at the start of the call

Business Contact Information From Public Sources

For our own business-to-business outreach to roofing companies, we collect business contact information from public sources — such as public business listings (including Google business profiles), company websites, state contractor-license registries, the Better Business Bureau, and business directories — including business name, business address, business phone, website, and the owner's name, title, and business email address. We may use third-party services to verify that a business email address is deliverable. We use this information solely to contact businesses about our services. Every such email includes our postal address and a working opt-out; opt-out requests are added to a permanent suppression list and honored promptly. We do not cold-contact homeowners or consumers.

Information Collected Automatically

• Usage data: Features used, conversation volumes, appointment counts
• Server logs: Standard web-server request logs
• Booking-link measurement: When you click one of our booking links (e.g. /book), we log the link path, traffic source, browser user agent, referring page, and a truncated IP prefix — the first three parts of the address only, never your full IP address. Where the link was sent to you personally, we also log the business email address, phone number and company name that link was addressed to, together with which message in the sequence and which version of it you clicked, so that we can attribute the click to the message we sent you
• Email engagement: Whether an email we sent was delivered or opened

Stored in Your Browser

Our onboarding and intake forms autosave your draft answers to your own browser's local storage on your device (not on our servers) so you don't lose progress; the draft is cleared when you submit. If you use a shared computer, submit the form or clear your browser storage when done.

2. How We Use Information

We use collected information to:

• Provide, maintain, and improve the Service
• Answer, qualify, and respond to your leads by voice, SMS, and email on your behalf
• Schedule appointments on your connected calendar
• Process payments and manage your subscription
• Send you service-related communications (onboarding emails, performance reports, billing notices)
• Contact roofing businesses about our services (B2B outreach, with opt-out)
• Analyze usage patterns to improve the product
• Comply with legal obligations

We do not sell your personal information or your leads' information, use your lead data to market our own services to your leads, share lead conversation data with other LeadCatch clients, or cold-contact consumers.

3. How We Share Information — Service Providers

We share information only with service providers that process data on our behalf, and only as needed to run the Service:

• Twilio — telephony and SMS delivery (carries call audio and text messages)
• Anthropic (Claude) — AI language processing of lead conversations and call transcripts
• ElevenLabs — voice synthesis of the AI assistant's spoken responses (receives only the text the assistant says, never caller audio)
• Google — calendar integration, account sign-in (OAuth), and public business-listing data
• Stripe — payment processing
• Brevo — email delivery and inbound email processing
• Resend — transactional email delivery
• Instantly — email delivery infrastructure, when in use
• MillionVerifier — verification that business email addresses are deliverable
• Hunter.io — business contact enrichment from public data
• Supabase — database hosting
• Vercel — website and application hosting
• Calendly — discovery-call scheduling
• Sentry — application error monitoring (error reports may include account identifiers)
• Google (Gmail) / ImprovMX — business mailbox hosting and email forwarding
• Telegram — real-time delivery of new-lead and booking alerts to the client and our operations team (an alert may include a lead's name and phone number)
• Notion — customer-relationship records for our prospects and clients (business contact details)
• Cloudflare — secure network tunneling of inbound call connections to our call-processing server (call audio transits Cloudflare's network in the connection path)
• ntfy — backup delivery channel for operational alerts when the primary channel is unavailable
• OpenPhone — business phone service for our own sales and consultation calls; it places, records, and transcribes those calls, and the transcript together with the participants' phone numbers is stored in our database
• Google (Gemini API) — AI-assisted research of publicly listed businesses, for our own business-to-business outreach and market research (receives only location and category search terms; never a lead's, homeowner's, or client's personal information)
• Meta (Facebook and Instagram) — where a client enables Facebook or Instagram messaging as a lead channel, replies to comments and direct messages are delivered through Meta's platform (Meta already holds the message the sender wrote). These channels are off by default
• Client-designated CRM (for example JobNimbus, AccuLynx, Jobber, or ServiceTitan) — where a client connects their own CRM, we push that client's lead records (name, phone, email, and property address) into it at the client's direction
• OpenStreetMap (Nominatim) — geocoding of city and state names for outreach planning (receives only place names; never personal information)

We may also disclose information: (a) if required by law, regulation, legal process, or governmental request; (b) in connection with a merger, acquisition, or sale of assets, in which case your data may be transferred to the acquiring entity; or (c) with your consent, for any purpose you explicitly authorize.

Mobile information and text-messaging consent

All of the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. We do not share, sell, rent, or provide your mobile phone number or your text-messaging consent data to third parties or affiliates for marketing or promotional purposes. Your phone number is disclosed only to (a) the roofing company you yourself contacted, so that it can schedule and complete the work you asked it about — that company is the business you reached out to and the party whose service you requested, not a third-party marketer — and (b) the service providers listed in this section, which handle it on our behalf for the purposes described there. In each case it is used only for those purposes and for nothing else. Consent you give to receive text messages from us is never transferred to another company for that company's own marketing. Full text-message program details — including message frequency, HELP and STOP instructions, and the fact that message and data rates may apply — are set out in our Messaging Policy.

Google Calendar data — Limited Use disclosure

LeadCatch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. When a roofing-company client connects their Google Calendar, LeadCatch requests exactly two Calendar scopes: calendar.events (create and manage calendar events) and calendar.events.freebusy (read only whether a given block of time is busy or free), together with the low-sensitivity openid and email scopes used solely to confirm which Google account was connected. We request no other Calendar scope — in particular not the full calendar or calendar.readonly scope, which would expose the contents of existing entries — and no other Google data (Gmail, Drive, Contacts, or otherwise) as part of this integration.

We use that access for exactly one purpose: booking an appointment onto the connected account's own calendar when an appointment is set with that client's leads, so it appears on the calendar the client already uses. Before creating the event we check the proposed time slot against the connected calendar's free/busy status, so we never double-book over something already on it. That check returns only busy-or-free time ranges — it does not return, and we do not receive, the titles, descriptions, guests, locations, or any other contents of the client's existing calendar entries. Google Calendar data obtained through this integration is not used for advertising of any kind, is not sold or shared with any third party for that third party's own purposes, and is not used to train generalized artificial-intelligence or machine-learning models. It is stored only for the purposes described in this policy, retained under the same terms as the rest of your account data (Section 4), and access can be revoked at any time from your Google Account permissions or by contacting us at the address in Section 12.

Google Ads data — Limited Use disclosure

LeadCatch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. When a roofing-company client connects their Google Ads account, LeadCatch requests a single scope: https://www.googleapis.com/auth/adwords. We request no other Google Ads scope. Because the consent request is incremental (include_granted_scopes), the token Google returns may also carry scopes you granted us earlier for a different feature — Google Calendar, for example; each of those is used only for the purpose disclosed where it was granted, and never for this one. Google publishes no narrower read-only variant of that scope, so although the access Google grants is technically capable of making changes, our software issues read requests only: it calls GoogleAdsService.Search to retrieve Local Services Ads leads (the local_services_lead resource) and calls listAccessibleCustomers once, immediately after consent, to identify which Google Ads accounts the client has authorized. No code path in our system creates, edits, pauses or deletes anything in a client's Google Ads account — we issue no mutate calls of any kind, and the tool has no interface for campaign, budget or ad management.

We use that access for exactly one purpose: retrieving new Local Services leads for the connected account and handing each one to that client's own automated assistant, so the homeowner gets a fast reply. The information we receive is the contact and job detail the homeowner submitted to Google — such as name, phone number, the service requested and the location. Google Ads data obtained through this integration is used only to service the client whose account it came from. It is not used for advertising of any kind, is not sold, rented or shared with any third party for that third party's own purposes, is not combined across clients into aggregate, benchmark or resale products, and is not used to train generalized artificial-intelligence or machine-learning models. The refresh token that authorizes this access is encrypted at rest (AES-256-GCM) and is never shared; if encryption is unavailable the connection fails rather than storing the token in plain text. It is stored only for the purposes described in this policy, retained under the same terms as the rest of your account data (Section 4), and access can be revoked at any time from your Google Account permissions or by removing the link in your Google Ads account — removal stops all retrieval immediately.

4. Data Retention

• Active accounts: Data is retained for the duration of your subscription.
• Closed accounts: Lead data, conversation data, call recordings, and call transcripts are retained after account closure until you ask us to delete them — we have no automatic purge schedule. You may request deletion in writing at any time and we will delete within 30 days of your request. Account and billing records are retained for 7 years for tax and legal compliance.
• Outreach prospects: Business contact information is retained while relevant to our outreach; if you opt out, your address is added to a suppression list that we retain indefinitely so the opt-out is honored.
• Website signups: Email addresses collected through our website are retained until you unsubscribe.

5. Data Security

We implement industry-standard security measures including TLS encryption for all data in transit, encrypted storage for sensitive credentials (API keys, tokens), access controls limiting access to customer data, and security reviews of third-party integrations. No system is 100% secure. We cannot guarantee absolute security, but we take reasonable measures to protect your data.

In the event of a data breach that compromises your personal information, we will investigate promptly and notify affected clients — and, where required, affected individuals and applicable regulators — without undue delay and consistent with the timelines required by applicable law.

6. Your Rights and Choices

Depending on your jurisdiction, you may have the right to access, correct, delete, or export your personal information, opt out of marketing communications, and withdraw consent for data processing. To exercise any of these rights, use our Data Opt-Out page or email inquiry@leadcatch.homes. We will respond within 30 days.

• Opt out of data collection entirely: Visit leadcatch.homes/data-opt-out — one request removes your information from our records and adds you to a permanent do-not-contact list.
• Email opt-out: Reply to any email from us with "unsubscribe" (or use the opt-out instructions in the email). Opt-outs are added to a permanent suppression list.
• Text message opt-out: Reply STOP — or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE, or OPTOUT — to any text message from us. The opt-out is honored immediately, automatically, on receipt; it applies to every message sent to that number; and the number is kept on a suppression list so the opt-out continues to be honored. You receive one confirmation message and nothing after it. The only way to start receiving messages again is to reply START, UNSTOP, or RESUBSCRIBE yourself. Reply HELP or INFO for assistance. Full program detail is in our Messaging Policy.
• Homeowner leads: If you contacted a roofing contractor and your data was processed by LeadCatch on that contractor's behalf, we will refer your request to that contractor and support them in honoring it.

7. Cookies and Tracking

We keep this simple and honest:

• No advertising or analytics cookies. Our marketing website does not use third-party analytics, advertising pixels, or cross-site tracking of any kind.
• Essential cookies only: The client dashboard uses session cookies strictly for login/authentication.
• First-party measurement: Booking-link clicks are logged server-side as described in Section 1 (with truncated IP).
• Email open detection: An email we send you may contain a small first-party image that loads when the message is opened, which is how we know whether it was opened (Section 1). It sits in the email, not on our website; it is not used for advertising, profiling, or cross-site tracking; and blocking remote images in your email client prevents it entirely.
• Local drafts: Onboarding forms save drafts to your own browser's local storage, as described in Section 1.

Because we do not use tracking cookies, no cookie consent banner is presented.

8. Children's Privacy

The Service is not directed to individuals under 18. We do not knowingly collect information from children. If we learn that we have collected data from a child under 18, we will delete it promptly.

9. State Privacy Rights (California and Other States)

If you are a California resident, the California Consumer Privacy Act (CCPA, as amended by the CPRA) gives you the right to: know what personal information we collect, use, and disclose; access and correct your personal information; delete your personal information (subject to legal retention requirements); opt out of the sale or sharing of personal information — we do not sell or share personal information as those terms are defined by the CCPA; limit the use of sensitive personal information — we do not use sensitive personal information beyond what is necessary to provide the Service; and not be discriminated against for exercising these rights.

Residents of other states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, and Oregon) may have similar rights of access, correction, deletion, portability, and opt-out. To exercise any state privacy right, use our Data Opt-Out page or email inquiry@leadcatch.homes; you may use an authorized agent where the law allows. We will verify your request and respond within the time required by the applicable law.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email at least 14 days before taking effect. The "Last Updated" date at the top reflects the most recent revision.

11. Scope and Legal Effect

The Service is intended for businesses and residents located in the United States. It is not directed to, or intended for, individuals in the European Union, the United Kingdom, or other jurisdictions outside the United States, and we do not knowingly process the personal data of individuals located there.

This Privacy Policy describes our data-handling practices. It is not a contract, does not create any contractual rights or third-party-beneficiary rights in any person, and is not intended to expand our obligations beyond those imposed by applicable law. The legal relationship between LeadCatch and its clients is governed by the separate written agreement between them; in the event of any conflict between that agreement and this Policy, the written agreement controls.

12. Contact

For privacy-related questions or requests, email inquiry@leadcatch.homes.
LeadCatch LLC — Knoxville, Tennessee, USA.
Mailing address (registered agent): 116 Agnes Rd, Ste 200, Knoxville, TN 37919, USA.