Service Availability Policy

LeadForge is designed to provide reliable access to its core application and supported workflows, but no online service can guarantee uninterrupted or error-free operation.

Availability may be affected by software deployments, maintenance, infrastructure incidents, provider outages, security events, network failures, capacity constraints, or circumstances outside LeadForge's reasonable control.

This general policy does not create a contractual uptime percentage unless a specific Service Level Agreement or signed order form expressly provides one.

A platform incident may affect the entire Service or only a particular feature, provider integration, region, workflow, or customer.

LeadForge may keep unaffected portions of the platform available while temporarily restricting a degraded feature, connected service, AI workflow, campaign action, meeting function, or other component.

A feature being temporarily unavailable does not necessarily mean that stored customer records are unavailable or lost.

LeadForge may perform scheduled maintenance, infrastructure upgrades, database work, security changes, model or provider migrations, and product deployments that temporarily affect availability.

Where practical, LeadForge may schedule higher-impact maintenance to reduce disruption and may provide advance notice when the expected impact is material.

Emergency maintenance may be performed without advance notice where necessary to address security, data-integrity, provider, or reliability risks.

LeadForge depends on third-party providers for hosting, database infrastructure, identity, payments, AI processing, video, business discovery, connected mailboxes, and other platform functions.

An outage, rate limit, policy change, network problem, degraded response, or service restriction at a provider may affect the corresponding LeadForge feature even when the rest of LeadForge remains operational.

LeadForge may reroute, retry, queue, disable, degrade, or substitute supported provider-dependent functionality where reasonably practical.

AI-assisted features may experience latency, queueing, model unavailability, provider errors, or partial completion independent of ordinary page availability.

Meeting transcription, Lead Intelligence, Business Partner Tasks, Pitch Deck generation, Copilot Discovery, Support AI, and similar workflows may therefore complete later than an ordinary application request.

LeadForge may retry or resume supported jobs where the product architecture permits it.

Discovery results depend in part on external business-data providers, source availability, rate limits, geographic coverage, and matching systems.

A provider outage or sparse source coverage may reduce the number, freshness, or completeness of results without constituting a complete LeadForge outage.

LeadForge may return cached or previously indexed business information when the applicable product rules permit it.

Email Campaign sending depends on the connected Google or Microsoft account, provider authorization, provider availability, mailbox status, sending limits, and recipient-side delivery systems.

LeadForge may pause or reject sending when authorization expires, the connected provider refuses a request, suppression rules apply, or continued sending could create abuse, deliverability, or compliance risk.

A successful submission to a connected provider does not guarantee final inbox delivery.

Team Video Chat and Meeting Intelligence depend on live video infrastructure, user devices, browsers, network quality, capture state, and downstream transcription or AI processing.

LeadForge may be unable to recover audio that was never successfully captured or transmitted. Temporary capture failures may be retried or finalized according to the Meeting Intelligence lifecycle supported by the product.

Retained transcripts and generated artifacts are distinct from temporary raw capture media and may remain available after a meeting ends.

LeadForge may impose temporary rate limits, queueing, reduced concurrency, provider fallbacks, feature restrictions, or other protective controls to maintain stability and reduce the impact of unusual demand or provider degradation.

LeadForge may also temporarily restrict functionality during a security event, billing integrity issue, abuse investigation, or other incident where unrestricted operation could increase harm.

LeadForge investigates significant service incidents and may use logs, diagnostics, provider evidence, usage records, and application state to identify the affected systems and restore service.

Recovery priorities may include protecting data integrity, containing security risk, restoring core access, restoring customer-facing workflows, and reconciling failed or partially completed jobs.

Where an error incorrectly consumes paid usage or creates a billing inconsistency, correction is handled under the Billing & Usage Policy and Refund Policy.

LeadForge uses managed infrastructure and application controls intended to preserve persisted product data through ordinary service interruptions.

Temporary unavailability does not by itself mean that customer data has been deleted. Retention, deletion, backups, and temporary-processing data are addressed in the Data Retention & Deletion Policy.

No backup or recovery process can guarantee recovery from every conceivable failure.

LeadForge is not responsible for failures caused solely by a customer's internet connection, unsupported device or browser, local network, disabled permissions, expired provider authorization, customer-controlled domain or mailbox configuration, or other systems outside LeadForge's control.

Customers are responsible for maintaining supported access, current authorization to connected services, and reasonable local security and network conditions.

This policy is informational and does not independently create service-credit rights.

If a customer has an executed Service Level Agreement or enterprise contract with specific availability commitments, exclusions, response targets, or remedies, that agreement controls for the covered services.

Any service-credit request is evaluated under the procedure and measurement rules in the applicable SLA.

LeadForge may update reliability practices, providers, maintenance procedures, recovery processes, or feature dependencies as the Service evolves. The current version will be published in the Legal & Trust Center.