1
On your computer
Protect the details
Supported names, account numbers, emails, and terms you add become stable stand-ins.
Private values stay localArchitecture · explained visually
See exactly where your information goes.
FusionWall prepares private work on your computer, pauses for your approval, sends only the protected request to the AI service you chose, then restores the answer and records what happened locally.
One governed request
Four moments. One person stays in control.
2
Your checkpoint
Review the exact send
Inspect the protected request, AI service, model, policy result, and warnings.
You choose send or cancel3
Chosen AI service
Receive a response
The provider receives the protected request and routing information required for the call.
Provider terms still apply4
Back on your computer
Restore and record
FusionWall restores private values on screen and adds a linked receipt to local evidence.
Answer and proof stay localTrust boundary
Most information never crosses the line.
The middle checkpoint is the boundary between customer authority and the selected AI provider.
Your computer
Customer-controlled workspace
Remains here
- Original files and raw values
- Encrypted stand-in mappings
- Vault contents and custom terms
- Restored answers and local receipts
FusionWall does here
- Detects supported sensitive details
- Applies policy and shows warnings
- Restores values after the response
- Links the action into local evidence
→Human
approval←request out
answer back
approval←request out
answer back
Selected service
AI provider account
Receives for the approved call
- Protected request
- Selected model and fixed route
- Provider credential through its API
- Required provider metadata
Your provider agreement, retention settings, and data-use terms still apply.
Private receipt
A useful record—with honest limits.
What was proposed
Protected request fingerprint, selected evidence, provider, model, and active policy.
What was decided
Policy result, warnings, approval state, and whether the person chose to proceed.
What happened
Outcome metadata and the link to the preceding local receipt in the tamper-evident chain.
This is local evidence, not external notarization. A local administrator with full control can replace local state. The receipt helps reveal later changes when the linked chain is still available; it is not a third-party attestation.
Show technical detail
Outbound: FusionWall creates a protected request locally, binds it to the configured provider, endpoint profile, model, policy decision, and human approval, then performs the provider call.
Inbound: The provider response returns to FusionWall, where stand-ins are restored locally for display. Receipt hashes and outcome metadata are written into the local linked ledger.
Boundary: Raw source files, decrypted vault material, restoration mappings, and restored response content are not part of the intended provider request. Provider-side processing remains governed by the provider account and contract.
Keep evaluating
Review the evidence behind the diagram.
Explore a sample receipt or continue into the deeper security explanation.