Last updated: July 22, 2026
Subprocessors
This page lists the third-party service providers ("subprocessors") that WYRE AI, LLC uses to operate Conduit and that may process customer data in doing so. It supplements our Privacy Policy.
1. Infrastructure and Operations Subprocessors
These providers are engaged by WYRE and may process customer data as part of running the service:
Microsoft Azure — Microsoft Corporation
United States (East US 2)
Purpose: Cloud hosting — application runtime (Container Apps), database (Azure Database for PostgreSQL), secrets management (Key Vault), infrastructure logs (Log Analytics).
Data processed: All service data, including account information, encrypted vendor credentials, and audit/request logs.
Cloudflare — Cloudflare, Inc.
Global edge network
Purpose: Edge network / DNS for the public service domain.
Data processed: Traffic to the public domain in transit (TLS-terminated at the edge).
Auth0 — Okta, Inc.
United States
Purpose: User authentication and identity management.
Data processed: Email address, display name, authentication metadata.
Microsoft Entra ID — Microsoft Corporation
United States / Microsoft global cloud
Purpose: User authentication for organizations signing in with Microsoft.
Data processed: Email address, display name, tenant identifier.
Stripe — Stripe, Inc.
United States
Purpose: Payment processing and subscription billing.
Data processed: Billing contact name and email, payment method details, subscription state.
Resend — Resend, Inc.
United States
Purpose: Transactional email delivery (invitations, security notices, billing notices).
Data processed: Recipient email address and name, message content.
Microsoft 365 / Microsoft Graph — Microsoft Corporation
United States / Microsoft global cloud
Purpose: Email delivery for onboarding messages sent from WYRE mailboxes.
Data processed: Recipient email address, message content.
Loops — Funnel Envy Inc. d/b/a Loops
United States
Purpose: Product lifecycle and marketing email.
Data processed: Contact email address, name, product usage events.
PostHog — PostHog, Inc.
United States (US Cloud)
Purpose: First-party product analytics — understanding feature usage and onboarding to improve the service. Configured cookieless (no cookies or persistent on-device storage).
Data processed: Product usage events; for signed-in users, associated with account email and organization identifier. No advertising or cross-site tracking.
HubSpot — HubSpot, Inc.
United States
Purpose: In-dashboard support chat widget and support inbox; CRM record-keeping for your organization and its contacts, including account-usage signals and sales follow-up on new signups.
Data processed: Name, email address, and support conversation content from the chat widget. Separately, when your organization is created, renamed, or changes plan, we create or update a corresponding Company and Contact record in HubSpot — organization name, plan tier, your internal organization identifier, and the account owner's name and email; this happens automatically at signup, not only if you use the chat widget. We also sync account-usage signals to that Company record on an ongoing basis: which vendors your organization has connected, your tool-call volume over the trailing 30 days, when your organization was last active, and a derived engagement stage and health score computed from those signals — so our team can see how organizations are using Conduit and follow up if something looks off. When someone starts creating a Conduit account, we may also create a follow-up task in HubSpot assigned to a WYRE sales team member, containing the prospective organization's name, the contact's email address, and how they found us.
Slack — Slack Technologies (Salesforce, Inc.)
United States
Purpose: Internal operational notifications to WYRE staff (e.g. new-signup alerts).
Data processed: Organization name and signup contact details contained in notifications.
Operational monitoring services (e.g. Rootly for infrastructure alerting) receive only infrastructure alert metadata and do not process customer content.
Browser-loaded services: sign-in and dashboard pages load web fonts from Google Fonts (Google LLC). Your browser's IP address is disclosed to Google when those fonts are fetched. No customer content or account data is sent to Google.
2. Customer-Directed Connections (Not WYRE Subprocessors)
The core function of Conduit is to proxy requests, at your direction, to third-party vendor tools that you connect using your own accounts and credentials (for example PSA, RMM, documentation, and security platforms, or vendor-hosted MCP endpoints). When you connect a vendor:
- Your credentials for that vendor are stored encrypted and used solely to proxy your requests to that vendor.
- Data flows between your AI assistant and that vendor at your instruction. The vendor processes that data under your agreement with them, not under WYRE's.
- Some integrations are vendor-hosted MCP endpoints operated by the vendor itself; requests to those integrations (including your credentials for them) are transmitted directly to the vendor's own infrastructure.
Similarly, if you configure audit-log streaming to an external logging platform, the destination you configure is your processor, not ours. The list of connectable vendors is available in the product's vendor catalog.
3. Changes to This List
We will update this page when we add or replace a subprocessor and will notify account contacts before a new subprocessor begins processing customer data, consistent with the notice provisions of our Privacy Policy and Terms of Service.
To receive these notices proactively, subscribe to updates at our trust center — subprocessor changes are published there alongside our monitored controls.
4. Contact
Questions about this list: privacy@wyretechnology.com