Encrypted connections
LeadPilot HQ is delivered over HTTPS so information sent between your browser and the platform is encrypted while in transit.
LeadPilot HQ Security
LeadPilot HQ uses modern infrastructure, access controls, encrypted connections, and trusted payment services to help protect the platform and the information stored within it.
LeadPilot HQ is delivered over HTTPS so information sent between your browser and the platform is encrypted while in transit.
Account authentication is managed through Supabase. Password-reset and email-confirmation links use secure, time-sensitive verification flows.
Subscription payments and billing information are handled through Stripe. LeadPilot HQ does not directly store complete payment-card numbers.
Database policies are used to help prevent one account from accessing another account’s private business, lead, and conversation information.
Rate limits and automated verification tools help reduce spam, excessive requests, and misuse of public-facing forms and AI features.
LeadPilot HQ uses browser security headers that restrict unnecessary access to features such as location, camera, and microphone permissions.
Security is a shared responsibility. Account owners should use a strong, unique password, protect access to their email account, sign out of shared devices, and avoid sharing login credentials with unauthorized individuals.
Businesses using LeadPilot HQ are also responsible for collecting and using customer information lawfully and for providing any privacy notices required for their business.
Do not publicly disclose a suspected vulnerability or include sensitive customer information in your first message. Send a clear description of the issue to our support address.
Report a Security Concern