Privacy Policy

1. Summary

LeadsIn is designed to help you collect publicly available local business information, organize leads, generate outreach drafts, send or schedule emails through providers you configure, and track engagement events such as delivery, opens, clicks, bounces, unsubscribes, and replies.

Most LeadsIn workspace data is stored locally in your browser using Chrome extension storage. Leadsin does not sell your personal information, lead lists, email content, AI prompts, browsing activity, or customer data.

2. Chrome Web Store Limited Use Disclosure

LeadsIn complies with the Chrome Web Store User Data Policy, including the Limited Use requirements, by limiting use of extension data to the single purpose of providing and improving the LeadsIn lead generation, outreach, follow-up, and reporting workflow.

• We do not sell user data.
• We do not use or transfer user data for personalized advertising.
• We do not allow humans to read user data unless you ask us for support, it is required for security, or it is required by law.
• We transfer data to third parties only when needed to provide a user-facing feature you configure, such as AI drafting, email sending, license verification, or payment processing.
• We do not collect web browsing activity except as necessary for user-facing extension features, such as extracting leads from Google Maps pages you use with LeadsIn or researching lead websites when you enable that workflow.

3. Information LeadsIn May Process

Workspace and lead data

This includes campaign names, search queries, local business names, addresses, phone numbers, email addresses, websites, categories, ratings, review counts, notes, scores, lead type, and imported CSV contact data.

Outreach and email data

This includes email drafts, subjects, bodies, attachments selected by you, sender settings, follow-up drafts, scheduled follow-ups, quick email content, send history, reply status, delivery events, opens, clicks, bounces, unsubscribes, complaints, and suppression records.

AI provider configuration and prompts

If you configure an AI provider, LeadsIn may send prompts to that provider that include your company profile, offer details, lead details, research snippets, and drafting instructions needed to generate useful outreach. Your API keys are stored in Chrome extension storage on your device.

Email provider configuration

If you configure Plunk, Resend, Mailgun, a private relay, SMTP, IMAP, or unsubscribe endpoints, LeadsIn processes the keys, tokens, sender accounts, recipient information, message content, and event data needed to send and track emails.

License and purchase data

LeadsIn may process license keys and related validation responses. Purchases are handled by Gumroad or another checkout provider shown at the time of purchase. We do not store full payment card information inside the extension.

Technical data

LeadsIn may process extension settings, feature toggles, local logs, error messages, timestamps, provider response statuses, and backup/export files created by you.

4. How We Use Information

• To extract and organize leads from pages where you intentionally run LeadsIn.
• To score and classify leads as Hot, Warm, or Cold based on research and engagement signals.
• To generate, format, review, save, send, and schedule outreach emails and follow-ups.
• To sync provider activity such as delivery, opens, clicks, bounces, unsubscribes, complaints, and replies.
• To import contacts from CSV files and export CSV, XLSX, or backup files at your request.
• To verify licenses, provide support, troubleshoot errors, prevent abuse, and maintain extension security.

5. Third-Party Services

LeadsIn may send data to third-party services only when you configure or request a feature that requires that service. Depending on your settings, these services may include:

• AI providers such as OpenAI-compatible providers, Anthropic Claude, Amazon Bedrock, OpenRouter, Groq, MiniMax, DeepSeek, or Ollama endpoints you configure.
• Email and delivery providers such as Plunk, Resend, Mailgun, SMTP/IMAP mailboxes, and private HTTPS relays.
• License, payment, or checkout providers such as Gumroad.
• Support tools when you voluntarily contact us and share details for troubleshooting.

Those third-party services process information according to their own terms and privacy policies. You are responsible for reviewing provider policies before connecting them to LeadsIn.

6. Storage, Security, And Retention

LeadsIn stores workspace data primarily in Chrome extension storage on your device. The extension uses Chrome storage permissions, including local storage capacity, so it can keep lead records, settings, drafts, events, and attachments needed by your campaigns.

When data is sent to AI, email, license, relay, or payment providers, it is transmitted over HTTPS where supported by the provider endpoint. You should protect your device, Chrome profile, API keys, mailbox credentials, relay tokens, and exported files.

Data remains in your browser until you delete it, uninstall the extension, clear Chrome extension storage, or a provider retains data under its own policy. Exported files remain wherever you save them.

7. Your Choices And Controls

• You can choose draft-only mode instead of connecting an email provider.
• You can disable modules such as follow-ups, email sending, reply detection, unsubscribe sync, compliance footer, or auto CSV export where available in settings.
• You can review and edit drafts before sending.
• You can delete leads, drafts, follow-ups, attachments, and campaign data from the extension UI.
• You can export CSV, XLSX, and backup files when you want a copy of your data.
• You can revoke provider keys by removing them in LeadsIn and rotating or deleting them inside the provider dashboard.

8. Outreach Compliance

LeadsIn provides tools for outreach, but you are responsible for using those tools lawfully. You must comply with applicable email, privacy, anti-spam, consumer protection, platform, and data protection laws, including rules about consent, opt-out, identification, and truthful messaging.

Do not use LeadsIn to send deceptive, unlawful, harassing, or high-volume spam messages. Use unsubscribe and suppression features when required and honor recipient opt-out requests promptly.

9. Children

LeadsIn is not intended for children under 13 and is not designed for personal use by minors. Do not use LeadsIn to collect information from children.

10. Changes To This Policy

We may update this Privacy Policy as LeadsIn changes or as legal, provider, or Chrome Web Store requirements change. The updated policy will show a new "Last updated" date.

11. Contact

For privacy questions, support requests, or deletion questions, contact Leadsin at support@leadsin.im.

Website: https://leadsin.im