Lead Data,
Handled Carefully.
How verified lead data moves through PeakIntent, what we collect, how it's protected, who processes it, and how consumers stay in control.
Data In Transit
All connections between consumers, the PeakIntent platform, verification vendors, and provider CRMs use TLS. Webhooks delivered to provider CRMs use HTTPS endpoints; HTTP-only endpoints are not supported.
What We Collect
During the inbound funnel, PeakIntent collects only what is needed to qualify and route a lead:
- Service category and stated need
- ZIP code or service address
- Name, email, phone
- Verification artifacts (deliverability result, SMS OTP success)
- Timing or urgency, if the prospect provides it
Vendors That Process Lead Data
PeakIntent uses a small set of specialized vendors. Each is bound by its own privacy and security commitments.
- Bouncer.io, email deliverability validation
- MessageCentral, SMS one-time-password verification
- Mailgun, transactional email delivery
- OpenAI, pricing computation and spam scoring (standard API tier; data is not used for model training)
- GoHighLevel, default CRM forwarding
- Zapier and n8n, bridges to 30+ customer-configured CRMs
Retention
Lead data is retained for as long as needed to complete delivery, billing, and dispute resolution. After that, identifiable lead information is removed from operational systems; aggregate analytics are retained in de-identified form.
Consumer Controls
- Reply STOP to any SMS to opt out of further messages
- Use the unsubscribe link in any email
- Email [email protected] with deletion or correction requests; see the privacy policy for details
Reporting a Concern
Security concerns can be reported to [email protected]. Please include enough detail to reproduce or verify the issue.
Security Frequently Asked Questions
Quick answers about transmission, retention, vendors, and opt-out.
Have a Security Question?
Email us at [email protected], we read every message.