Trust Center
Compute and Connect Trust Center
Review Lithi Compute and Connect security, privacy, billing, evidence, policies, and support by data path, human control, and scope.
On this page
Lithi's Trust Center helps you review Compute and Connect one question at a time. Compute pages cover security, data boundaries, encryption, quotes, billing, receipts, and impact-method limits. Connect pages cover provider finance and human control over relationship work. Shared pages cover privacy, subprocessors, compliance, disclosure, and reporting a security issue. Each page states its scope and limit, so you can match evidence to your product, data path, account, period, and decision.
What this means for you
Use the narrowest page that answers your review question. A Trust page explains a named control, record, process, or policy. It is not a universal statement about every Lithi product, customer setup, provider, region, or time period.
Read the page's review date and limitation before drawing a conclusion. If the question concerns your account, agreement, payment state, or current connection, the applicable signed-in record or contract remains the authority.
Compute
Start with Compute security for how work is scoped, approved, and separated from other customers, and data and processing boundaries for where each data category is stored, processed, and transferred. Encryption and executor access follows protection across a named data path, including where plaintext may exist while a Mac executes accepted work.
For money, quotes, limits and billing explains preview and quote authority, spend ceilings, and the Mercury invoice record that proves a customer payment state. Results and receipt evidence explains what an accepted task's receipt records, checks, and protects, and what it cannot prove.
Monthly impact methodology explains measured, estimated, withheld, and unavailable fields in a Compute impact report, and the evidence a claim needs before it appears.
Connect
Lithi Connect is a human-reviewed relationship workflow. Private relationship context stays on the Connector's own Mac; the Connector chooses the accounts and people to use, reviews proposed work, and performs each action. Connect privacy and human control explains that boundary and where to check a current payout record.
Provider allocation and settlement explains how customer charges and Mac-provider earnings stay in separate records, and which authority proves each one.
Shared review
These routes cover controls that can affect either product or a shared review:
- Privacy explains data categories, connected-service choices, and how to make a privacy request.
- Subprocessors lists provider roles and processing scope. A listed provider does not show that your workspace uses it.
- Compliance and assurance explains how contracts, product controls, tests, and provider reports answer different review questions.
- Disclosure policy explains the response boundary once a security report is open.
- Report a security issue is the safe path for a suspected vulnerability.
- Trust updates records dated changes to this guidance.
Scope and evidence
| Field | Record |
|---|---|
| Scope | Lithi Compute, Lithi Connect, and shared Trust guidance named on this page. |
| Status | Scoped public guidance; account and contract records may control a specific outcome. |
| Owner | Lithi Trust, security, product, and finance authorities, as applicable. |
| Evidence | The linked Trust page, current product record, signed receipt, policy, or finance record for the question. |
| Last reviewed | 2026-09-03 |
| Limitation | A page is scoped evidence, not universal certification or proof. |
Use the page's stated evidence to separate contracts, product controls, focused tests, and provider materials. If a required product, data class, environment, or period is missing, treat the question as open.
Primary action
Contact Lithi Trust support with the product, operation, data category, environment, and period you are reviewing. Do not send passwords, access codes, private records, bank details, or API keys.