Conduit is a business-to-business (B2B) lead intake and qualification infrastructure platform. It provides a configurable engine for ingesting leads from multiple sources, scoring them using the LSQA model, automating WhatsApp outreach, and running an AI-powered qualification agent.
These Terms of Service ("Terms") govern the relationship between Conduit ("we", "us") and the businesses ("Clients") that deploy and operate instances of the Conduit engine. These Terms are not addressed to end consumers or leads — individuals whose data is processed have rights described in the Privacy Policy.
Conduit is an infrastructure tool sold and deployed exclusively to businesses. Each client deployment operates under a separate configuration and is the independent data fiduciary for all personal data processed through their instance. Conduit does not directly interact with end consumers.
Conduit operates as a per-client deployment, not a multi-tenant SaaS. Each client receives:
client_config.yaml file governing all engine behaviour for that deploymentClient data is never co-mingled across deployments. The client owns and controls their hosting environment, database, and API credentials at all times.
By deploying and operating Conduit, each client agrees to the following obligations:
| Area | Obligation |
|---|---|
| Consent | Obtain explicit, informed consent from all leads before their personal data enters the system. All lead capture forms must include a clear WhatsApp opt-in statement. CSV imports must only contain leads who have provided prior consent. |
| DPDP Act 2023 | Comply with the India Digital Personal Data Protection Act 2023 as the data fiduciary. Respond to data principal requests (access, correction, erasure) within mandated timeframes. Maintain a valid consent record for each lead. |
| WhatsApp Policy | Comply with Meta's WhatsApp Business Messaging Policy at all times. Only message leads who have opted in to WhatsApp communications. Never send messages after a lead has sent a STOP request. Register and obtain approval for all business-initiated message templates before go-live. |
| Template Approval | Submit all six required WhatsApp message templates for Meta/Twilio approval during onboarding. Do not go live until all templates are approved. Template approval takes 24–48 hours and must be completed before the production environment is enabled. |
| Data Retention | Configure a data retention period appropriate for your jurisdiction. The default is 365 days. Delete or anonymise lead records that exceed the retention period. |
| Third-Party DPAs | Sign Data Processing Addendums with Supabase and Twilio before processing live lead data. For deployments processing EU personal data, obtain a DPA from Anthropic. Confirm Supabase project region is Singapore or Mumbai for India data localisation. |
| Credential Security | Protect all API credentials stored in the .env file. Never commit secrets to version control. Rotate credentials immediately if a breach is suspected. |
| AI Disclosure | The system's AI qualification agent is configured to disclose its AI nature when directly asked. Do not modify the agent's operating instructions to suppress this disclosure. Doing so violates WhatsApp Business API policy and applicable transparency requirements. |
| Opt-Out Compliance | Never attempt to circumvent the opt-out mechanism. When a lead sends STOP (or equivalent), the system archives the lead and cancels all follow-ups. Do not manually reactivate a lead who has opted out to resume outreach. |
| Lawful Use Only | Use Conduit only for lawful lead qualification and outreach. Do not use the system for spam, unsolicited bulk messaging, or any communication that violates applicable law or platform policies. |
All WhatsApp outreach from Conduit is subject to Meta's WhatsApp Business Messaging Policy. The following rules are non-negotiable and enforced at the infrastructure level:
Clients are solely responsible for any violations of the WhatsApp Business Messaging Policy arising from modifications to the Conduit engine, manual database interventions, or configurations that bypass the built-in compliance mechanisms. Conduit infrastructure does not assume liability for client-side policy violations.
The qualification agent uses the Claude AI API (Anthropic, PBC). Clients deploying the AI agent agree to:
The AI agent operates in mode: full deployments only. Clients operating in mode: intake_only do not activate the agent and have no Anthropic API usage.
The Conduit engine codebase, LSQA scoring model, architecture, and associated documentation are the intellectual property of Regnor Infrastructure. Clients are licensed to deploy and operate the engine for their own business purposes under the terms of their agreement.
Client-specific configuration files (client_config.yaml), knowledge base content, and lead data remain the property of the client. Conduit makes no claim to client data or client-authored configurations.
To the maximum extent permitted by applicable law, Conduit infrastructure shall not be liable for:
Conduit's total cumulative liability to any client shall not exceed the fees paid by that client in the three months preceding the event giving rise to the claim.
Conduit is deployed per-client on Railway or Render. Hosting availability is governed by the applicable hosting provider's service level agreement, not by Conduit infrastructure directly. Clients are responsible for monitoring their deployment and for maintaining hosting accounts in good standing.
Third-party service outages (Meta Graph API, Twilio, Anthropic Claude API, Supabase, Gmail API) may affect system functionality. The engine includes retry logic and graceful degradation for known failure modes (e.g. the Meta Graph API dev fallback), but cannot guarantee uninterrupted operation when upstream services are unavailable.
Conduit must not be used for:
Violation of acceptable use terms may result in immediate termination of the client's deployment access.
Conduit infrastructure may update the engine codebase, add or modify features, and update these Terms from time to time. Material changes to the Terms will be communicated to active clients. Continued operation of a Conduit deployment following such changes constitutes acceptance of the revised Terms.
Clients who modify the engine codebase for their own deployment do so at their own risk and are solely responsible for any consequences of those modifications, including compliance failures or data breaches.
These Terms are governed by the laws of India. Any disputes arising from these Terms shall be subject to the exclusive jurisdiction of the courts in India.
For clients processing personal data of EU residents, the terms of the EU General Data Protection Regulation (GDPR) apply in addition to these Terms. Clients processing EU personal data must ensure an appropriate legal transfer mechanism is in place for any data transferred outside the EU.
For questions about these Terms, deployment agreements, or to report a compliance concern, use the contact form at conduit.infrastructure or reach out through your onboarding channel.