Data Retention & Deletion Policy

LeadForge retains information for the period reasonably necessary to provide the Service, preserve customer-created workflows and records, maintain continuity, secure and troubleshoot the platform, administer billing and entitlements, comply with law, and resolve disputes.

Retention is not identical for every category of information. Operational records may be intentionally persistent, while temporary processing data may be designed for rapid deletion after its purpose is complete.

A product freshness period, cache period, or refresh threshold is not automatically a deletion deadline.

LeadForge retains Personal and Workspace records according to the scope, ownership, and lifecycle of the underlying object.

Removing a user's Workspace access does not automatically delete Workspace records, and Workspace membership does not automatically transfer ownership of Personal records.

Where Personal and Workspace versions of similar artifacts coexist, each version may have an independent retention lifecycle.

Account, profile, preference, authentication-reference, and membership information is retained while needed to maintain the user's account and authorized access to the Service.

After account closure or loss of access, LeadForge may retain limited records where reasonably necessary for security, fraud prevention, billing, tax, contractual enforcement, legal claims, audit, or other lawful obligations.

Authentication information managed directly by an identity provider may also be subject to that provider's retention practices.

LeadForge stores operational records such as leads, territories, Vault state, activity, tasks, generated work, settings, shared artifacts, meeting records, collaboration, and related Workspace information so that customer workflows can persist.

Deleting a visible card, activity, or user-facing object does not necessarily delete every underlying source record, audit record, usage event, message, provider record, or independently retained artifact associated with it.

Where LeadForge provides a specific delete, close, remove, or revoke control, that control applies to the object or access relationship identified by the product unless the interface expressly states that broader deletion will occur.

Discovery results and related business information may be cached and persisted to support territory continuity, deduplication, LeadForge-known business results, and subsequent workflows.

The current Discovery cache freshness period is 120 days. That period determines when LeadForge may refresh or re-query discovery information; it is not a promise that all associated business or territory records are automatically deleted after 120 days.

Business records that become part of a lead, territory, Workspace, or other persistent workflow may remain beyond the discovery freshness period.

Completed Lead Intelligence research currently uses a 120-day freshness period for determining when the researched artifact should be considered current enough for reuse or due for refresh.

The 120-day Lead Intelligence freshness period is not an automatic deletion schedule. A completed intelligence artifact may remain available after it becomes stale so LeadForge can preserve history, provenance, generated work, and downstream workflows.

A refreshed Lead Intelligence artifact may supersede or update current context without requiring every historical record or derived artifact to be physically deleted.

LeadForge retains original import headers and source rows as the source of truth for import mapping, validation, remapping, migration reporting, skip reasons, reconciliation, and auditability.

Imported source data is stored separately from normalized LeadForge lead fields created from that source. Editing or deleting a resulting lead does not by itself mean that the original import batch or retained source payload has been deleted.

Customers are responsible for ensuring that imported business or contact information may lawfully be provided to LeadForge.

LeadForge may retain Copilot conversations, Business Partner task inputs and results, AI-assisted Support conversations, prompts, outputs, and related context needed to preserve product continuity.

LeadForge may derive structured Personal or Workspace memory from supported product activity. A memory record may be retained separately from the conversation, meeting, artifact, or other source from which it was derived.

A memory item becoming stale, being excluded from active AI context, or no longer appearing in a particular interface does not necessarily mean that its underlying source record has been physically deleted.

Generated artifacts may include Pitch Decks, Task Results, Lead Intelligence, Meeting Intelligence artifacts, summaries, and other AI-assisted work product.

Deleting one generated artifact does not automatically delete the independent source records, usage records, provenance, or other artifacts created from the same underlying information.

Where Personal and Workspace representations of generated work are maintained separately, deleting or editing one representation does not necessarily change the other.

Meeting Intelligence distinguishes temporary raw capture media from retained transcript-derived records.

After a capture is successfully processed, the current default retention period for completed raw capture chunks is zero hours, and the capture pipeline is designed to remove those completed raw chunks after processing.

For failed, canceled, or abandoned capture attempts, the current default cleanup period is up to 24 hours so supported recovery or finalization can occur before temporary media is removed.

