Trust Center
Subprocessors
See which service providers may process customer data for Lithi, what each one does, and how to review changes under your agreement.
On this page
Lithi may engage specialized service providers to deliver hosting, messaging, billing, connected services, and other requested features. This page summarizes their roles and data categories; your DPA and agreement govern authorization, change, review, and objection terms.
What subprocessors do
Subprocessors help Lithi deliver a specific service. They may handle only the information needed for that service, such as account details, approved work content, connected records, messages, billing details, or service logs.
The table groups each provider by its service role and the data categories that role may involve. A provider listed here does not mean that your workspace uses that provider.
Current providers
| Provider | What it does | Data categories that may be involved |
|---|---|---|
| Supabase | Database, authentication, file storage, and realtime service. | Account data, authentication details, files, and service logs. |
| Vercel | Web hosting, edge delivery, and serverless functions. | Request logs and deployment artifacts. |
| Anthropic | AI model inference for approved work. | Prompts, instructions, and approved inference context. |
| Stripe | Inbound payment processing for subscription products; plan-specific availability is unverified. | Payment metadata and provider-held card tokens. |
| Twilio | SMS delivery and phone verification. | Phone numbers, message content, and delivery logs. |
| Unipile | Connected LinkedIn and email messaging services. | Message threads, email data, and calendar events. |
| Merge.dev | Connected CRM, HRIS, accounting, and ticketing services. | Connected records and integration data. |
| Mercury | Lithi Compute customer invoices on USD NET30 terms and Connector commission payouts. | Customer and organization identifiers, billing contacts, invoice references, billing periods, currency, amounts, due dates, payment status, bank routing details for approved ACH, and payout recipient information. |
| Fly.io | Background workers for queued service tasks. | Job payloads and execution logs. |
| Mailgun | Outbound email delivery. | Email content, recipient addresses, and delivery logs. |
| Google Workspace | Transactional email for billing, alerts, and verification. | Email content, recipient addresses, and delivery logs. |
| Mapbox | Location search, territory mapping, and address entry. | Location queries and transient network location data. |
Review changes
If Lithi adds a provider or replaces one, review this page alongside the DPA and your applicable agreement. Those documents govern authorization, notice, review, objection, and effective-date terms.
This page does not set a separate notice period or change your agreement. Ask about your account when a provider, service, or data category matters to your decision.
Ask about your setup
To ask whether a provider applies to your workspace, or to discuss a data category, email trust@lithi.ai. Include your organization, service, and question. Do not send passwords, access codes, payment details, or private customer content.
For broader context, see privacy and Compute security.
Primary action
Review the DPA for the contractual authorization, change, and objection terms that apply to your account.