Privacy Policy

This Privacy Policy applies to information processed by LeadForge LLC (“LeadForge,” “we,” “us,” or “our”) when you visit LeadForge websites, create or use a LeadForge account, participate in a Workspace, use LeadForge product features, contact Support, connect third-party services, or otherwise interact with the LeadForge service.

This policy describes LeadForge’s general privacy practices. An executed Data Processing Agreement, enterprise agreement, order form, or other written agreement may provide additional or different terms for particular customer data or processing activities.

LeadForge is designed primarily for business and professional use. Some information processed through the Service may relate to identifiable individuals, including users, customer contacts, business owners, employees, meeting participants, campaign recipients, and other persons represented in customer-provided or publicly available business information.

When you create or maintain a LeadForge account, we may process identity and profile information such as your name, username, profile image, email address, contact email, phone number, time zone, display role, Workspace presence, theme and product preferences, notification preferences, and other account settings you choose to provide.

LeadForge also processes authentication identifiers, session information, Workspace membership, role and permission information, invitation status, and related access-control records needed to authenticate users and determine which Personal or Workspace information they are permitted to access.

Some authentication information is processed through third-party identity services. LeadForge may receive account identifiers and profile information from those providers as necessary to maintain your account and authenticated sessions.

LeadForge supports both Personal and Workspace contexts. Information may therefore be associated with an individual user, a shared Workspace, or both, depending on the feature and selected scope.

Workspace information may include members, roles, access permissions, business records, territories, leads, Vault and pipeline state, activities, tasks, Task Results, Pitch Decks, Lead Intelligence, meeting artifacts, campaign records, usage information, shared work, settings, and other operational records created or used by the Workspace.

Personal information may include user-owned records, preferences, personal activity, Personal Copilot context or memory, and other records that the product identifies as belonging to the individual user rather than the shared Workspace.

Workspace owners and administrators may be able to view, manage, grant, restrict, or revoke access to Workspace information according to the product’s role and permission model. A user’s removal from a Workspace does not necessarily delete records that belong to that Workspace.

LeadForge processes business information used for Discovery, territory analysis, Lead Intelligence, scoring, enrichment, and related sales workflows. This may include business names, locations, industries, websites, phone numbers, email addresses, business-owner or contact names, ratings, reviews, public social or online-presence information, addresses, and other business-related signals.

Business information may come from public sources, mapping and business-directory services, LeadForge’s existing business index, customer imports, user-provided records, or research performed through LeadForge features.

Although much of this information concerns businesses, some records may identify or relate to individual owners, operators, employees, or contacts. LeadForge processes that information as part of the business-intelligence and workflow functions requested by users.

When you use Lead Imports or otherwise provide records to LeadForge, we may process the files, headers, source rows, mapped fields, normalized records, validation results, duplicate-match information, migration reports, and related metadata needed to import and preserve those records.

LeadForge currently retains original import headers and source rows as source-of-truth records for mapping, remapping, validation, migration reporting, and auditability. Those source records may contain business or contact information supplied by the customer.

Customers are responsible for determining that they have authority to provide imported information to LeadForge and to use that information through the Service.

LeadForge uses artificial intelligence and automated systems across features such as LeadForge Copilot, Business Partner Tasks, Lead Intelligence, Pitch Decks, Discovery assistance, Meeting Intelligence, and AI-assisted Support.

Depending on the feature, LeadForge may process user prompts, prior interactions, page context, relevant leads or territories, business records, Workspace or Personal context, pipeline state, generated artifacts, meeting information, support context, and other information necessary to perform the requested task.

LeadForge may create or retain structured Personal or Workspace memory so supported AI features can maintain continuity across interactions. The context available to an AI feature depends on permissions, the selected data scope, and the product surface in use.

AI processing may be performed by LeadForge systems and by third-party model or transcription providers acting as service providers for the applicable request.

When users participate in Team Video Chat, LeadForge may process meeting-participant identity, room and session information, call-state information, and other technical data needed to provide the live meeting experience.

