The Caesar® design, in plain words

The Model Gets a Question.
The Names Stay with You.

Caesar® is designed to work like a careful assistant. It takes the names out on your side, then asks an outside model for help. Follow one request from a bank’s compliance desk.

Example 1

A bank’s compliance request

Your side

Outside model

Your side01 The compliance officer asks

Review the three transfers Qadisha Trading SAL made last week from account LB62 0999 … 0122 to Norhaven Bank. The owner is Karim Nassar. Draft the suspicious transaction report.

Outside model

Nothing has been sent yet.

Your side02 Names come out

Review the three transfers Company A made last week from account Account 1 to Bank B. The owner is Person A. Draft the suspicious transaction report.

Company AisQadisha Trading SALAccount 1isLB62 0999 … 0122Bank BisNorhaven BankPerson AisKarim Nassar

This list is the key. It is kept on your side.

Outside model03 The model sees

Review the three transfers Company A made last week from account Account 1 to Bank B. The owner is Person A. Draft the suspicious transaction report.

No client. No owner. No account. No bank.

Outside model04 The model answers

Company A sent three transfers from account Account 1 to Bank B in five days, each just under the reporting limit. Owner: Person A. The pattern is consistent with structuring.

Your side05 Names go back

Qadisha Trading SAL sent three transfers from account LB62 0999 … 0122 to Norhaven Bank in five days, each just under the reporting limit. Owner: Karim Nassar. The pattern is consistent with structuring.

Caesar® uses the key to put the real names back. The officer reads one finished draft.

  • 4identifying facts found in the request
  • 4swapped for stand-ins on your side
  • 0real names in the question sent out
  • 4put back on your side

Illustrative example of the Caesar® design. The company, person, account and bank are invented.

Three levels of protection

Three things are designed to happen before anything is sent.

Taking names out is the first level. Caesar® is designed with two more, so that no outside model is given the whole story.

Level 1 · Facts

Names come out.

Names and identifying facts are swapped for stand-ins. The key is kept on your side.

Qadisha Trading SAL becomes Company A

Level 2 · Context

The request is broken up.

One request becomes several small questions. No single question carries the whole story.

“What must a suspicious transaction report contain?”

Level 3 · Intent

The questions are spread out.

Small questions go to different approved models. The sensitive one is answered by a model on your side.

“What does this client’s transaction history show?” is answered on your side.

Who sees what.

WhatYour sideOutside model
Your whole request and its contextYesNo
Real names and identifying factsYesNo
The key that links stand-ins to real namesYesNo
The sensitive questions and their answersYesNo
Small questions with stand-insYesYes, each model only its own
The finished answer with the real namesYesNo

“So in the end you do send our information to a model?”

A question is sent. Your information is not the question. In the design, an outside model receives a small question with stand-ins in it. It does not receive the client, the account number or the whole request, and it does not hold the key.

This page describes how Caesar® is designed to handle a request.

The same method in a government body

The same method, on a case file and on a briefing.

The request changes. The method does not. Names come out, a question goes out, the names go back.

Example 2

A citizen’s case file

The case officer asks

Draft the letter refusing the housing benefit appeal by Layla Mansour, national ID 1987 0412 663, case HB/2026/04417. Reason: the declared income is above the limit.

The model sees

Draft the letter refusing the housing benefit appeal by Citizen A, national ID ID 1, case Case 1. Reason: the declared income is above the limit.

No name. No ID. No case number.

You read

Dear Layla Mansour, your appeal in case HB/2026/04417 has been reviewed. It cannot be granted because the declared income is above the limit.

The key · kept on your side
Citizen AisLayla MansourID 1is1987 0412 663Case 1isHB/2026/04417
Example 3

A ministerial briefing

The adviser asks

Write a briefing note for Minister Rania Khoury before the meeting with Valdoria on the Northern Port grain terminal, funded from BL 4471.

The model sees

Write a briefing note for Official A before the meeting with State B on the Site 1 grain terminal, funded from Budget line 1.

No official. No state. No site. No budget line.

You read

Briefing for Minister Rania Khoury. Meeting with Valdoria on the Northern Port grain terminal, funded from BL 4471. Three points to raise, two risks, one ask.

The key · kept on your side
Official AisMinister Rania KhouryState BisValdoriaSite 1isNorthern PortBudget line 1isBL 4471

In a briefing, the subject itself can be sensitive, not only the names. That is what levels 2 and 3 are for. You can also decide that this kind of request is answered only by a model on your side.

Illustrative examples of the Caesar® design. Every person, state, site and number is invented.

For banks and governments

Connected to the best models in the world, on your terms.

A closed system is safe and falls behind. An open one keeps up and worries the regulator. Caesar® is designed so you do not have to choose.

For a bank

Customer data is yours to keep.

Client names, account numbers and the full request are designed to be handled on your side.

Outside models help with the general part of the work: wording, structure, reasoning on small questions.

For a government body

Start closed. Open only what you choose.

Many public bodies run open models on their own machines and talk to no outside model. Caesar® can run that way.

When you want newer models, you approve them one by one and decide which requests may use them.

You decide which requests may reach a frontier model, and every one that does is recorded.

  • You setWhich models are approved
  • You setWhich requests may go out
  • You setWhat counts as sensitive
  • You getA record of every request sent
Read this before you rely on it

This page explains the Caesar® design in plain words. Which protection levels are switched on, which kinds of personal data are detected and which models are approved are set for each deployment. Ask us for the configuration of yours, and bring one real request so we can walk it through with your team and show what is sent.

Shape your use case.

Tell us the requests your team handles every day. We will show you how Caesar® is designed to handle them.

Talk to HAQQ

Bring the problem. We’ll shape the use case with you.

You don’t need a defined AI use case to start. We work through it with your team, then the architecture, infrastructure, security review and deployment path your environment requires.

Talk to HAQQ

Prefer email? Write to our team

Discuss your AI deployment.

Tell us what you want to achieve and the constraints you work under.

What can we help with?

We use these details only to reply to your request.