Security & Data Protection Policy

LeadForge maintains administrative, technical, and operational safeguards designed to protect the confidentiality, integrity, and availability of the Service and the information processed through it.

Security controls are selected according to the nature of the platform, the data involved, the available infrastructure, and the risks LeadForge is reasonably able to identify and mitigate.

No internet-connected service can guarantee absolute security. LeadForge therefore uses layered controls, monitoring, restricted access, and incident-response practices rather than representing that security incidents are impossible.

LeadForge operates on managed cloud infrastructure and relies on established service providers for application hosting, database infrastructure, identity, payments, AI processing, video, and other platform functions.

LeadForge configures and operates the application layer, while infrastructure providers remain responsible for portions of the physical, network, platform, and service-layer security within their respective environments.

Material providers used by the current production architecture are described in the Subprocessors & Service Providers document.

LeadForge uses an external identity provider for authentication and authenticated session management.

Application routes and server-side operations are expected to validate authenticated identity and applicable Workspace or Personal authorization before returning protected records or performing protected actions.

Users are responsible for protecting their credentials, devices, and authenticated sessions and should promptly report suspected compromise.

LeadForge applies server-side authorization and data-scope controls to separate Personal and Workspace records and to enforce role, membership, ownership, and Workspace-access rules.

Workspace owners and administrators may have broader management authority than members, but administrative authority does not automatically override every object-level, privacy, consent, or ownership rule.

LeadForge designs AI-assisted features, collaboration features, imports, lead workflows, and generated artifacts to consume only information available to the relevant user and scope.

LeadForge uses HTTPS and encrypted network connections for normal browser-to-service communication and secured connections to supported providers.

Sensitive provider credentials and application secrets are intended to remain server-side rather than being exposed in ordinary client application code.

Where LeadForge stores connected-mailbox authorization credentials, the current product architecture encrypts those credentials before persistence.

Infrastructure providers may also provide encryption, storage protection, key management, or transport security within their managed services.

LeadForge uses Stripe for payment and subscription processing and does not use the LeadForge application database as a repository for full payment-card numbers.

Stripe processes payment credentials and returns the subscription, transaction, customer, and billing state needed for LeadForge to administer paid service.

Customers remain responsible for protecting access to billing accounts and for reporting unauthorized payment activity.

LeadForge integrates with external services such as Google and Microsoft mail services, Google Places, Stream video, AI providers, and web-push delivery infrastructure.

LeadForge limits requested access according to the supported integration. The current connected-mailbox integrations are designed for identity and sending functions and are not designed to read mailbox contents.

Third-party service availability, security, and provider-side controls remain partly outside LeadForge's direct control.

LeadForge may use request validation, authorization checks, usage controls, rate limits, idempotency protections, deduplication, transactional checks, and feature-specific safeguards to reduce unauthorized actions, duplicate operations, and abuse.

Provider credentials and privileged operations should be performed server-side where appropriate.

LeadForge may restrict suspicious or anomalous requests when reasonably necessary to protect the Service, customers, providers, or platform integrity.

LeadForge records operational, security, billing, usage, entitlement, diagnostic, and error information needed to operate and protect the Service.

Monitoring may be used to investigate unusual authentication activity, authorization failures, abuse, provider failures, billing inconsistencies, application errors, meeting-capture failures, campaign delivery issues, and other operational events.

Logs and diagnostics are retained according to operational need, security requirements, applicable law, and the Data Retention & Deletion Policy.

Team Video Chat uses third-party live-video infrastructure while Meeting Intelligence capture, transcription, and artifact processing follow LeadForge-controlled application workflows.

Temporary raw Meeting Intelligence capture media is treated differently from retained transcripts, artifacts, provenance, and memory records, as described in the Data Retention & Deletion Policy.

Email Campaigns, Team Threads, direct messages, and connected services are subject to authorization, provider, and product controls appropriate to those features.

LeadForge investigates suspected security incidents and may take steps such as restricting access, disabling credentials or integrations, preserving evidence, correcting software, rotating secrets, limiting affected functionality, or coordinating with providers.

If an incident creates a legally required notification obligation, LeadForge will provide notice in accordance with applicable law and any controlling contractual obligations.

Customers may be asked to cooperate with reasonable investigation, containment, credential rotation, or remediation steps where their account, Workspace, device, or connected service is involved.

Users who identify a suspected vulnerability or security issue should report it through LeadForge Support or the contact method made available in the Legal & Trust Center and should avoid exploiting, publicly disclosing, or accessing data beyond what is reasonably necessary to demonstrate the issue.

LeadForge may request reproduction details, affected routes or features, timestamps, logs, or other information reasonably necessary to investigate a report.

Customers are responsible for managing Workspace membership, roles, devices, passwords, connected accounts, mailbox authorization, user offboarding, and the lawful configuration of their own workflows.

Customers should grant only the access their users require, remove users and connected services that are no longer authorized, and promptly report suspected compromise or misuse.

LeadForge security controls do not eliminate risks created by customer credential sharing, insecure devices, unauthorized exports, malicious insiders, or misuse of legitimately granted permissions.

LeadForge may modify security controls, providers, architecture, monitoring, authentication, or operational practices as the Service evolves.

Material changes affecting contractual data-protection commitments may also be reflected in the Privacy Policy, Data Processing Agreement, Subprocessors & Service Providers document, or applicable enterprise agreement.