Lithi Trust Center

Compute expects a permitted dataset: company facts you may share are different from named contacts, notes and credentials. See what Lithi receives, and which policy or agreement sets retention.

You choose the work, the data and who gets the result. A job runs only after you approve it, or when an existing approval policy covers it.

Kit-prepared work is encrypted before it leaves your environment. The executor decrypts and reads only its granted piece while the job runs.

Learn which kinds of data Lithi handles, what each is used for and how to ask about yours.

Compute is priced per token, and a quote sets the price and limits before you approve. Check your invoice separately before you pay.

A receipt shows what was recorded for your work and which checks it covered. It doesn't tell you whether the answer is right for your task.

If you share your Mac, your earnings are kept apart from customer bills. A statement shows what you earned; a confirmed payout record shows it was paid.

Contracts, product controls, tests and provider reports each answer part of it. None is a Lithi certification.

Lithi lists the providers it uses, what each one does and which data it handles.

Our acknowledgment confirms we received your report. It doesn't confirm the cause, a fix or a reward.

Email can use an approved delivery plan; LinkedIn and Facebook work stays human-reviewed, with copy-and-open or copy-and-paste handoffs.

Each figure is marked measured, estimated or unavailable, so a missing value never shows as zero.

Tell our security team privately, and test only systems and accounts you're allowed to use.

Tell us the product and what you need to know. Don't send passwords, API keys or customer files.