Where your knowledge goes, and where it doesn’t.

Stored on your PC.

Everything the hub keeps stays in one folder on the PC that runs it.

Every change to a document is kept as a full version you can view and restore. The search index is built on your PC. With the default search model running in Ollama on your PC, indexing stays on your PC too.

What leaves your PC, and when.

These are the cases where something leaves your PC. Apart from one automatic download and regular checks of your hub’s public address (in testing), the hub connects only to the services it is set up to use: your sources, the AI providers on its AI models page, which you control, the messaging apps you connect, web addresses that a Memory or tool is allowed to reach, and Tailscale and Google for sharing and sign-in.

Who receives what, and when

Who	What they receive	When	To keep it on your PC
An AI app connected to your hub, yours or a key holder’s In testing	The search results, document text, cards and source names it asks for, from the Memories allowed. It is kept under that person’s account with their AI provider.	Each time it searches or reads.	Share fewer Memories, or revoke the key.
The AI provider the hub uses for its own answers, if it isn’t on your PC	Your question, up to 8 matching passages, up to 5 pinned cards, the Memory’s description and instructions, and up to the last 20 messages of the chat. While answering, it can search again or read up to 20,000 characters of a document.	Each time you ask in the hub, and on every scheduled run.	Put a model on your PC first on the AI models page, and switch off any online provider.
The AI provider the hub uses for corrections and AI-written tools, if it isn’t on your PC	For a correction: the question, the answer, text around the cited passages and your comment. For tool ideas, and when it writes a tool: a summary of the Memory, including recent document titles, card titles and up to 15 recent questions.	When you press Disagree and add a comment, and when it writes a tool. Tool ideas come about once a day per Memory, on by default, with no click.	Use a model on your PC, or turn tool ideas off.
An online search service, if you pick one for a Memory	The text of every passage and every search.	When indexing and searching.	Use the search model in Ollama on your PC.
Your messaging apps	Notices, and the results of scheduled questions sent there. Most notices go to every messaging app you connect by default, and the disagreement notice includes your question and comment.	When a notice fires, or a scheduled question runs.	Switch notices off for each app, or use the Test inbox, which keeps messages inside the hub.
Your work tools, such as Jira, Confluence and Notion	Requests for your content, sent directly from your PC with the credential you gave.	On each sync, and when the hub’s AI looks something up live in Jira or Confluence.	Nothing to change: this is how a source is read.
Your work tools, if you switch on write-back	Corrected text: Jira gets a comment, and Confluence and Notion get the page text replaced.	When a correction is applied with both write-back switches on. Corrections apply at once by default.	Leave write-back off, which is the default.
Websites that a web source reads, and pages the hub’s own AI fetches when a Memory allows them	Requests for their pages, from your PC’s internet address. A web source follows links only to a set depth and page count, and obeys robots.txt.	On each sync, or when the hub’s AI fetches an allowed page.	Nothing to change.
Web addresses that an AI-written tool is allowed to call	What the tool sends them. A tool’s network access is limited to the hub and the web addresses listed in its settings.	When the tool runs.	Keep tools you don’t need switched off.
Google In testing	Only the sign-in. The hub keeps your Google account ID, e-mail, name and, for a Workspace account, your organization’s domain.	Only while you sign in.	Nothing to change.
Tailscale In testing	Tailscale says its relay cannot decrypt your hub’s traffic. It does see connection details: your hub’s address, the internet addresses that connect to it, and how much data flows and when.	While your hub has its public address.	Nothing to change.
Cloudflare’s public DNS service In testing	Lookups of your hub’s public address, from your PC’s internet address. No document content.	About every 5 minutes while your hub has a public address, and more often just after it goes public or while it can’t be reached.	Nothing to change. The checks stop when your hub has no public address.
A public word-list server run by OpenAI	No document content. The server sees your PC’s internet address.	Once, the first time the hub indexes, unless the file is already on the PC.	If the download fails, the hub estimates passage sizes instead.
Us, the makers	Nothing from your hub: the app sends us nothing. Google sign-in uses an app registration we own; see What the app sends us.	Never.	Nothing to change.

