Data Usage & Discovery Policy

This policy applies to business information and discovery activity processed through LeadForge’s Discovery, LeadForge, Targeted, and Copilot Discovery modes, together with related territory, lead, and business-index records.

It does not replace the Privacy Policy, Billing & Usage Policy, Acceptable Use Policy, or Data Retention & Deletion Policy. Those documents govern related privacy, billing, acceptable-use, and retention questions.

LeadForge may obtain business information from public or commercially available sources, mapping and business-listing services, business websites, provider APIs, the existing LeadForge index, user-provided information, and other sources used to support business discovery and sales intelligence.

Depending on availability, business records may include names, categories, locations, websites, phone numbers, email addresses, addresses, ratings or review counts, public business metadata, external identifiers, and other business-facing information.

Third-party and public-source data can be incomplete, stale, duplicated, or inaccurate. LeadForge does not represent that every external record is current or complete, and users should verify material information before relying on it for outreach, contracting, compliance, or other consequential decisions.

Discovery mode is designed to find businesses that are new to the LeadForge index rather than simply returning already-known indexed businesses.

A qualifying newly returned business consumes Discovery capacity under the applicable plan. Candidates that are evaluated but not returned as qualifying new results do not consume Discovery capacity.

Discovery results may be deduplicated, filtered, normalized, rejected, or matched against existing LeadForge records before they are shown to the user.

LeadForge mode searches the existing LeadForge business index.

Businesses returned from the existing index do not consume Discovery capacity merely because they are surfaced again through LeadForge mode.

Indexed records may reflect business information previously discovered, normalized, refreshed, or otherwise retained by LeadForge in accordance with this policy and the Data Retention & Deletion Policy.

Targeted mode is designed to locate a specific named business or chain and requires a Business Name.

Targeted requests may evaluate multiple candidates in order to identify the requested business or matching locations. Candidates that are rejected or not returned do not consume Discovery capacity.

If Targeted mode returns a business that qualifies as newly discovered under the current product rules, that returned business may consume Discovery capacity. Known LeadForge index results do not consume Discovery capacity merely because they are returned through Targeted mode.

Copilot Discovery allows users to describe the businesses they want to find using natural-language instructions.

Copilot Discovery may interpret the request, evaluate known and new business candidates, and return results that satisfy the request.

Copilot Discovery requires a lead target and a maximum Discovery allowance. It checks eligible fresh directory businesses the user has not previously discovered first, then uses external searches to fill remaining slots within the allowance. Directory results and IDs-only lookups use no Discoveries. Each successful paid Google business-detail lookup uses one Discovery, including businesses that do not match. Failed detail lookups do not consume customer Discoveries. A search can consume Discoveries without returning matches. AI usage may apply separately. Hard requirements remain enforced, and broader searches without a location or industry require confirmation.

Because Copilot Discovery uses AI-assisted processing, AI usage may apply in addition to Discovery usage where indicated by the product.

Discovery accounting is based on qualifying returned results rather than every external lookup, candidate evaluation, deduplication check, or rejected result performed behind the scenes.

LeadForge may use identifiers, normalized fields, prior index state, provider metadata, business attributes, and other matching logic to determine whether a result is already known or qualifies as new.

The Billing & Usage Policy governs plan allowances, metering, corrections, and disputes concerning Discovery usage.

LeadForge applies record-matching and deduplication logic to reduce duplicate business records and avoid repeatedly treating the same business as newly discovered.

Matching may use provider identifiers, normalized business names, websites, phone numbers, addresses, geographic information, or other business attributes where available.

Automated matching is not infallible. Distinct businesses may share similar attributes, and the same business may appear differently across providers or locations. LeadForge may merge, separate, or correct records as its matching systems improve.

Discovery activity may be organized into territories and persisted discovery sessions so users can return to prior work, expand coverage, and avoid unnecessarily repeating the same search state.

Successful discovery results may remain available until a later successful search replaces or expands the active result set according to the product workflow.

