Skip to content
Skip to content

Privacy Policy

How Lithi handles account, Compute, Connect, support, billing, and browser information, with source permissions and privacy requests kept distinct.

Privacy and data practices

Last Updated: October 27, 2026

Lithi Technologies LLC ("Lithi," "we," "us," or "our") uses information to provide Compute, Connect, and related account and support services. This policy describes the categories and paths involved. Using the website by itself does not grant permission to read a connected account or send a message; those actions use feature-specific permissions and approvals.

Contents

1. Information We Collect

Information You Provide Directly

Information you provide can include:

  • Account and workspace details: Name, email, organization, membership, roles, and access settings.
  • Compute work records: The task description, approved input and output references, quote and approval records, usage, receipts, and delivery status associated with work you request.
  • Connect records: Selected account and source details, contacts or relationship context used for a stated purpose, approved message or plan details, and the resulting action status.
  • Support and security reports: The contact details and description you choose to send when asking for help or reporting a concern.
  • Billing and provider-finance records: Invoice, usage, statement, and payment-status details for the applicable account or provider role.

Mac-provider operational records are a separate category. They can include device enrollment and permitted runtime, release, resource-use and coarse-region evidence. Ordinary health reporting does not require a private application inventory or exact location. Read data handling for the telemetry boundary.

Information Collected Automatically

Website and service requests can create technical records such as IP address, browser and operating-system details, page and interaction events, session identifiers, and cookie or browser-storage identifiers. Their presence depends on the page, enabled feature, and configuration; browser storage is described in the Cookie Policy.

Information from Third-Party Sources

When you connect a service, Lithi may receive information from the account, source, or resource you selected and permitted for the stated purpose. The provider may also process information under its own service terms. The current Subprocessor register describes providers Lithi engages and their stated service roles.

2. Selected Sources and Connected Services

You choose which account or source to connect and the purpose for using it. Permission to read one selected source does not authorize unrelated accounts, records, or actions. Disconnecting a source stops future access through that connection; it does not recall information already delivered to another account or service. The provider and service path determine any additional processing and storage.

For a customer dataset, you must have the rights and authority to use and disclose the selected records for the intended task. Company facts, named business contacts, free-text notes and credentials are different categories. Public availability and a B2B label do not establish eligibility. Local preparation checks the actual permitted working copy and complete request; credentials and prohibited regulated or secret material are refused.

3. Compute Work and Connect Activity

For Compute, local preparation can inspect and prepare information in your environment. A free estimate does not upload task content or start work. If you separately approve a submission, transfer and storage protections apply to the path; ordinary control and relay services handle approved metadata and ciphertext. An assigned Mac reads its piece while performing admitted work, and a privileged host owner may be able to inspect ordinary execution memory. Compute is not confidential computing. Results, destination access, receipts, and billing records have separate purposes and permissions.

Managed key release is the default. A run-scoped release authority can technically unwrap block keys; it releases them to assigned executors under the applicable checks rather than using them to read content. Qualified customer-held profiles keep release on an online customer Kit. Spread placement limits what one owner can receive across their Macs, checking and retry attempts. It does not make the remaining content anonymous or prove that different owners cannot collude. Review encryption and key custody before approving that disclosure.

For Connect, source access, exact action approval, and optional learning consent are separate choices. An approved email or LinkedIn plan is limited to the sender, recipients, content versions, purpose, and timing that you reviewed. The recipient and selected service receive the message and may retain it under their own terms. A draft, source permission, or recommendation does not approve sending.

Ask Lithi uses a server-signed, per-tenant session cookie to scope current-session chat and validates it against the tenant and origin. The server-side authority expires after 30 minutes; a visitor or session identifier alone does not grant access. That session lifetime is not a deletion timer for stored exchanges or ratings, which are separate service records. This policy states no fixed retention period for those records.

The website assistant sends your chat and relevant conversation and page context to Anthropic to generate an answer. This is separate from customer Compute execution and visitor memory. Chat exchanges and ratings are retained as separate service records. Visitor memory stores only selected product topics and facts after filtering; the original chat may contain personal information. Share only information you intend to use in that conversation.

When Visit context for Ask Lithi is allowed, the site records which pages you open, how long each page is visible and in active use, how far you scroll, which page sections appear on screen and for how long, and which Ask Lithi actions or links you use. These are page and interaction events tied to session and browser-storage identifiers. Arrival source, channel, and named AI assistant or agent can also be recorded for permitted site measurement. During your visit, Ask Lithi uses this context to understand what you have been looking at, so it can suggest questions, put the most relevant answers first, and choose what to explain and what to ask you next. It may mention a page or topic you looked at, but it does not list your visit back to you or show times or scroll depth, and these measurements do not establish your identity, actual reading, or comprehension. Lithi does not use this context to identify you, build a cross-visitor profile, or train model weights. The relevant page context includes these measurements and the published text of the sections you viewed with your question.

Where visitor memory is enabled for this browser, Ask Lithi can use it to make a later visit easier. Memory also requires the personalization permission that applies in your region. In the EU, EEA, UK, and Switzerland, personalization waits for consent; elsewhere, permitted visit personalization is on by default with notice. Allowing personalization does not by itself enable visitor memory. Global Privacy Control and a saved opt-out turn them off. The memory can include the source channel, named AI assistant or agent, arrival month, public pages and sections you visited, estimated reading opportunity, product topics, pending conversation threads, language and answer-depth preferences, and lead-submission status as a plain fact. Estimated reading opportunity describes what was available to read; it does not prove that you read or understood it.