When Meeting Intelligence is enabled with required participant notice and consent, LeadForge may process captured audio, participant information, transcripts, transcript segments, consent records, provenance records, generated meeting artifacts, follow-up information, and approved memory or context derived from the meeting.

Raw Meeting Intelligence capture media is treated separately from retained transcript-derived records. The current capture pipeline is designed to remove successfully processed raw audio chunks after processing, while failed, canceled, or abandoned capture chunks may be retained temporarily for recovery or finalization. Additional details are provided in the Data Retention & Deletion Policy.

If you connect a supported Google or Microsoft mailbox, LeadForge processes the connected account identity, provider identifiers, granted scopes, encrypted authorization credentials, token-expiration information, and other connection metadata needed to maintain the integration.

The current Google integration requests Gmail send access and the current Microsoft integration requests Mail.Send access. These integrations are designed to send Email Campaign messages through the connected mailbox and are not designed to read the contents of the user’s mailbox.

Email Campaign processing may include campaign configuration, sender identity, recipient information, message content, delivery state, failure state, suppression and unsubscribe records, campaign history, and related compliance or audit information.

LeadForge retains suppression and unsubscribe information as necessary to prevent future messages from being sent to recipients who have opted out.

LeadForge processes content and metadata created through Team Threads, direct messages, shared-work cards, and related collaboration features. This may include message content, sender and participant identifiers, timestamps, shared LeadForge objects, thread membership, and status information.

Certain direct-message features may allow communication between LeadForge users outside the current Workspace. Information shared in those conversations may remain available to the other participant even if one user closes or removes the conversation from their own view.

LeadForge may process profile information such as names, usernames, profile images, roles, contact information, time zones, and presence information where those details are used in Team Directory, collaboration, assignment, or communication features.

When you contact LeadForge Support, we may process the content of your support messages together with account, Workspace, page, billing, usage, entitlement, error, diagnostic, and product-context information needed to understand and resolve the issue.

AI-assisted Support may use relevant diagnostic evidence and product context to generate or improve a response. Support and diagnostic records may also be used for troubleshooting, reliability analysis, abuse prevention, incident investigation, and product support quality.

LeadForge does not intentionally expose unrelated customer information to Support workflows when it is not needed to address the request.

LeadForge may process notification preferences and notification-delivery records. If you enable web push notifications, LeadForge stores the push subscription endpoint and associated cryptographic delivery keys provided by the browser or device so notifications can be delivered to that device.

LeadForge may also process ordinary technical information generated through use of a web application, such as browser or device characteristics, network information, timestamps, request metadata, error information, security events, and logs needed to operate, secure, and troubleshoot the Service.

Push-subscription information is used for notification delivery and subscription management rather than for advertising.

If you purchase a paid plan or add-on, LeadForge processes subscription status, plan information, billing identifiers, transaction status, purchased capacity, usage and entitlement information, and other records needed to administer billing and access.

Payment-card processing is handled by LeadForge’s payment provider. LeadForge does not use its application database as a repository for full payment-card numbers.

Billing, usage, and entitlement records may be retained as necessary for account administration, dispute resolution, accounting, tax, fraud prevention, and legal compliance.

LeadForge uses information to provide and operate the Service; authenticate users; enforce Personal and Workspace permissions; perform Discovery, research, AI, collaboration, campaign, meeting, import, notification, and support functions; maintain continuity across user workflows; administer subscriptions and usage; protect security and platform integrity; troubleshoot failures; prevent abuse; comply with legal obligations; and improve the reliability and usefulness of the Service.

LeadForge may use operational data to develop, test, debug, and improve LeadForge features where that use is consistent with the customer relationship, applicable agreements, and law. LeadForge does not treat customer-provided confidential information as public merely because it is processed by the Service.

Where information is used for a materially different purpose that requires additional notice or consent under applicable law, LeadForge will provide that notice or obtain that consent as required.

LeadForge shares information with service providers when reasonably necessary to operate the Service. These providers may support hosting, databases, authentication, payments, artificial intelligence, transcription, video, business discovery, connected email, notification delivery, security, and related infrastructure.

