Is Lobby's Behavioral Model User-Owned and Portable?

Updated

Lobby states that its extensions of human cognition are "user-owned and portable across systems," and that the underlying artifact is a behavioral model that learns, predicts, and amplifies how you think and act. That is the company's stated design intent, not a verified guarantee: the site does not publish a data-handling policy, export format, or deletion procedure, so ownership and portability should be treated as claims to confirm before you connect work tools.

What Lobby says the model is

Lobby describes its first product as a predictive email workflow agent. You connect the tools you already use, and the model predicts your email workflows end to end — the site's framing is "No prompt, you just approve." The behavioral model is presented as the core artifact: it learns your judgment, predicts how you would act, and amplifies that pattern across connected systems.

The site also positions these extensions as eventually coordinating with each other to "amplify collective intelligence." That future-facing language matters for the ownership question, because a model that coordinates across systems implies data flows beyond a single user's account.

What "user-owned" and "portable" would need to mean

In practice, these two words cover several distinct things. A reader should separate them:

Claim What it would require What the site shows
User-owned You can access, export, and delete the behavioral model and its training data No export or deletion details published
Portable The model can move to another system or provider in a usable form Stated as a design goal; no format or mechanism given
Learned from your tools Clear scope of which connected tools feed the model "Connect your tools" and "50+ tools addon"; no per-tool data list
Approval-based action You see and approve predicted workflows before they run "No prompt, you just approve"

"Owned" is not the same as "stored on your device." A model can be described as user-owned while still running on the vendor's infrastructure. Likewise, "portable" can mean anything from a documented API to a one-time data dump — the site does not specify which.

Questions to verify before connecting tools

Because the page evidence stops at the claim, the useful next step is to ask Lobby directly, or check its terms and privacy pages, for:

  • Scope of ingestion: which connected tools and message types train the behavioral model, and whether calendar and email content are both used.
  • Export: whether you can retrieve the behavioral model or its underlying data, and in what format.
  • Deletion: what happens to the model when you disconnect a tool or close the account.
  • Portability mechanism: whether "portable across systems" means an API, a standard file, or a migration service.
  • Sub-agent access: the site mentions "80+ Sub-agents"; ask what data each can read and whether you can restrict them.
  • Approval boundary: confirm that predicted workflows require your approval before sending or scheduling, and whether any actions can run without it.

Practical reading of the claim

Treat "user-owned and portable" as a product philosophy Lobby is building toward, supported by its manifesto language about user-owned extensions. It is a reasonable signal of intent, but it is not yet an auditable commitment on the public page. If model ownership is a hard requirement for your organization, get the export, deletion, and tool-scope answers in writing before connecting email and calendar accounts.