Every line here is something you can go and check, or a limit we are naming before you hit it. If you cannot verify it, treat it as unproven — that is the standard we hold ourselves to everywhere else.
Your work — every answer, every file, every picture — is written to your own disk by software running on your own machine. We run no session store, no queue and no copy of your results. There is nothing here for it to sit on.
Your email, the web address of your own machine, when you paired it, and a name you chose. That is the whole record. It is a bookmark, not an authority: your machine decides what it serves, not us.
When you work, the page connects directly to your own machine. This site is not in that path. Nothing here forwards a turn, and nothing larger than 4 KB can be posted to this site at all — a conversation does not fit through it.
no route here carries your workYou place your key yourself. Nothing here ever sees it. No field on this site accepts one, and we never make a model call for you — so there is nothing to leak and nothing to trust us about.
no field here accepts a keyA limited pass, so your machine can check its own access with us. The pass opens exactly one question on this site — still entitled, or revoked — and nothing else. Three facts about it, named here before you have to find them. It renews itself at each good check-in, so access continues until it is revoked — and if your machine cannot reach us, the pass expires within 24 hours. Your account email is inside it, in the clear — it lives on your own machine, readable only by your user account, and that is still worth saying. And if this portal is ever set to fail open at the end of its life, this pass is how your machine collects the grant that keeps it working. The pass your machine uses on you is a different one, minted by the machine itself. We never see it.
one question is all it opensYour prompts go to Claude or GPT — that's what a model call is. Your work and your files stay on this machine. What the vendor keeps after that is theirs to state, not ours; we make no claim about it here.
your prompts go to the model vendorUnpairing, purging and uninstalling each return what was removed, what was kept on purpose, and a check you can run yourself. If you cannot verify it, treat it as unproven — that is the standard.
Code on a machine we do not own cannot be made truly unusable, and we will not pretend otherwise. Your work is never deleted on any path — cutting access disables our software, never your files.
Revoking access removes the portal, the tunnel and the interface immediately, and disables the agent at its next check-in (within 24 hours). It does not reach into a machine we do not own — and it never touches your files.
A six-digit code by email. No password, so there is nothing to steal from us and nothing for you to lose. The code works once and expires in 10 minutes; a sign-in lasts 24 hours, and your machine renews it by checking in.
We cannot email a sign-in code to just anyone yet — until our sending domain is onboarded on a paid plan we can only reach addresses verified on our account, and the sign-in page says so plainly rather than spinning. And the engine underneath is read-only, checked byte-for-byte every time it starts.
Engine pin 3798fbc, verified at boot: 6 of 6 scripts byte-identical, 0 alerts.
| field | what it is |
|---|---|
account | the email you sign in with |
agent_url | the web address of your own machine |
paired_at | when you connected it |
label | a name you chose, to tell two machines apart |
Alongside it: a one-way hash of your current sign-in code, a one-way hash of your session cookie, and — if it ever happens — one line saying when access was cut off and why. That is all of it. Read this page as data if you would rather diff it.