LeadForge may also disclose information when required by law, legal process, or a valid governmental request; when reasonably necessary to protect users, LeadForge, or others from fraud, abuse, security threats, or unlawful activity; in connection with a merger, financing, acquisition, reorganization, sale of assets, or similar corporate transaction; or at the direction of the customer or user.

LeadForge does not sell customer Workspace content or user account data to advertisers or data brokers for their independent advertising use.

The Subprocessors & Service Providers document identifies material providers used in the current LeadForge architecture and explains the functions they perform.

LeadForge integrates with or relies on third-party services including hosting and database providers, authentication and payment services, AI and transcription providers, video infrastructure, Google services, Microsoft services, browser and device push systems, and public business-data services.

When you intentionally connect or use a third-party service, information may be transmitted to that provider as necessary to perform the requested function. Third-party providers may also collect information directly under their own terms and privacy notices when you interact with their services.

LeadForge does not control the independent privacy practices of third parties acting outside their role in providing services to LeadForge or the customer.

LeadForge uses cookies and similar technologies for authentication, session continuity, security, preferences, and essential product operation. Additional information is provided in the Cookie Policy.

LeadForge may also use browser storage or similar client-side mechanisms for product preferences, continuity, and feature state where appropriate.

LeadForge retains different categories of information for different periods based on the purpose of the record, customer expectations, operational requirements, security needs, legal obligations, and applicable agreements.

Some information is intentionally persistent because it forms part of a user’s or Workspace’s business history, while temporary processing data may be removed shortly after its purpose is complete. Deleting one visible object does not necessarily delete independent source records, audit records, billing records, suppression records, or other information that must or may be retained separately.

Detailed product-specific retention practices, including Meeting Intelligence capture media, Discovery and Lead Intelligence freshness, Lead Imports, AI records, campaign data, and deletion requests, are described in the Data Retention & Deletion Policy.

LeadForge uses administrative, technical, and organizational measures designed to protect information against unauthorized access, loss, misuse, alteration, or disclosure. These measures include authenticated access controls, server-side authorization, encrypted network connections, protected application secrets, monitoring, and other safeguards appropriate to the Service.

Certain sensitive integration credentials, including connected-mailbox authorization credentials, are stored in encrypted form by LeadForge.

No security system can guarantee complete protection. Users are responsible for protecting their own credentials, devices, connected accounts, and authorized access. Additional information is provided in the Security & Data Protection Policy.

Depending on your location, relationship with LeadForge, and the nature of the information involved, applicable law may provide rights to request access to, correction of, deletion of, or a copy of certain personal information, or to object to or restrict certain processing.

Some requests may need to be directed to the LeadForge customer or Workspace that controls the relevant information. LeadForge may act as a service provider or processor for customer-controlled data and may assist the applicable customer with a valid request where required.

LeadForge may verify the identity and authority of a requester before completing a privacy request. A request may also be limited or denied where an applicable legal exception permits or requires continued processing or retention.

Privacy requests may be submitted through LeadForge Support or another privacy-contact method made available in the Legal & Trust Center.

LeadForge and its service providers may process information in the United States and in other jurisdictions where applicable providers operate.

Where applicable law requires contractual, transfer, or other safeguards for international processing, LeadForge addresses those requirements through applicable provider agreements, Data Processing Agreements, enterprise agreements, or other legally recognized mechanisms as appropriate.

LeadForge is not intended for individuals under 18 years of age. LeadForge does not knowingly offer the Service to children or knowingly collect personal information from children for use of the Service.

If LeadForge learns that personal information was provided by a child in connection with use of the Service, LeadForge may take appropriate steps to remove or restrict that information.

LeadForge may update this Privacy Policy as the Service, provider relationships, data practices, or legal requirements change. The current version and last-updated date will be published in the Legal & Trust Center.

If a change materially affects how LeadForge handles personal information, LeadForge may provide additional notice where required by law or reasonably appropriate.