Kanhe · PersonalXD-P · 2026
A relay service can read every word you send

A local checkpoint
between you and the model

API keys, ID numbers and bank cards are blocked outright. Phone numbers and emails become ⟦KH_1⟧ before they are sent. What comes back goes through response verification across five checks. Every credential is written to a provenance ledger you can export as an evidence bundle.

Windows / macOS / Linux · Free during betaPricing
Package checksums:MD5 / SHA256

Security logSample data
Problem

What it can see

The relay you use is the only link in the chain holding plaintext.

Article I

Everything you send

Prompts, pasted code and uploaded documents are all fully readable by the relay.

A relay is not a blind forwarder. It necessarily holds the plaintext.

Article II

Everything it returns

Standing in the middle of the path, it can rewrite content before it reaches you.

A modified response is not always obvious.

Article III

The model that answers

The model you asked for and the model that answered may not be the same one.

Downgrades, swaps and truncation can all happen in between.

Two layers

Swap on the way out, verify on the way back

Both run on your own machine. Conversations never pass through our servers.

Article IV

On the way out

Before a request leaves the machine, sensitive fields are replaced with placeholders and only then handed to the relay. API keys, tokens, ID numbers, bank cards, phone numbers and emails are all covered.
Article V

On the way back

Returned content passes five checks before it is shown to you.Instructions smuggled into the answerYour system settings were rewrittenThe response length suddenly changedIt wants to call your toolsIt wrote your information out
Addendum

Who mentioned it first

Every sensitive credential records the direction, role and time it first appeared. A credential that shows up for the first time in a response is flagged separately — that is the only way to tell “my task needed it” from “someone took it off the wire”.Exportable as an evidence bundle.
Three tiers

You decide how much to block

No parameters to tune. Three tiers map to three levels of action.

Relaxed

Only handle high-confidence risk; keep the model output as intact as possible.

Block what is clearly dangerous; log the rest

BalancedDefault

Balance safety and usability, weighing interception against false positives.

Handle dangerous and suspicious; log and warn on the rest

Strict

Widen interception and put safety first.

Block anything suspicious; degrade what is uncertain

Statistical signals such as health hints and content-policy hints are only logged and surfaced — they never discard a whole reply. Only responses that match explicit risk features are blocked or degraded.

Data

Data stays on this computer

A boundary you can account for, line by line, is the only real boundary.

Article VII

Local database

Conversations and detection records stay on your machine. Nothing is uploaded.
Article VIII

No secondary use

Not used for training, not used for anything else.
Article IX

Machine code only for activation

Used to issue and validate activation codes, nothing more.
Procedure

Four steps and you are running

Nothing to configure in between.

I

Download and install

Download the package for your system and double-click to install.

II

Copy the machine code

Open the Activation page in the client and copy the machine code.

III

Register and claim

Sign up with an email address, submit the machine code, claim an activation code.

IV

Paste it back

Paste the activation code into the client. Done.

Beta

Open and free during beta

It works, but it is still being polished. Free during beta — register and use it.

One

Register and use it, no cap

Sign up with an email address and a verification code, then submit your machine code to claim an activation code. There is no cap during beta.

No invite code, no waiting list.

Two

You may hit rough edges

The beta is still fixing false positives and compatibility issues, so an occasional decision may not match your expectation. You can switch tiers in the client, or send us the details and we will check each case.

If something is blocked that should not be, tell us.

Three

Data stays on your machine

Conversations and detection records stay local. Nothing is uploaded or used for training. The machine code is only used to issue and validate activation codes.

The beta does not change the privacy boundary.

Addendum

Questions you may have

About activation and privacy.

What if I change computers?+

An activation code is bound to a machine code. After switching devices, claim a new activation code for the new machine code on the website.

Do activation codes expire?+

Yes. The expiry date is shown in your web account. Please activate before it passes.

Do you upload my conversations?+

No. Conversations are processed and stored locally. The machine code is only used to issue and validate activation codes.

Which systems are supported?+

Windows 10/11 is the primary target. macOS (Apple Silicon) and Linux (deb / AppImage) ship with each release. The download button picks the right package for your system. Windows 7/8 no longer receive security updates and WebView2 is frozen there, so we do not recommend them.

What if it blocks something it should not?+

Statistical signals are logged, not blocked. If a decision does not match your expectation, switch tiers or send us feedback.

Install it, use it for a week, then decide

Free during beta, no card required. Once installed, the log shows exactly what it blocked and what it let through.