Territory and discovery-session records are intended to support continuity, collaboration, analysis, and later workflow actions rather than functioning as a transient one-time search response.

LeadForge currently uses a 120-day freshness period for discovery-session caching and related business discovery records. The freshness period determines when LeadForge may treat previously retrieved data as sufficiently recent for reuse or when it may refresh or re-query underlying sources.

A 120-day freshness period is not the same as automatic deletion after 120 days. Discovery, territory, and lead records may continue to be retained where needed for product continuity, customer records, usage history, legal obligations, or other purposes described in the Data Retention & Deletion Policy.

Refreshing a business record may update some fields while preserving identifiers, prior workflow state, ownership, notes, intelligence, or other records associated with that business.

Discovering a business and unlocking a lead are separate product actions.

Lead unlocks are free and do not consume a separate paid usage unit. Unlocking may make additional contact information, Lead Intelligence, workflow actions, outreach tools, or other lead-level features available according to plan and permission rules.

Once a business becomes part of a user’s or Workspace’s lead workflow, LeadForge may retain the associated lead record independently of the freshness period that applies to discovery-session caching.

Lead Intelligence is a separate researched intelligence artifact and should not be treated as identical to a raw discovery result or score-derived business summary.

LeadForge may use discovered business information, public website content, business metadata, customer-provided context, and other permitted sources to build or refresh Lead Intelligence.

Lead Intelligence may also use a 120-day freshness period for determining when researched intelligence should be considered current enough for reuse or due for refresh. That freshness period is not an automatic deletion schedule.

Lead Imports and other customer-provided records are not treated as newly discovered businesses merely because they enter LeadForge through an import workflow.

Imported records may be matched against existing LeadForge businesses, deduplicated, enriched, or connected to Lead Intelligence and other product features.

LeadForge may preserve source headers, original rows, mapping information, and related import evidence so that import history, review, reconciliation, and downstream records remain traceable.

LeadForge uses business discovery information to provide territories, lead records, contact views, scoring, Lead Intelligence, Business Partner Tasks, Pitch Decks, Copilot context, Daily Actions, reporting, outreach preparation, and other product workflows.

LeadForge may also use operational information about discovery requests, matching, provider responses, freshness, failures, and usage events to maintain, secure, troubleshoot, and improve the Service.

Customer use of discovered information remains subject to applicable privacy, marketing, communications, recording, consumer-protection, and other laws that govern the customer’s intended use.

Discovery features are intended for legitimate business-development, agency, research, and sales-intelligence workflows.

Users may not scrape, reconstruct, mirror, resell, sublicense, or bulk-extract substantial portions of the LeadForge index or provider-derived data in order to create a competing dataset, evade product controls, or use LeadForge as an unauthorized bulk data feed.

Users may not use automated systems, multiple accounts, coordinated Workspaces, or technical manipulation to circumvent Discovery accounting, rate limits, provider restrictions, or other safeguards.

Ordinary use of business records for a customer’s own lawful sales, outreach, client-service, research, account-planning, and agency operations is permitted subject to the Terms of Service and Acceptable Use Policy.

LeadForge relies on third-party providers for some business listings, geographic data, websites, infrastructure, and related source information.

Availability, coverage, accuracy, rate limits, terms, and response times may depend on those providers. A provider may change or remove information without notice to LeadForge.

LeadForge may substitute providers, change source priority, refresh logic, matching rules, or retrieval methods as needed to operate and improve the Service.

LeadForge may correct, merge, suppress, refresh, or otherwise update business records when it identifies stale information, duplication, conflicting source data, or matching errors.

Users who identify a material business-data error may report it through LeadForge Support. LeadForge may review the underlying source, matching history, provider data, and related system records before deciding whether a correction is appropriate.

A correction to a business record does not necessarily alter historical usage, activity, imports, messages, or other records that accurately reflected what the platform showed at the time.

LeadForge may update this policy as Discovery modes, providers, index architecture, freshness rules, AI-assisted discovery, matching systems, or business-data workflows evolve. The current version and last-updated date will be published in the Legal & Trust Center.