Privacy Policy

Last updated: October 2026 · LeadIntellect Privacy & Data Rights Governance

1. Introduction & Scope

LeadIntellect ("we", "our", "platform") operates a B2B sales intelligence and prospect discovery workspace. We provide professional contact and company information to business users conducting legitimate business-to-business communications. This policy explains how we collect, process, verify, and safeguard personal and business data.

2. Categories of B2B Data Processed

Our B2B index processes professional business identity details including:

  • Professional name, job title, seniority, and department.
  • Corporate business email addresses and domain names.
  • Direct business dial and corporate switchboard phone numbers.
  • Public corporate social profile URLs (such as LinkedIn company and professional pages).
  • Company firmographics (headcount tiers, industry sectors, registered city, state, country).

We do not collect or index sensitive personal data such as political affiliations, religious beliefs, health records, biometric information, or consumer personal financial credentials.

3. Lawful Basis for Processing

We process professional B2B directory information under legitimate interest for professional business-to-business communication. We maintain balanced assessments ensuring that our processing does not override the fundamental rights and freedoms of individuals. Users who do not wish to have their corporate contact details indexed may submit an opt-out request at any time.

4. Your Data Rights & Opt-Out

Any professional has the right to:

  • Request confirmation of whether their business contact details exist in our index.
  • Request immediate suppression and permanent removal of their contact record.
  • Correct inaccurate business title, company affiliation, or location details.

To submit an opt-out or removal request, visit our Data Use & Suppression Registry page or email privacy@leadintellect.ai.

5. Data Retention & Security

All account credentials and API keys are stored server-side with industry-standard cryptographic hashing and encryption in transit (TLS 1.3). We review dataset freshness on scheduled cycles to retire decayed or stale records.