When a model on your PC does all of the hub’s AI work, none of that work leaves the PC. If an online provider is also switched on, the hub can fall back to it when the local model can’t answer. What an AI provider keeps or trains on is set by the account it is used under, yours or a key holder’s, and that account’s settings.

One more case: opening the hub’s API documentation page, a page for developers, makes your browser fetch its viewer from a public web server.

What the app sends us: nothing.

The hub sends nothing to us. Its code has no telemetry, analytics, crash reporting, advertising identifiers or update check.

We host nothing for your hub: no online copy of your data, no relay and no account server. Sharing with keys and approving with passkeys need no service run by us.

Google sign-in uses one Google app registration that we own and every hub shares, but the sign-in itself runs directly between your PC and Google.

Planned An optional update check is planned. It would be off unless you turn it on, send no identifier, and install an update only when you choose.

How it’s protected.

What the hub records on your PC.

Records, and how long they are kept by default

Record	Kept for, by default
AI model use, with tokens and estimated cost	30 days
Tool runs, with their input and the start of the result	30 days
Read notifications	30 days
Finished sync jobs	30 days
Calls from connected AI apps In testing	Request and answer text wiped after 7 days; records deleted after 30
Visits to your hub’s approval page, with the visitor’s internet address In testing	Recorded on your PC
Failed passkey or key attempts, with the internet address In testing	30 days
Chats	Until you delete them
Scheduled-question runs	No automatic clean-up
The change log: approvals, key uses with time, app and internet address, revocations, refused Google sign-ins with their e-mail address, secret reveals and other changes	Never cleared automatically
The technical log	Up to 5 MB, plus three older copies

The first four 30-day periods can be changed in Settings. Today the app’s screens don’t show the call records or the change log. Costs are estimates, and the hub has no spending limit of its own for pay-per-use keys.

Your hub’s public address, in plain words. In testing

AI apps such as Claude reach your hub from their own servers, so your hub needs a web address. It gets one from your own Tailscale account, through a Tailscale feature called Funnel. The address starts with https, ends in /mcp, and contains your PC’s name and your Tailscale network’s name. We supply no network, domain or relay for it.

Tailscale says the secure connection ends on your own PC and its relay cannot decrypt your hub’s traffic. It does see connection details: your hub’s address, the internet addresses that connect to it, and how much data flows and when.

The address is public. It is recorded permanently in public certificate logs that anyone can search, so give your PC a neutral name, not your own. Keys and passkey approval work only once your hub has this address.

Known limits

Tailscale calls Funnel a beta feature, so the address can go down when Tailscale has a problem. Only one Windows account on a PC can run Tailscale. A PC signed in to a work Tailscale network has to switch to a personal account, and another VPN app can stop the address working.

Planned setup Planned

You’ll sign in to Tailscale with a personal account, such as Gmail, Apple or a personal GitHub account, not a work account. Tailscale says its free Personal plan is for non-commercial use, so business users should check Tailscale’s paid plans. Then you make two clicks that only you can make, in your own Tailscale admin console: ‘Enable HTTPS and Funnel’, then ‘Disable key expiry’ for this PC. If you skip the second, the address stops working after 180 days until you sign in to Tailscale again.

Planned Later, other ways to get an address may be offered for people who can’t use Tailscale. Some of them would let that provider see your hub’s traffic.

Deleting things.

• Deleting a document removes the hub’s copy, and an uploaded original, and stops later syncs bringing it back. The original in its source system is not touched.
• Deleting a source deletes all its documents from your PC. Deleting a Memory deletes its index, documents, files, cards, tools, chats and scheduled questions.
• In testing A deleted Memory is removed from every connection and key at once.
• A document removed at its source leaves search at the next full sync, but its stored copy stays until you delete it.
• Deletion is ordinary file and database deletion, not a secure wipe, and backups keep their copies.
• The change log keeps document titles and Memory names after you delete them, and it is never cleared automatically.

Questions about your data