Six steps, for every request
- 1
Check who is asking
Does the request come from a known user, with a valid key? Is its behaviour normal?
- 2
Understand the request
Kusubi recognises what it contains: personal data, sensitive information, type of task. It adds labels to it.
- 3
Apply your rules
Your rules apply to these labels. The request is accepted, adapted or refused. What must not leave does not leave.
- 4
Protect personal data
Names, addresses, numbers: they are replaced before being sent to the model, then put back in place in the response.
- 5
Choose the model
The request goes to the cheapest authorised model that meets the expected quality.
- 6
Measure and keep the proof
Every decision is recorded: who, what, which model, why, at what cost.
Your administrator stays in control
From an administration area, they manage users and their keys, write the company's rules, and see every decision with its reason.
Four requests, four decisions
Fictitious examples. Some requests go through, others are refused: the reason is shown to the user and to their administrator.
-
Request 1 : “Summarise the minutes of Monday's team meeting.”
- Who : passed
- Content : passed
- Rules : passed
- Data : passed
- Model : passed
- Proof : decision recorded
✓ Accepted
What the user seesHere is the summary.
What the administrator seesAccepted · text summary · no sensitive data · standard model
-
Request 2 : “Draft a reply to Ms Martin about her contract no. 4521.”
- Who : passed
- Content : passed
- Rules : passed
- Data : data replaced
- Model : passed
- Proof : decision recorded
✓ Accepted
What the user seesHere is the draft reply. The name and the contract number were not sent to the model.
What the administrator seesAccepted · personal data replaced before sending, restored in the response
-
Request 3 : “Analyse this file of the team's salaries and compare them.”
- Who : passed
- Content : passed
- Rules : Refused
- Data : not reached
- Model : not reached
- Proof : decision recorded
✕ Refused
What the user seesRequest refused: it contains payroll data. Your company's rule reserves this data for the HR department.
What the administrator seesRefused · rule “Payroll data” · reason shown to the user
-
Request 4 : “Here is our server access key: sk-…, check the configuration.”
- Who : passed
- Content : passed
- Rules : Refused
- Data : not reached
- Model : not reached
- Proof : decision recorded
✕ Refused
What the user seesRequest refused: it contains a secret (an access key). Remove it, then send the request again.
What the administrator seesRefused · secret detected · leak prevented · alert to the administrator
The animation stops when the pointer or the focus is on it. With “reduce motion”, the four examples are shown one after the other.