Choose where Latorium processes your work

I could write a giant privacy paragraph here, but it’s easier to just say this: the extension has no Latorium analytics or code-upload server to call. If you don’t believe me, run a packet capture and check.

Install the free tier How it works Security controls

Who handles account data

Christian Yip Jun operates and sells the Latorium software product and is responsible for the Latorium account and licensing records described below. Latorium is the product and brand, not a separate legal entity.

Privacy questions and account-data requests may be sent to support@latorium.com. No postal address is published, because Latorium is sold by an individual rather than a registered business; ask and one will be provided for a formal request.

How to check Latorium Local Coder traffic

How to verify it

  1. Install Latorium and let it set up Latorium Local Coder.
  2. Start a packet capture, or set a default-deny outbound firewall rule with one exception for your local inference port.
  3. Use it normally: retrieval, drafting, completion, the task board.
  4. Confirm Local Coder requests remain on the host.

Latorium Local Coder sends its traffic to the local inference service. Paid-plan licensing requests send only account identity and entitlement status.

Stripe receives payment and subscription information. The licensing service receives an opaque account ID, Stripe identifiers, plan, billing status, and revocation metadata. It never receives source code, prompts, context, embeddings, memory, diffs, Git data, or Local Coder output.

If you continue with GitHub, GitHub authenticates your identity and Latorium stores the immutable GitHub user ID and current login name against your Latorium account. Latorium requests no repository or organization access and does not retain the temporary GitHub access token.

What Latorium stores

Project and AI records stay inside your workspace. If you create a paid-plan account, the licensing service separately stores only the minimum account and billing records needed to authenticate you and provide access.

Audit log
your workspace
Task board
your workspace
Saved lessons
your workspace
Paid entitlement
signed by the server, cached and verified locally
Account service
email, salted password hash, session records, Stripe identifiers and subscription state

Session token counters are read from the logs Claude Code and Codex already write on your machine. Only the counters, never prompt or response content.

Passwords are never stored directly. Sessions expire and can be revoked; password recovery invalidates existing sessions. Ask support@latorium.com to close an account or request deletion of account records that are not required for fraud prevention, tax, payment disputes or other legal obligations.

What each mode sends

Latorium supports different processing modes, and the boundary depends on which mode and agent you choose.

Latorium Local Coder sends its requests to the local service. Claude Code and Codex are cloud services, so whatever context you send them is handled under that provider's terms.

We'd rather write that down than let the privacy claim quietly imply something it doesn't cover.