Your workspace should feel private.
Last updated 10 October 2026
Operator and contact
LeadPilot is operated by Ali Paragulgov, Tbilisi, Georgia. Contact the operator through the Support page or at 95ali06@gmail.com.
What we collect
When you sign in with Google, LeadPilot receives your Google account identifier, verified email address and display name. When you use ChatGPT sign-in, we receive the account identifier, email and available name supplied by that service. LeadPilot never receives your Google or ChatGPT password. We store the business profile, leads, notes, proposals, templates and activity that you choose to add.
How we use it
We use this information only to authenticate you, provide your workspace, save your changes, improve reliability and understand basic product usage. We do not sell your data.
Storage, cookies and access
Application data is stored through the hosting platform and is separated by your authenticated user identifier. Other users can access your workspace only if you grant them team membership. Permissions can limit records and custom fields. Google sign-in creates a secure, HTTP-only session cookie for up to seven days. Google may also set cookies needed to complete sign-in under its own privacy terms.
Optional tools
Team membership, booking names and email addresses, manual financial entries and audit events are stored with the workspace. Google session records support session revocation. Enabled webhooks send event type, record identifier and timestamp to the HTTPS endpoint you configure. Read-only API keys grant access to workspace records; protect and revoke them when unused.
Optional Pro payments
When Pro checkout is enabled, Paddle collects and processes payment and billing details under its own privacy policy. LeadPilot stores the workspace identifier, provider customer, transaction and subscription identifiers, paid-period dates and payment-event identifiers to verify access and prevent duplicate processing. Card details are entered in Paddle checkout and are not stored by LeadPilot. Payment records are retained separately from client content for billing, dispute handling and abuse prevention. Deleting workspace records does not cancel a recurring subscription; use Manage subscription first.
Offline copies
Offline access is optional. When enabled, selected names, notes, dates and budgets are encrypted in browser storage with your offline passphrase. The passphrase is not sent to LeadPilot. Remove this copy on shared devices. Signing out or deleting server data does not automatically remove browser copies or downloaded backups.
Your choices
You can download a full JSON backup or export contacts as CSV and delete your LeadPilot workspace data from Settings. Deleting product data does not delete your Google or ChatGPT account.
Support and retention
Support requests include your email, message and account identifier when signed in. The operator can read them to provide support. Records remain until you delete your workspace. Deleted leads stay in Trash until workspace deletion or replacement by a backup. Product events are retained for up to 90 days and are cleaned up when new events arrive. Product events are removed on workspace deletion. Plan metadata and proposal identifiers used to enforce quotas and prevent reset abuse are stored separately; these do not retain proposal contents. Automatic in-app reminders store an account ID, client record ID and due date and are removed on workspace deletion; anonymous events cannot be linked to an account deletion. Temporary abuse-prevention counters store a hash of your network address and expire after their quota window. Hosting backups may follow the platform’s retention rules.
Early access
LeadPilot is in early access. We may update this notice as the product and its infrastructure develop.