Privacy

Where your data actually sits.

Our three products store data in three different places, so one blanket statement would be useless — or dishonest. This page goes product by product: what is stored, where it is stored, what leaves your device, and what still passes through us.

Last updated 2026-08-03

The one thing that is true across all three: we do not sell your data, we do not use your content to train models, and we do not run advertising.

Beyond that, read the section for the product you use. Where a product routes something through our infrastructure, it says so plainly rather than hiding behind "we care about your privacy".

AgentLoom

desktop app · open source (AGPL-3.0) · nothing of ours in between
API keys
Stored in your operating system's keychain, on your machine.
Conversations
Stored in a database on your own disk. They are not uploaded anywhere.
Your code
Agents work directly in your own repositories, in place. AgentLoom's own bookkeeping never touches your working tree.
Our servers
AgentLoom runs no server on the internet. The only listeners it starts are loopback-only helpers on your own machine.
What leaves your device
Requests to the model provider you chose — and, if you turn on web search, your search queries go to the search backend you configured (DuckDuckGo, or Brave/Exa with your own key). Nothing routes through us.

ProtoLens

web service · GitHub is the access boundary
Repository access
Controlled entirely by your own GitHub App installation. You choose which repositories ProtoLens can see, and you can revoke it in GitHub at any time.
Prototype files
Fetched by repository, ref and path — ProtoLens does not clone your repositories or run arbitrary code from them, does not install your dependencies, and does not run your application backends.
Review comments
Stored as Markdown-oriented review data associated with the prototype being reviewed, and exportable as Markdown at any time.
Rendering
HTML review rendering is sandboxed. JavaScript execution and form submission are intentionally constrained.
Review links
A review URL is the sharing boundary. Private prototype files are not republished as open public assets outside that model.

Loomnote

runs in your browser · notes live in your GitHub repository
Your notes
Plain Markdown files — one per note — in the GitHub repository you authorized. We run no database and never store your note bodies.
Working copy
Local first: the working copy lives on your device and works offline. The durable copy is in your repository, under your name, and one git clone takes everything with you.
Reading with AI
The MCP server is local and read-only. Your own AI client reads your notes on your own machine; note bodies do not reach us.

What still passes through us

  1. The front-end JavaScript is served by us. Whatever we ship, your browser runs — this is not a zero-trust setup.
  2. OAuth token exchange and the CORS proxy we need mean credentials, and sometimes note bodies, pass through our edge in transit. Not stored, not written to disk, not logged.
  3. Your browser cache holds plaintext — on your own device.

This website

Questions, or a request about your data

Write to panda@myagenthubs.com. For AgentLoom and Loomnote, most of "your data" is already in your own keychain, disk or repository — you can inspect or delete it without asking us. For ProtoLens, revoking the GitHub App installation cuts off access immediately.