Let AI Use Internal Documents Without Touching the Raw Data
Keep confidential documents encrypted while passing AI only the needed facts/attributes — with proof. The AI never touches raw PII or originals, and what it used remains provable after the fact.
Three voices from the front line.
- IT / InfoSec
“We want AI in our workflows, but handing internal documents to a model or outside is too risky — so it's stalled”
- Digital transformation / business unit
“The PoC succeeded — but production sign-off is stuck with governance”
- CISO / internal audit
“We have no way to reconstruct or explain what the AI referenced at audit time”
Hand over the source, or just the facts?
Change what reaches the AI, and the leakage risk goes with it.
- name:
- Taro Tanaka
- address:
- Shinagawa, Tokyo…
- contract:
- Plan A
- date:
- 2024-08-15
- id:
- 09xxx-xxxx-xxxx
- agent:
- did:lemma:agent-contract-classifier
- modelId:
- claude-3.7-sonnet
- policyHash:
- 0x71c5…
- inputCommitment:
- 0xb4e2…
- outputCommitment:
- contract tier = A
- satisfiesPolicy:
- true
- ZK verified:
- ✓ VALID
The document stays encrypted, and the AI receives only the necessary facts and attributes — with proof. The model never touches raw PII or the original. Because the AI can prove it used only that fact, you can later explain what it referenced without disclosing the source.
See the technical details ↗Choose on three criteria.
Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-proof |
|---|---|---|---|
| Access control only | △ | ✗ | ✗ |
| Masking / anonymization | △ | ✗ | ✗ |
| Encryption only | ✓ | ✗ | ✗ |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ |
What's next
We enter through AI-adoption and data-governance support and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify document sets / workflows stalled by leakage fear.
- Narrow to 1–2 decisions (results) to prove — e.g. "contract tier A," "credit tier at or above" — the facts passed to the AI. Not the originals.
- Design connection and versioning — connection to your document platform / AI-RAG pipeline, and source-version fixing.
- Prove one path via a (quote-based) PoC.
- Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; the setup and pricing are designed together.
Tell us one workflow where "want AI but scared of leakage" applies, in the first 30 minutes. No disclosure of sensitive data required.
The bigger picture
The bigger picture this use case belongs to.
We map use scenarios across industries and workflows by the four axes.
See use scenarios for Verifiable AI in Solutions →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.