Payment data is the first thing to control.
IBANs and card numbers, controlled on every channel.

Three clocks are already running.
None of this waits for your AI policy to be written.
Eight rules, enforcing from the first hour.
DORA-aligned. Every rule readable, simulatable and yours to change.
Where it stops a leak, in a bank.
A payment instruction, masked before send.
An analyst pastes payment details into an AI tool. The IBAN is masked in the box. The rest of the message goes through.
- Mod-97 for IBANs, Luhn for cards
- One banner, and the analyst keeps working
- One line in the evidence log, no content

A reconciliation file, stopped on upload.
Spreadsheets carry thousands of identifiers. The file is scanned on the device and stopped before it leaves. The banner names the data types found.
- Excel, Word, PowerPoint, PDF, CSV
- A file needing redaction is stopped, not rewritten
- Scanned documents are flagged, never guessed at

An internal script, routed through the gateway.
Engineering routes AI calls through the gateway, on keys you issue. Same policy, same log. Payment identifiers are redacted before they reach the provider.
- Mistral and Azure OpenAI EU stay in the EU
- Non-EU providers blocked per department
- No interception anywhere in the path

Your regulator checks the pack alone.
Export a signed pack for a period and hand it over. They verify it offline, with one command. Deltawall is not in the room.
- Chain, Merkle seal and Ed25519 signature
- Labels and salted hashes only, never content
- The same property protects the works council

What a bank asks first.
01Does this need a change to our network?
No. No proxy, no certificates, no rerouting. One extension, installed through your existing browser policy.
02Where is the data held?
In the EU. Content never reaches our servers. They hold data types, salted hashes and metadata. A dedicated EU tenant with your own keys is available on Enterprise.
03What does the works council say?
We wrote the pack for that meeting. No individual metric exists in the product. Dashboards aggregate by department. Works-council mode removes every individual view.
04How does this sit with DORA?
Third-party risk and operational resilience both cover what leaves through an AI tool. The template controls payment identifiers on every channel. The evidence log is the record that it happened.
05Can our MSP run it for us?
Yes. The console is multi-tenant by design. Device enrolment and live status included.
Let's talk.
Thirty minutes. You watch the product stop realistic data in a real browser.
- Six leaks: three prompts, three files, live
- The dashboard a security lead sees on Monday
- An evidence pack exported and verified while you watch
- Whether a proof of value in your estate makes sense

