Privacy Intrusion Prevention. Use any AI. Keep your data.

By Pillar Delta AI

See how it works

The film

ZEROTRACE in one minute.

One minute, with sound.

The problem

Your people already send client data to AI.

A privacy intrusion is private information reaching someone who should not have it: an AI service, its staff, or an attacker using AI. Security was built to watch signals: files, links, networks. With AI, client data leaves as ordinary sentences, and only something that reads their meaning can stop it.

Needs a person · todayExample

1,240sensitive details sent out, unchecked

Nobody checks what leaves, and nobody can prove it afterwards.

Client names, account numbers, health details and salaries go out with the work. There is no record of what went, so there is nothing to show a client or an auditor.

Example · four teams, one working day

The check

Every request is read before it leaves.

We build the first Privacy & Security LLM. Each request is checked in layers: rules first, then our LLM looks again. Names, account numbers and health details become codes before anything leaves, and are put back in the answer.

One request from Claims, read before it left

3details hidden

The work still gets done.

The name, the policy number and the IBAN were replaced by codes before anything left your building. The outside service summarised the claim with the codes; ZEROTRACE put the real details back into its answer before anyone read it.

Made-up example · not a real claim · Claims, 19 Nov 2026, 09:41

Inside your building

Please summarise the claim of Maria Papadopoulou, policy 77-4410-92, paid to GR16 0110 1250 0000 0001 2300 695, before the hearing.

What leaves, for the outside service

Please summarise the claim of Person 1, policy Policy 1, paid to IBAN 1, before the hearing.

The answer, as your people read it

The claim of Maria Papadopoulou under policy 77-4410-92 is complete. Pay GR16 0110 1250 0000 0001 2300 695 before the hearing.

The route

Sensitive work stays inside. The rest goes to the best service for the price.

Against one premium serviceExample

31%of the spend

Your rules choose the route. Nobody has to stop and decide.

The medical report stays in your building. The contract goes to an EU service with the client's names turned into codes first. The press release goes worldwide, at the lowest price. If a service is down, the work waits or stays inside. It never goes wider.

Example · Claims, Legal, Comms · 19 Nov 2026, 09:41

Where each piece went

  1. In your building

    Health data, privileged files, anything your rules call secret.

    Medical report · claim 4410stayed inside

  2. EU service

    Work your rules allow inside the EU, with names turned into codes first.

    Contract draft · client namescoded, then sent

  3. Worldwide

    Public and low-risk work, sent to the best service for the price.

    Press release · publiclowest price

nothing leavesleaves with names in codeleaves as written

The record

Every decision is written down. Nobody can rewrite it.

Each decision is sealed to the one before it. If anyone changes one afterwards, the record shows exactly where.

Record checked · 1,284 decisionsExample

1change found

Changed afterwards: its seal no longer matches.

The claim summary sealed at 09:41:19 now says it was sent worldwide. When it was written, it stayed inside. The check recomputes every seal, so it names the exact entry; the decisions around it are untouched.

Example · the record of 19 Nov 2026, 09:41:02 to 09:41:33

The record, as it was written

  1. Medical reportstayed inside · seal 7f3a…c21e
  2. Contract draftcoded, EU · seal 1b88…04d7
  3. Claim summarystayed inside · seal 3c5e…a91fsent worldwide · seal does not match
  4. Press releaselowest price, worldwide · seal 9d02…6be3
  5. HR letterstayed inside · seal e41c…7a08

Made-up example. The titles are labels for this page only: the record keeps what was decided, never what was written.

The promises

What ZEROTRACE can never do.

Checked each time the Node starts

5rules, built in

No administrator can switch them off.

They are written into ZEROTRACE itself, not into its settings. A settings file that tries to loosen one is refused, and the Node does not start until it is put right.

ZEROTRACE can never

  1. 01

    Send what must stay inside to any outside service.

    built in
  2. 02

    Take a wider route when something fails. It waits, or keeps the work inside.

    built in
  3. 03

    Loosen a check. New checks can only add caution.

    built in
  4. 04

    Keep your text in its record. It keeps what it decided, never what you wrote.

    built in
  5. 05

    Be loosened by a setting. No setting reaches these five; team settings can only tighten.

    built in

Where it runs

In your building, under your keys.

Your perimeter

1way out, and it is checked

Everything that leaves passes one checked gate.

ZEROTRACE runs on your own hardware or private cloud. Your people keep the tools they already use: their work goes to the AI service inside your building, or leaves through the gate, where every request is read first.

What stays yours

  • Your hardware or your private cloud
  • Your keys. We never hold them.
  • The inside route works without internet
  • Nothing calls home to Pillar Delta

For your sector

Made first for work that must stay private.

Insurance first, then legal, then any regulated company.

  1. Insurance

    Claims, medical reports, fraud files

    Handle claims with AI while health data and policyholder names stay inside.

    Health data stays inside

    See it for insurance
  2. Legal

    Privileged files and client names

    Draft and review with AI without putting professional secrecy at risk.

    Privileged files stay inside

    See it for legal
  3. Any regulated company

    HR, finance, health, public sector

    One gate for every team, and a record your auditor can check.

    What your rules call secret stays inside

    See how it fits

Next step

See it on your own documents.

Your briefing

30minutes

For your management and your IT team, on the kind of work you do.

  1. 01Where the Node would run: your hardware or your private cloud
  2. 02What it checks and where it routes, on your kind of work
  3. 03What your auditor gets: the record and its check

Your request

or write to info@zerotrace.ai

We use your details only to answer this request.