08 · Security

Nothing needsto leave.

Most AI security is a promise about what happens to your data after it leaves. S◉LOCK is built on a simpler doctrine: it doesn’t.

The perimeter · outbound attempts die at the boundary

The doctrine

Four walls, by design.

Residency, not retention policies. Your prompts, files and outputs are processed where they live — on your machine. There is no “we delete it after 30 days”, because there is no “we”.

The blind vault. Credentials and secrets are sealed so that even the system’s own intelligence handles them as ciphertext. The AI can use a key it cannot read. So can nobody else.

Capability leases, not open doors. When an agent needs power, it is granted a narrow, revocable, receipt-logged lease — never the run of the house. Autonomy inside S◉LOCK is a loan with paperwork.

Receipts for everything. Every consequential action lands in an append-only ledger. Not marketing telemetry — your ledger, on your disk, of what your system did in your name.

For professionals

Client secrecy survives

Law, medicine, finance — the professions that cannot legally paste a case file into a chatbot can put S◉LOCK in the office. The data never crosses the door.

For Europe

Residency is compliance

GDPR’s hardest questions get easy when there is no processor, no transfer, and no third country. The machine is the jurisdiction.

For you

Kill switches you own

Network, autonomy, spending, memory — each behind a switch on your side of the glass. The system asks first. You can make it incapable of asking.

The safest place for your data
is where it already is.