Sub-Processors
Last updated: October 31, 2026
These are the service providers that process personal information on behalf of Liaison Intelligence, LLC to deliver the Service. Each one receives personal information under a written agreement with us that requires it to give that information the same or equal protection as our Privacy Policy, and uses it only for the purpose shown, as described in Section 8 of our Privacy Policy. What AI providers may receive, and how to withdraw your consent, is in Section 16 of the Privacy Policy and our Data Sharing Policy. AI model providers are not permitted to use your content to train their models; where a provider's own terms say more or less than that, the table says so. All data is encrypted in transit with TLS 1.2 or higher.
| Provider | What it does for the Service | Data it may process |
|---|---|---|
| Amazon Web Services | Application hosting, file and media storage, encryption-key management, and content delivery for the app; Amazon Comprehend to detect sensitive personal information in content so it can be protected | Service data, including files you upload and meeting media |
| Supabase | Database, authentication, and storage | Service data |
| vast.ai marketplace hosts | Rented GPU servers on which Liaison runs its own speech-to-text software to transcribe Liaison meeting recordings; the host of each server has physical control of it | Meeting audio and the transcripts produced from it |
| Calendly | The booking calendar on our website, for calls with the Liaison team | Name, email, booking details and answers; the ad click identifier only as the visitor’s cookie choices allow |
| Vercel | Hosting of useliaison.com, its forms, and the site chat | Website visitor data and form submissions |
| Stripe | Subscription billing and payments | Name, email, billing details; card details entered on Stripe’s own forms |
| Apple | Payments for plans bought in the Liaison iOS app, and push notification delivery to the Liaison app on iOS (Apple Push Notification service) | Purchase and subscription records; device push token and notification contents |
| Resend | Email delivery, transactional and marketing | Email addresses and the emails we send |
| Twilio | SMS delivery and phone-number verification | Phone numbers and SMS contents |
| Linq | iMessage delivery and receipt, where the iMessage option is offered | Phone numbers or Apple ID email addresses, message contents, and attachments |
| Anthropic | AI model provider | Content processed to produce answers, drafts, and insights; not used to train their models |
| OpenAI | AI model provider | Content processed to produce answers, drafts, and insights; not used to train their models |
| xAI | AI model provider, and the voice on live voice calls | Content processed to produce answers, drafts, and insights; on a live voice call, the audio of the conversation; not used to train their models |
| Venice AI | AI model provider, including speech-to-text and analysis for meeting recordings | Content processed to produce transcripts, answers, and insights; Venice states that prompts are not stored |
| OpenRouter | AI model routing: passes requests to the AI model that answers them, including open-weight models such as DeepSeek | Content processed to produce answers, drafts, and insights |
| ElevenLabs | Speech and voice: turning speech into text and creating spoken replies | Spoken audio from voice features and meeting recordings, and the text of Liaison’s spoken replies |
| Recall.ai | The meeting bot that joins video calls and captures the recording when a workspace turns the Notetaker on | Meeting audio and video, participant names, and meeting chat, deleted after transcription |
| Google Firebase Cloud Messaging | Push notification delivery to the Liaison app on Android | Device push token and notification contents |
| Apify | Where the feature is offered, retrieves public Reddit and X posts for research a user asks Liaison to do | Search terms, and the public posts it returns |
| Imgflip | Renders memes a user makes in Create | Caption text and the chosen template |
| Google Analytics | Website analytics on useliaison.com (one Google Analytics property), only as the visitor’s cookie choices allow | Usage and device data on the website |
| Google Ads | Measuring which of Liaison’s own ads led to a booked call, a trial, a free-report request or a subscription | Ad click identifiers, conversion names, times and values; no names or email addresses |
What is not on this list
The tools you connect to Liaison, such as your email, calendar, CRM, accounting, payments, field-operations, and meeting services, are not sub-processors. They are the systems you authorize Liaison to read from and act in, and your agreements with them govern how they handle your data. The commercial data providers we obtain prospect information from are described in Section 7 of the Privacy Policy. Some AI work, such as sorting incoming workspace events, runs on a Liaison-operated server in the United States; that server is part of the Service, not a sub-processor.
Channels you choose to use. If you use Liaison on Telegram or WhatsApp, or connect your own Telegram or WhatsApp account, Telegram and Meta (WhatsApp) carry the messages you exchange there under their own terms. They are used only if you choose them.
We update this page when a provider is added or replaced. Questions go to support@useliaison.com.