The shape of the licence, before the terms

A licence page usually opens with a price. This one cannot, and it says so rather than putting a placeholder where a ruled number should be. What it can say is the shape: what stays yours, what has to leave your machine — nothing — and what happens to your records when you stop.

Whatever the terms turn out to say, they cannot require your records to leave your computer, because the software is built so that they never have to. The engine listens on the machine's own loopback address by default — it is not reachable from the network unless you make it so. The store is a SQLite file on your local disk, one file per tenant. The model that turns your text into something searchable, BAAI/bge-small-en-v1.5, runs on the machine itself.

That last point is enforced, not promised. If the engine is configured with an embedding provider that would post your text to somebody else's server, it refuses to start. It does not warn and carry on. This is the property the rest of the licence hangs from: a licence to use software that keeps your files where they are is a different thing from a licence to a service that holds them, and this is the first kind.

The files you point the software at are yours before it reads them and yours after. The readable copies it makes from them are ordinary Markdown files sitting on your disk, and they are yours. The index it builds over those copies is yours. Nothing in the design gives the company a copy of any of it. There is no service on the other end of this product, so there is nowhere for a copy to go.

Your corpus is never blended with anyone else's. Every read and every write in the store must name a tenant, and the software refuses the operation if it does not — that is enforced in the data layer, not in a setting. And no model is built from your records. The product indexes and retrieves; it does not fold your history into weights, its own or anybody's. This is the condition that keeps a corpus separable, and separable is what makes the next section possible.

Exporting is copying. The readable copies are plain Markdown, the store is one SQLite file, and the provenance record that says where each document came from and how it was read travels with them. There is no proprietary container to get your records out of, because they were never put in one.

Deleting is yours to do, and it does not need permission. Delete the index and the originals are untouched — the conversion layer never modifies a source file; it reads each one and writes a separate copy. Delete the readable copies as well and you are back to the filing cabinet you started with, byte for byte. Nothing is retained by anyone else, because nothing was sent to anyone else.

No price is ruled, so none is printed. No terms are published, so none are paraphrased. That is not a gap this page is talking around. It is the position, and here is the reasoning behind it.

This product has no customers. Its central promise — that it declines to answer when your records do not carry the answer — was measured once and fell short. A price set before that measurement is fixed would be a price on a claim the record does not yet support. Terms drafted before anyone outside the owner's companies has run the software would be terms written to nobody's actual situation. The company would rather publish the three properties above, which are facts about how the software is built, than publish a number and a clause that would have to be changed the first time somebody used it.

When terms exist they will be published on this page and dated. Until then, the honest sentence is the short one: not yet.