These temporary-media periods do not apply to retained transcripts, transcript segments, artifacts, provenance, consent records, or approved memory.

Meeting transcripts, transcript segments, generated artifacts, provenance, consent state, and approved meeting-derived memory may persist after temporary raw audio has been deleted.

These records support review, collaboration, Workspace history, troubleshooting, and permitted AI context.

Deleting or closing a meeting surface does not necessarily delete every transcript-derived record unless the applicable product control expressly provides that result.

LeadForge retains information needed to operate Email Campaigns, including campaign configuration, recipient and delivery state, suppression and unsubscribe records, connected-mailbox identity, granted scopes, and encrypted authorization credentials required to maintain an active connection.

Suppression and unsubscribe records may be retained after a campaign ends or a mailbox is removed because retaining those records may be necessary to honor opt-outs and avoid future unwanted sending.

Removing a connected mailbox ends LeadForge's use of that connection according to the product flow, but historical campaign, delivery, compliance, billing, or audit records may remain where needed.

Team Threads, direct messages, group conversations, shared-work references, and related collaboration records may be retained to preserve participant history and Workspace continuity.

Closing a direct-message view for one participant does not necessarily delete the conversation retained for another participant.

Leaving a Workspace or losing Workspace access does not automatically delete messages, shared-work references, or records that belong to the Workspace or remain available to other authorized participants.

LeadForge may retain Support conversations, diagnostic evidence, error information, request identifiers, logs, and other technical records needed to investigate product behavior, security issues, billing disputes, or customer reports.

Diagnostic information may be minimized, rotated, or deleted when it is no longer reasonably necessary for reliability, security, support, or legal purposes.

LeadForge retains billing, subscription, usage, entitlement, seat, capacity, transaction, and related operational records for as long as reasonably necessary to administer the Service, reconcile access, investigate disputes, enforce plan rules, and satisfy accounting, tax, contractual, or legal obligations.

These records may be retained for a different period than ordinary product content because they support financial and system-integrity requirements.

Security, abuse-prevention, authorization, incident, and audit records may be retained for the period reasonably necessary to investigate events, protect the Service, prevent repeated abuse, establish or defend legal claims, and satisfy applicable obligations.

LeadForge may preserve relevant records for longer when they are subject to a legal hold, active investigation, dispute, or security incident.

LeadForge's demo environment may include synthetic Workspace content together with limited real lead or import records associated with the user.

Synthetic demo-only records may be removed when the user leaves or migrates from the demo according to the product's demo lifecycle.

Where the product expressly preserves real user-owned leads, imports, or related real artifacts during upgrade into a production Workspace, those retained real records may continue under the ordinary production retention rules.

Deletion from the active application does not always result in instantaneous removal from every backup, cache, log, provider-managed recovery system, or distributed copy.

Residual copies may remain for a limited period until the relevant system is overwritten, rotated, or otherwise expires them.

LeadForge does not use residual backup copies as ordinary active customer data after deletion except where restoration, security, legal preservation, or disaster-recovery needs require temporary access.

Where applicable law provides a deletion right, an eligible request may be submitted through LeadForge Support or the contact method made available in the Legal & Trust Center.

LeadForge may need to verify the requester, determine whether the request concerns Personal or Workspace data, and confirm the requester's authority over the relevant records before acting.

LeadForge does not represent that every account, Workspace, or underlying record can be instantly or automatically deleted through a single product control.

A deletion request may be limited where retention is required or permitted for legal obligations, security, fraud prevention, billing and tax records, contractual rights, establishment or defense of legal claims, recordkeeping, suppression of future communications, or other lawful exceptions.

LeadForge may preserve information subject to a valid legal hold, investigation, security event, or dispute until the preservation requirement ends.

Where an executed enterprise agreement or Data Processing Addendum establishes a more specific return, deletion, retention, or backup obligation for covered Customer Data, that agreement controls for the covered data.

Customer-specific deletion commitments do not automatically apply to records outside the scope of the executed agreement.

LeadForge may update retention practices as the platform, architecture, providers, features, and legal obligations evolve.

A material change to a freshness window, temporary-processing period, backup lifecycle, or deletion process may require this policy to be updated so that the published description remains accurate.