Use cases Privacy FAQ Blog About Request beta access

What could your team accomplish if they never forgot anything?

The Wheel is a privacy-first AI platform for knowledge work. It builds what your team knows into an encrypted record you own, and lets only what the work needs leave.

Build the record · use it where work happens

Comes in from
Drive Uploads Notes A 3am idea Gmail · Calendar · Slack · Notion · GitHub in testing
You choose what comes in · it lands encrypted
The Wheel

Everything you and your team know.

● Your knowledge notes · chats · drafts only you can see it
● Teammate’s their private space only they can see it
Shared team space team docs · notes · decisions promote something private and it becomes part of the team’s work

🔒 Encrypted before it reaches us. Keys unlocked, never held.

You choose what goes out · per tool, per task, revocable
Used inside
Claude Cursor any MCP-enabled tool

over MCP, with your permission · only the slice a task needs leaves · answers land back in the record

Privacy that doesn’t depend on promises.

Encrypted in your browser

Your notes and uploads are encrypted before they reach our servers. We store the locked copies and cannot open them.

Keys unlocked, never held

No raw key is stored anywhere, on any side. Your PIN opens them for one task, then they seal again.

Access by permission

You decide what AI can see, and you can take that back at any time.

A receipt every time

Every run lands on your receipts page: what entered, what stayed private, what left, and what came back.

Patent-pending core · U.S. utility application 19/737,707

The problem

Your team’s knowledge is everywhere except where you need it.

Context is scattered

The doc is in Drive. The decision is in Slack. The reasoning is in a chat history that belongs to a model vendor. You can find the document and still not know why the decision was made.

Knowledge walks out the door

When someone leaves, the files stay and the why goes with them. Every new hire starts with archaeology. Every tool switch starts the record over.

Nobody has custody of the record

Custody is a plain question: who holds the record, who can read it, and who decides what leaves. Today the answer is usually a vendor. Privacy should not require an enterprise contract or a server you run yourself. A promise not to read your data is not the same as not being able to.

The loop

Build it once. Think across it. Use it anywhere. Keep the receipt.

Build the record

Files, notes, conversations, and decisions accumulate in one company-owned place, encrypted in your browser before they reach our servers.

Think across it

Search by meaning or exact phrase without opening the whole library. Only the matches you select get opened, and only while you’re working with them. Ask questions and get answers built from your own material, with the sources shown, not summarized away.

Use it where work happens

Open the record from Claude, Cursor, or any MCP-enabled tool. Only the context a task needs leaves, and what comes back lands in the record. The tool changes; the record stays.

Keep the receipt

Nothing reaches an outside AI without permission. Every run lands on your receipts page: what entered, what stayed private, what left, and what came back. You can revoke at any time.

The receipt: four questions, always answerable

What enteredthe sources and notes you brought into the work.
01
What stayed privateeverything that never left your encrypted library.
02
What left, and wherewhat went out to an outside AI, and under which permission.
03
What came backthe answers and summaries that returned to your record.
04

kept for every run · plain language · yours to delete

An empty record is never presented as proof that nothing left. How privacy works →

Inside The Wheel

Think inside your Wheel: chat that knows your work, because it’s built on it.

The Wheel’s own chat answers from your record. Underneath it, a knowledge graph connects your notes, documents, and conversations, so an answer can draw on the meeting note and the document it referenced, even when you only asked about one of them.

The Wheel dashboard mid-conversation: a grounded answer with three cited sources and nothing leaving custody, beside the Operating Memory, Knowledge graph, and Scratchpad widgets.
01

Grounded answers

Ask in plain language and get an answer built from your own material, with the exact sources shown rather than summarized away.

02

A graph underneath

Notes, documents, and conversations get connected as they come in, so related work surfaces even when you didn’t ask for it by name.

03

Search, two ways

By meaning or by exact phrase, over encrypted content, without opening your whole library to look.

04

Notes, notebooks, spaces

Capture new thinking directly. Private by default; shared with your team only when you deliberately promote it.

Most tools store what you know. The Wheel compounds it.

How this is different

Isn’t this just a chatbot with more context?

