Your information stays in your company.
We work toward enterprise and international security and compliance standards. What you see on this page is already checked automatically, on every change.
- 1Your database, your account
Your information lives in a database your company owns.
- 2Isolation per clientChecked on every change
Each row is visible only to whoever it belongs to.
- 3The agent's key
Each agent reads only what its key allows.
- 4The model
It gets the text of the task, not your database.
Everyone sees and does what their role allows. So does the agent.
Permissions are assigned by role and each agent has its own key. An agent can read and propose. Approving and sending anything outside always goes through a person.
- Can
- With sign-off
- Cannot
| Read | Propose | Approve | Send outside | |
|---|---|---|---|---|
| Leadership | ||||
| Team | ||||
| Agent | ||||
| Client |
Hover over each cell to see the rule.
Before anything reaches a client or moves money, a person signs.
You decide where that signature goes, process by process. It can move once you know what to trust. It cannot disappear.
Quote 0248, ready to send
The sales agent prepared it with the current catalog. It does not go out until someone approves it.
Who approved it and when is recorded.
Everything that happens is recorded, with the time, who, and where the data came from.
The system writes it, not the agent. It tells you why a quote went out at that price and lets you rebuild the day something went wrong.
| Time | Who | What | Where the data came from |
|---|---|---|---|
| 09:14 | Sales agent | Prepared quote 0248 | Current catalog · request from Sep 22 |
| 09:15 | Sales agent | Sent it for sign-off | Amount above the automatic limit |
| 09:22 | Laura · finance | Asked to see the margin | September price sheet |
| 09:31 | You | You approved quote 0248 | On-screen review, with the margin visible |
| 09:31 | Sales agent | Delivered it to the client | With your signature attached |
| 11:40 | Site agent | Flagged front B as off schedule | Site log · requisition 118 |
What is already checked automatically.
The security program has 50 controls. These are the ones that already pass the automated review. The rest are in progress, and we do not announce them until they pass.
- Isolation per client on every tableOn every change
Each row is visible only to whoever it belongs to. The sweep checks every table.
- No view bypasses isolationOn every change
Views inherit the same permissions as their tables.
- Nobody can empty an entire tableOn every change
The permission to wipe whole tables is revoked for users and visitors.
- No link sends you to an unvalidated destinationOn every change
Redirects only go to our own routes.
- The standard cannot get worseEvery change
If a change breaks a control that was passing, the automated review flags it before it goes in.
- The schema lives in the repositoryEvery change
Every database change is a reviewed migration; what is in the repository is what runs.
- Confidential material under lockEvery commit
Amounts and sensitive data cannot enter the code history.
- Backups reviewed every monthMonthly
They are checked against the provider, and a reminder opens on the first day of each month.
What we will not promise you.
Because whoever answers for the company is going to ask anyway.
- That an agent never makes mistakes.It does. That is why a person signs and everything goes into the log.
- That we hold a certification.We do not. We work toward enterprise and international standards, and we give you the evidence your auditor works with.
- That it installs itself.Where the signature goes is decided with you, process by process.
- That the risk is zero.Nobody can promise that. What we do give you is knowing what happened, when, and who approved it.
Does your security team have questions? We give you the evidence.