The system of record for enterprise AI
CLS++ captures every prompt and response across ChatGPT, Claude, Gemini and every agent you run — into one tamper-evident record. Encrypted on the device before it leaves, so not even we can read it.
Deploys in a day · No change to how people work · Browser extension, MCP server, REST API
What breaks today
Article 12 asks for one thing: reconstruct how any AI-assisted decision was made — who triggered it, on what data, under whose authority. Almost nobody can.
Each provider records only its own slice, in its own console, in its own format. Stitching them into one defensible timeline after an incident is not possible.
Staff paste contracts, code and customer records into personal accounts. Your gateway sees traffic. It cannot see which employee, which document, which decision.
Prohibition moves the usage, not the risk — onto devices and networks you cannot instrument. Every blocked tool becomes an unlogged one.
How it works
Three steps, one afternoon to deploy. Nobody changes the tool they already use.
A 47 KB browser extension plus an MCP server sit where the work happens. Nothing gets re-plumbed.
ZPML encrypts on the device — FHIPE, Paillier and additive secret sharing. Our servers store and search ciphertext they cannot decrypt.
Hash-chained and append-only, so any gap or edit is detectable. Export an Article 12 log on demand.
Why not your model vendor's memory
Google, OpenAI and Anthropic all ship memory. It's a retention feature, and it stops at their own boundary. Three gaps are structural, not roadmap items.