A chatbot with more context still keeps that context on the vendor’s servers, on the vendor’s terms. The Wheel is the layer underneath: your record lives with you, encrypted with your keys, and each question sends only the slice a model needs, to whichever model fits it. The receipt names the provider that handled it, shows what left and what came back, and the record stays yours no matter which model you use today or next year.

Where the record lives decides everything else.

Adding context to a chatbot

The vendor holds the record.

  • Memory lives inside one vendor’s product, on their terms.
  • You can’t see what it kept, used, or forgot.
  • Everything you paste is theirs to hold, readable on their servers.
  • One model for every question, whether it fits or not.
  • Switch tools and the record starts over.
  • Deletion usually means less than you think. Read the definition.
The Wheel

The company holds the record.

  • Your record lives with you, encrypted with your keys.
  • Receipts show what entered, what left, and what came back.
  • Even we can’t read what you don’t unlock.
  • Each question sends only the slice a model needs. The receipt names the provider, shows what left, and shows what came back.
  • Works with Claude, Cursor, and other MCP-enabled tools. Keep your tools, keep your record.
  • Deletion is key destruction, and it ends in a signed certificate you can check.

And there is no migration project. Connect a source, and you’re asking useful questions in minutes. No DevOps, no data team, no six-week rollout.

The founding beta

What we’re testing with founding companies.

The beta is invite-only and free. We’re working with a small group of founding companies to answer seven questions before we open wider.

01

Can a single founder recover past decisions without searching five tools?

02

Can a company build investor updates from its own record?

03

Can onboarding work from the record instead of from archaeology?

04

Does the receipt architecture hold under real multi-model workflows?

05

Can a team share context without giving up private-by-default?

06

Does Drive-first ingestion cover enough of a founding company’s record?

07

Can company knowledge survive an AI-tool switch?

In the beta now
  • Google Drive ingestion (you pick the folders)
  • Chat that answers from your record
  • Knowledge graph connecting notes, docs, and conversations
  • Receipts for every AI interaction
  • Support for MCP-enabled tools (Claude, Cursor)
  • Private and shared spaces
  • Gmail, Calendar, Slack, Notion, GitHub in final testing
Intentionally not in the beta
  • Enterprise SSO and admin console
  • On-premise or self-hosted deployment
  • Public API for third-party integrations
  • Custom or fine-tuned model hosting
  • Bulk migration tooling

These aren’t missing. They’re scoped out so we can get the core right first.

The questions come first. The product follows what the answers reveal.

The beta is free. Paid plans follow the shape of your work.

Just you, or your team. A free plan launches alongside them. No ads, no data sales. You pay for the product, or you use the free plan.

Privacy by architecture

Keys unlocked, never held. We cannot read what you have not opened.

Your notes and uploads are encrypted in your browser before they reach our servers. When you ask AI to help with your work, you decide what it can see, and you can take that back at any time. Privacy here is structural, not a promise.

Encrypted in your browserbefore it reaches us
Keys unlocked, never heldopened by your PIN, one task at a time
Access by permissionyou decide · you revoke
Receiptswhat left · what came back
Patent-pending coreU.S. utility application 19/737,707
FAQ

Straight answers to the obvious questions.

How do I know what leaves your system?

Your notes and uploads are encrypted in your browser before they reach our servers. No raw key is stored anywhere, on any side. When you ask AI to work with your record, you give it permission first, and your receipts page shows what entered, what stayed private, what left, and what came back.

What happens if The Wheel changes its terms or is acquired?

Your data belongs to you. You can export it and permanently delete all content on demand, including before any change of control.

Is it as capable as ChatGPT or Claude?

Two different things. The Wheel’s own chat routes each question to a model that fits, from a mix of frontier and strong open-source models, and your receipt names the provider. For work that belongs in another tool, The Wheel brings your record to Claude or Cursor over MCP instead of becoming every tool itself.

How do I get access?

The beta is invite-only and free. Request access below and we’ll be in touch as spots open. If your invitation isn’t working, email us for help.

Read the full FAQ →

Early access

Own the record
before it spreads.

The beta is invite-only and free for founding companies. Request access and we’ll be in touch as spots open.

Founding beta · invite-only · free during beta

This page keeps its own receiptevery request counted on your machine · no cookies · fonts self-hostedsee the receipt →