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.

LeadsIn may process account information, page content you intentionally submit to the extension, lead and campaign records, email content, provider credentials, and technical information. Some data stays in Chrome extension storage; signed-in users may also enable cloud sync through our Firebase/Google Cloud backend. 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 directory pages you use with LeadsIn or researching lead websites when you enable that workflow.

3. What We Collect And How We Collect It

LeadsIn collects information only when you provide it, sign in, import it, activate an extension feature, connect a provider, or ask the extension to synchronize or send information. The extension does not record your entire browsing history. When you intentionally run a LeadsIn workflow on a supported page, it may read the page URL, page title, visible business listings, contact details, and requested website content needed to perform that workflow.

Information you provide directly

This includes your account email and password during sign-in, display name and profile settings, company profile, campaign instructions, API keys or tokens you enter, CSV files, attachments, feedback, and support messages.

Information collected from pages you use

This includes business names, addresses, phone numbers, email addresses, websites, categories, ratings, review counts, page URLs, page text, website text, social links, and other public business information that you ask LeadsIn to capture or research.

Information received from connected services

When you connect an AI or email provider, LeadsIn may receive model responses, send results, message identifiers, delivery events, opens, clicks, bounces, complaints, replies, unsubscribe events, and suppression records from that provider.

Account, usage, and technical information

This includes your Firebase user ID, account email, authentication tokens, plan and usage counters, extension settings, feature toggles, local logs, error messages, timestamps, provider response statuses, and backup/export files created by you.

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. Any AI API key stored by a direct client-side integration is kept in Chrome extension storage on your device. If the request uses the LeadsIn server-managed AI configuration, the key is held in the server-side configuration and is not exposed to the extension.

Email provider configuration

If you configure Brevo, Mailchimp Transactional, Mailtrap, Mailgun, Resend, Plunk, SMTP, IMAP, a private HTTPS relay, or an unsubscribe endpoint, LeadsIn processes the keys, tokens, sender accounts, recipient information, message content, attachments, and event data needed to test, send, synchronize, and suppress emails. Custom email-provider credentials are stored in the private server-side provider record for your account, not in the extension workspace.

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. Who Receives Data And Why

LeadsIn shares data only with the parties listed below, and only when needed to provide a feature you use, operate the service, process a purchase, or comply with law. We do not sell user data or share it for cross-context behavioral advertising.

• LeadsIn backend and Google Firebase/Google Cloud: account identity, authentication data, profile data, usage counters, and—when you sign in and cloud sync is enabled—your campaigns, leads, account preferences, and suppression records. Provider credentials are stored in a private server-side database branch.
• Your selected AI service: prompts, company context, lead details, research excerpts, and drafting instructions. Depending on your configuration, this may be OpenAI, Anthropic, Groq, OpenRouter, DeepSeek, MiniMax, Amazon Bedrock, an Ollama endpoint, or another endpoint you configure.
• Your selected email or relay service: sender and recipient addresses, subject and message content, attachments you choose, provider credentials, and delivery or engagement data. Supported services include Brevo, Mailchimp Transactional, Mailtrap, Mailgun, Resend, Plunk, SMTP/IMAP mailboxes, private HTTPS relays, and unsubscribe services.
• Gumroad or the checkout provider shown at purchase: purchase and license information. The payment provider handles payment-card data; LeadsIn does not store full card numbers.
• Website hosting and support providers: ordinary website request data such as IP address, user-agent, and request timestamps when you visit LeadsIn.im, plus any information you voluntarily include in a support request.

These recipients process information according to their own terms and privacy policies. You choose whether to connect them, and you should review their policies before sending them lead, customer, or email data.

6. Storage, Security, And Retention

On your device: LeadsIn stores workspace state, leads, campaigns, drafts, settings, session data, and local event history in Chrome extension storage so the extension can work between browser sessions. You can remove this data by deleting it in LeadsIn, signing out, uninstalling the extension, or clearing the extension's Chrome storage.

On our backend: When you sign in and sync is enabled, LeadsIn stores your Firebase account identity, profile, usage data, synced campaigns, leads, account preferences, and suppression records in Firebase/Google Cloud Realtime Database. Custom email-provider credentials are stored separately in a private server-side record. We do not store full payment-card numbers.

With providers: AI, email, relay, unsubscribe, payment, and license providers may retain data under their own policies. Deleting a record in LeadsIn does not delete copies already sent to a provider or copies in an export you saved. Deleted synced records may remain as synchronization tombstones until no longer needed to prevent an old browser from restoring them.

We use reasonable access controls and HTTPS for supported network requests, but no service or device is completely secure. You should protect your Chrome profile, passwords, API keys, mailbox credentials, relay tokens, and exported files.

7. Your Choices, Deletion, And Requests

• 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.
• You can request access, correction, or deletion of account data by emailing support@leadsin.im. We may need to verify that the request belongs to the account holder.

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