Effective April 28, 2026
Privacy Policy
This policy is written for the LeadGuard.Pro AI call catcher product, including call answering, missed-call textback, transcripts, SMS/MMS, knowledge base setup, website scraping, and account login.
This is a product-ready policy draft, not legal advice. Have counsel review it before production launch.
Overview
This Privacy Policy explains how LeadGuard.Pro collects, uses, shares, and protects information when businesses use our AI call catcher, dashboard, websites, messaging tools, and related services.
LeadGuard.Pro is built for service businesses that want an AI system to answer missed calls or send text-message follow-ups after missed calls.
Information We Collect
Account information: business name, owner name, email address, phone number, login information, billing status, and connected-service settings.
Business profile information: trade, service areas, hours, website URL, offered services, policies, call scripts, emergency handling rules, and knowledge base content.
Call and messaging information: caller phone numbers, call times, recordings if enabled, transcripts, summaries, SMS/MMS bodies, media URLs, consent-to-text indicators, and job details provided by callers.
Integration information: identifiers and tokens needed to connect services such as Google login, Twilio, Vapi, Stripe, and optional calendars. Sensitive tokens should be encrypted before storage in production.
Usage and device information: IP address, browser type, pages viewed, timestamps, diagnostics, and security logs.
How We Use Information
Provide the AI call catcher, missed-call textback, dashboard, setup flows, lead summaries, and customer messaging features.
Configure the AI assistant using the business knowledge base, service catalog, voice selection, scripts, and safety escalation rules.
Route communications, detect errors, prevent abuse, secure accounts, process billing, and comply with legal obligations.
Improve reliability, support onboarding, troubleshoot integrations, and develop product features.
AI Processing
LeadGuard.Pro may process call transcripts, message bodies, uploaded media metadata, and business knowledge base content with AI systems to generate responses, summaries, classifications, and routing recommendations.
Businesses are responsible for ensuring their uploaded knowledge, scripts, and caller disclosures are accurate and lawful for their location and industry.
The AI should not be configured to provide emergency medical, legal, financial, or dangerous technical advice. Safety-related calls should be escalated according to the configured policy.
Call Recording and Messaging
If call recording or transcription is enabled, callers may be recorded and transcribed. Businesses are responsible for providing any legally required notice or consent for call recording in the areas where they operate.
SMS/MMS features may be subject to carrier rules, A2P 10DLC registration, opt-out requirements, and messaging compliance obligations.
How We Share Information
Service providers: hosting, database, voice AI, telecom, analytics, payments, authentication, email, and support providers that help operate LeadGuard.Pro.
Customer-directed integrations: services connected by the business, such as Google login, Twilio, Vapi, Stripe, and optional calendar tools.
Legal and safety: when required by law, legal process, security obligations, or to protect rights, safety, and service integrity.
Business transfers: in connection with a merger, acquisition, financing, or sale of assets.
Data Retention
We retain account, business, lead, call, message, and integration records for as long as needed to provide the service, comply with legal obligations, resolve disputes, enforce agreements, and maintain security.
Businesses should be able to request deletion or export of their account data, subject to legal, billing, security, and backup retention requirements.
Security
We use administrative, technical, and organizational safeguards designed to protect information. No online service can guarantee absolute security.
Production deployments should verify webhook signatures, restrict service-role keys to server routes, encrypt OAuth refresh tokens, protect recordings/transcripts behind authentication, and apply row-level access controls.
Your Choices
Businesses may update profile information, bot scripts, voice settings, services, and knowledge base entries in the dashboard.
Callers may request that the business update or delete information associated with a lead, subject to the business's obligations and LeadGuard.Pro's retention requirements.
Users may opt out of non-essential marketing communications. Transactional and service messages may still be sent.
Children
LeadGuard.Pro is intended for business use and is not directed to children under 13. We do not knowingly collect personal information from children under 13.
Changes
We may update this Privacy Policy from time to time. The updated policy will be posted with a new effective date.
Contact
Privacy questions can be sent to privacy@leadguard.pro. Replace this address with the production support contact before launch.