The memory can also include visitor-stated facts about your Mac model, chip, memory, Mac count, hours per day, use case, team size, country, or language. It does not include contact details, form contents, secrets, or sensitive facts. Current prices and earnings are never reused from memory. There is no cross-device merge by email, lead, or another identifier.

Where visitor memory retention is enabled, memory is kept for up to 365 days after the last permitted memory signal. Page observations used for current-visit chat context are kept for 90 days and embedded-widget page-view records for 180 days. Chat exchanges, ratings, leads, and provider records remain separate records with separate purposes and retention. When a memory experiment is enabled, a stable ten percent of eligible returning visitors receives no memory personalization for eight weeks so Lithi can measure whether memory helps; chat continues to work for that group. The holdout is a measurement choice, not a different privacy choice.

Ask Lithi can answer “What do you remember about me?” with a plain summary. Choose Forget me in Privacy choices or in chat to erase this browser's visitor memory, record the request without visitor content so earlier activity cannot restore the memory, and expire both visitor identity cookies. Your next visit starts as a new visitor. Turning personalization off also clears current memory and prevents earlier activity from restoring it. These controls do not promise erasure of raw analytics, lead, chat, rating, or provider records.

Visit context follows the visitor's region. In the EU, EEA, UK, and Switzerland, it stays off until you allow it in Privacy choices; elsewhere, it is on by default with notice unless you turn it off there. A saved personalization opt-out stays respected, and an invalid, expired, or ambiguous saved choice keeps Visit context and site measurement off. Global Privacy Control turns off Visit context, site measurement, and advertising measurement for this browser. Advertising measurement is a separate choice and stays off until you enable it in Privacy choices in the footer; you can change or withdraw it there, and changing advertising does not change Visit context. The chat still works without Visit context or memory, and sign-in and essential service storage have separate purposes.

4. How We Use Your Information

We use information to administer accounts and access, provide the Compute or Connect feature you select, enforce the source and action permissions that apply, return results and status, prepare usage and payment records, answer support requests, protect service integrity, and meet the legal obligations that apply to the account. A permission or record for one service purpose does not authorize an unrelated purpose.

Processing an original task does not authorize indefinite retention, exact-copy learning, model training or another purpose. A separate use requires the applicable rights, disclosed purpose, permitted scope and current permission or instructions. Required operational and accounting records remain distinct from optional learning copies. Lithi does not offer customer task datasets for sale.

5. SMS, Voice, and Service Messages

Some account or service workflows may use SMS for a specific notification. A Compute estimate or approval for Connect email or LinkedIn does not authorize an SMS or voice call, and this policy does not grant permission to contact your customers or prospects. Where an SMS feature is enabled, the applicable sender, purpose, recipient, consent, provider path, and stop instructions govern that message. Carrier charges may apply under the recipient's plan. See the SMS Policy for its scope and stop instructions.

6. Legal Basis, Sharing, Security, and Retention

Our legal bases include contract performance, legitimate interests, consent, and legal obligation. Service providers may process information needed for hosting, authentication, connected services, communications, storage, billing, or support. The Subprocessor register lists providers Lithi engages and their stated purposes and data categories. A listed provider does not necessarily process Compute task content, and a list entry does not mean every customer uses that provider.

Google Workspace handles correspondence with Lithi, and Mailgun sends account and service email, including sign-in codes. If you enable advertising measurement, Meta Pixel and the Conversions API can receive page and interaction events, browser and advertising identifiers, network information, and hashed contact details supplied for an applicable lead event. Hashing a contact detail does not make it anonymous. Read the Cookie Policy for the associated browser storage.

Customer Compute invoices, Mac-provider earnings, payout records, and other product subscriptions are separate records. The applicable account, invoice, and payment provider determine which billing information is processed for a payment path.

Banking and payment services handle the information needed for the relevant transaction under their own terms. Using Compute does not require you to open an account with Lithi's banking provider.

Security boundaries depend on the product and data path. Review Compute security, encryption, and data processing for the controls and limitations that apply. Retention also depends on the data category, purpose, product policy, and executed agreement; no one period applies to all information. Expiring access does not prove deletion of stored objects, backups, or destination copies.

7. Your Privacy Rights

EEA users may request access, rectification, erasure, restriction, data portability, objection to legitimate-interest processing, or withdrawal of consent. California users may exercise applicable rights to know, correct, delete, limit use of sensitive information, and opt out of sale or sharing for cross-context behavioral advertising without discrimination. Privacy choices let you decline advertising measurement and site measurement in this browser. Global Privacy Control also disables visit-based personalization, and saved personalization opt-outs remain respected. Contact privacy@lithi.ai to exercise your rights. We may need additional information to verify that you control the relevant records; an email address alone is not proof of identity, and an email request does not erase every record immediately.

8. Cookies, International Data, and Changes

The Cookie Policy describes cookies and browser storage used by sign-in, account connection, public-site measurement, Ask Lithi memory, and the embedded widget. The embedded script keeps its own visitor identifier in browser storage on the page where it runs; that _lithi_vid is separate from Lithi's server-signed lithi_visitor_v1. For Compute and Connect, the selected service and provider determine where information is processed; one provider or reporting region does not establish the location of every processing step. Applicable account terms govern international processing and transfers. We do not respond to Do Not Track signals. Global Privacy Control and the choices described in section 3 govern site measurement, advertising measurement, and visit-based personalization. We may update this policy by posting a website notice, emailing registered users, and updating the Last Updated date.

9. Contact and Compliance

Lithi Technologies LLC. Email privacy@lithi.ai. Lithi does not claim inherited provider certifications as Lithi certifications. Provider reports and certifications apply only to the provider and scope identified in the applicable report.

Primary action

Request a current privacy review