Service providers and subprocessors
Which outside providers help run Compute, accounts, email, website chat and measurement, and what data each one handles.
Lithi uses the providers below to run Compute and support its website, accounts and customer communications. Each entry explains the service and the data involved. Provider names link to their processing terms.
Understand which service handles your data
Compute infrastructure vendors handle account and job records, operational metadata and encrypted artifacts. A participating executor is an approved provider Mac that decrypts and reads its authorized piece while doing the work; it is a separate execution role, not another website or infrastructure vendor in this register. Read Compute security for that execution boundary.
Email, website chat and measurement have separate purposes. Google Workspace hosts correspondence with Lithi. Mailgun sends account and service email. Anthropic provides the website assistant. Meta measures website visits, interactions and lead events. These services are not the engine that runs your Compute tasks.
For example, requesting a sign-in code sends your email address and the code through the email service. Asking the website assistant a question sends the chat and relevant context to its provider. Neither action submits a Compute job.
Current providers
| Provider | Purpose | Data involved | Processing location |
|---|---|---|---|
| Supabase | Compute and accounts: Stores account, access, job and service records; provides authentication and storage. | account and authentication records, job metadata, service records and stored files | US East (Northern Virginia) for the primary project |
| Vercel | Website and API: Serves the website and handles web and API requests. | request information, submitted form and API data, operational logs | Global edge network; application regions follow deployment settings |
| Fly.io | Compute and service operations: Runs control services, background work and the gateway to selected service providers. | job references and execution metadata, service request data, operational logs | US East (Northern Virginia) for the primary control and worker services |
| Upstash | Compute and service operations: Maintains the work queue and request-rate counters. | queued job references and metadata, request-rate counters | Hosted database region selected for the service |
| Cloudflare | Compute file storage: Stores encrypted task artifacts for authorized transfer and retrieval. | encrypted artifacts, object metadata and digests | R2 storage locations under the selected bucket configuration |
| Google Workspace | Customer correspondence: Hosts Lithi mailboxes used for support, onboarding, billing and other correspondence. | email addresses, email content and attachments, mailbox records | Google service locations; applicable mailbox settings and terms govern processing |
| Mailgun | Account and service email: Sends verification codes, account notices and other service email. | sender and recipient addresses, email content, delivery and suppression records | US message-processing region; account information may be processed globally |
| Anthropic | Website assistant: Generates Ask Lithi answers from the conversation and supplied website context. | chat messages, selected conversation and page context, generated answers | Processing locations under Anthropic’s commercial service terms |
| Meta | Website measurement: Measures page visits, interactions and submitted lead events through Meta Pixel and the Conversions API. | website events and page URLs, browser and advertising identifiers, network information, hashed contact details for submitted lead events | Processing locations described in Meta’s Business Tools terms |
Processing roles and locations
Providers in this register serve different roles. Infrastructure, account, email, website chat and measurement vendors provide the listed services; participating executors are approved provider Macs governed by the Compute execution policy. Whether a provider acts as a subprocessor for a particular customer activity depends on the applicable Data Processing Agreement and service terms. The linked provider terms and your agreement determine the role for each activity.
The locations above describe the stated service or configuration, not a promise that every request, support interaction or backup stays in one country. For a location requirement, confirm the relevant data category and service terms with us before sending the data. See Privacy for the wider data flow and the Privacy Policy for the governing terms.
Changes and questions
Your agreement and Data Processing Agreement set the applicable provider-notice and objection terms. This register does not create a separate notice period.
Email trust@lithi.ai with your organization, the service and the data category you want to review. Keep private task content, passwords, access codes and payment details out of the initial message.