Privacy Policy

Leadwise is a business-to-business CRM. For Customer-submitted CRM records, the Customer normally determines why information is processed and who may access it. Leadwise processes that information to provide the service under Customer instructions.

Leadwise separately determines processing for accounts, authentication, security, billing, support, legal acceptance, AI metering, and service operations.

• Account and identity information, including name, business email, provider profile, workspace, role, permissions, authentication, session, and legal acceptance.
• CRM and workspace information, including leads, accounts, contacts, deals, tasks, notes, activities, timelines, custom fields, imports, and company knowledge.
• Where authorized and available, communication and meeting context, including metadata, permitted excerpts, drafts, participants, links, timestamps, notes, and CRM relationships.
• AI information, including prompts, selected context, outputs, models, providers, tokens, request counts, estimated costs, approvals, and actions.
• Connector information, including identity, permissions, tool calls, User, workspace, timestamps, results, errors, and revocation.
• Technical and commercial information, including IP address, bounded user agent, session events, security and audit logs, plan, seats, payment references, support, grievances, export, and deletion requests.

We use information to authenticate Users; provide CRM, built-in AI, connectors, imports, exports, reports, billing, security, audit, support, reliability, legal compliance, and rights handling. We do not sell personal data.

Customers are responsible for establishing an appropriate lawful basis and providing required notices. Every User is responsible for authorization to access, submit, disclose, or instruct Leadwise to process organizational or third-party information.

Leadwise selects and configures third-party providers used for built-in AI. Selected CRM information, company knowledge, and instructions may be transmitted when required for a requested feature.

Provider practices vary. Inputs and outputs may be retained, reviewed, evaluated, used to improve services, fine-tuned upon, or used for training depending on provider, model, routing, configuration, and contract. Leadwise does not guarantee that every request uses zero retention or no training.

Provider information and known settings may be requested at hello@synapseloop.in. Users should avoid unnecessary confidential, regulated, highly sensitive, or special-category information in AI instructions.

A Customer-selected client may receive information permitted by the authenticated User’s role and granted permissions. It processes information under its own terms, privacy policy, settings, and model policies. Leadwise does not control its independent retention, training, security, or use.

An authorized client may submit bounded email metadata, excerpts, generated summaries, source provenance, identifiers, participants, timestamps, links, and CRM matching context through external-email import. Accepted information is stored in the applicable workspace and may appear in review or shared CRM timelines under authorization, matching, and visibility rules.

The Customer directs the import and is responsible for authority to obtain and submit it. Leadwise processes accepted information as Customer Data and remains responsible for security and access controls of the storage it operates.

Native Gmail and Google Calendar integrations are currently disabled. Leadwise does not collect new Gmail or Calendar information through those disabled native integrations. External-email import may store bounded Customer-supplied information without authenticating to or fetching Gmail.

Previously connected or imported communication, meeting, token, cache, note, and audit information may remain quarantined or retained. No production Calendar-import MCP capability is currently offered. Any new connector or native integration must be disclosed before processing begins.

If Google access is enabled later, Leadwise will request only permissions required for the disclosed function. Google-derived information will not knowingly be used or transferred for advertising, surveillance, unrelated purposes, or unrestricted general-purpose model training contrary to Google policy.

Leadwise’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google API Services User Data Policy

Under current safety rules, raw transcripts are excluded from AI prompts, generated insights, AI Queue content, Daily Agenda, search, exports, and draft-email content. Protected source records may be retained where the relevant feature and authorization permit it.

Information may be disclosed to infrastructure, hosting, identity, communication, and AI providers; Customer-authorized services; authorized workspace Users; professional advisers; authorities where required; security and fraud recipients; or a business successor subject to safeguards.

Leadwise and its providers may process information outside the User’s location. Appropriate safeguards will be used where required. Leadwise does not promise India-only storage unless separately confirmed in writing.

Information is retained only as long as reasonably necessary to provide the workspace, permit applicable read and export access, meet contractual obligations, maintain security and audit evidence, administer billing, resolve disputes, and comply with law.

Removing a User or disconnecting a service does not automatically erase shared CRM history, imports, audit records, or protected backups. Deleted information may remain temporarily in backups until their cycle completes.

We use reasonable administrative, technical, and organizational safeguards, including authentication, role-based authorization, workspace isolation, restricted permissions, audit logging, protected credentials, and encrypted network transport where applicable. No measure eliminates every risk.

Subject to applicable law and the Customer’s role, a person may request processing information, access, correction, completion, erasure, applicable consent withdrawal, grievance redressal, or other available rights. Customer-controlled CRM requests may be referred to the Customer. Identity and authority may be verified.

Authorized Users may export supported information according to role and status. Workspace deletion is not self-service and requires a verified request from an authorized workspace owner. Limited security, billing, legal-acceptance, audit, and backup records may be retained where reasonably necessary or legally required.

Leadwise uses cookies or similar browser storage necessary for authentication, session continuity, request protection, essential preferences, security, and reliability. Optional advertising or marketing cookies would require separate disclosure if introduced.

Leadwise is intended for business Users aged 18 or older and is not directed to children.

We may update this policy for changes in law, providers, security, or product behavior. A material change may require workspace-level and individual renewed acceptance.

General questions, privacy requests, grievances, security reports, and legal notices may be sent to hello@synapseloop.in. We will verify requests and respond within the period required by applicable law. Formal operator information will be provided where applicable law requires it.

Contact SynapseLoop