Your data, held for you.
Operations data is the most sensitive data a company has. We deploy AI inside your systems and in your country, under your rules, and put what we commit to in writing.
Certifications and frameworks
- Information securityISO/IEC 27001:2022Our information security management system, built to be audited by an accredited certification body.In progress
- AI managementISO/IEC 42001:2023How we govern the AI we deploy: risk, testing, human oversight and change.In progress
- PrivacyISO/IEC 27701:2025Privacy information management, mapped to the Gulf's personal data laws.In progress
- Independent attestationSOC 2 Type IIAn examination of our controls over a period of time, by an independent CPA firm.In progress
- Cloud securityCSA STAR Level 1Our answers to the Cloud Security Alliance questionnaire, for its public registry.In progress
The laws we deploy under
- OmanPersonal Data Protection Law, Royal Decree 6/2022
- Saudi ArabiaPersonal Data Protection Law
- UAEFederal Decree-Law 45 of 2021 on personal data
- QatarLaw 13 of 2016 on personal data privacy
Protection in layers. Control in your hands.
Protection in layers
Controls at every stage your data passes through: where it is kept, who reaches it, what each agent may do, and what is written down.
Your data, your rules
You own the record and decide what is kept, for how long and who reads it. It is never used to train a model for anyone else.
Deployed where you need it
In a cloud region in your country, in your own cloud account, or on hardware in your building.
Deployment
In your country by default. In your building when you need it.
Every deployment lives in one place, agreed with you in writing before anything is built. The record, the documents it was written from and the log of every action stay there together.
In-country cloud
A cloud region inside your country, run for you by our engineers. The default, and the fastest way to start.
Your own cloud
Inside your account on AWS, Microsoft Azure, Google Cloud or Oracle, in their in-country regions. You hold the account and the keys. The provider's certifications cover its infrastructure, not our work.
Your building
On hardware in your data centre, for work that must never leave it, with a model that runs there too where the work allows.
One customer per deployment
Every deployment is its own. Your data is never pooled with another customer's.
Your country
- In-country cloudRun by us
- Your own cloudYour account, your keys
- Your buildingYour hardware
Encryption and access
Encrypted everywhere. Reached only by name.
Each person and each agent reads the part of the record its work needs, and nothing else. Every look and every change is a line in the log.
Encrypted in transit and at rest
TLS 1.2 or higher on every connection, and AES-256 for everything stored: the record, the documents and the log.
Behind your single sign-on
Your people sign in through your identity provider, with roles your IT team sets: who may read, approve, change or export.
Agents with a login of their own
Each agent signs in with credentials of its own, never a person's, scoped to one deployment and yours to revoke at any time.
Our engineers, logged like an agent
Our engineers' access is scoped to the deployment, approved by you, and recorded line by line.
- Agent
- Orders agent
- Session
- Signed in with its own credentials
| Resource | Access | Decision |
|---|---|---|
erp.sales_orders | Read, write | Allowed |
erp.price_lists | Read | Allowed |
credit.release | Above your limit | Asks a person |
records.export | None | Denied |
An example policy for one agent. Yours is set with your IT team.
AI safety
Agents tested on your work before they touch it.
A model reads the work in order to do it. Before any agent goes live, you get in writing what it reads, which of it is personal data, and where that model runs.
Run on your past cases
Each agent is run on your past cases first, in Arabic and English, with your team marking what good looks like.
Tested against hostile input
Messages and documents can carry instructions meant for the agent. Every agent is tested against them, and what it reads is treated as content, never as a command.
A person above every threshold
It starts with a low threshold and a person on every case. Its limits widen only when the results hold.
Never trained on your data
No model is trained on your data, and each workflow's model is chosen for it and named before it goes live.
- Run on your past cases, marked by your teamEvery agent
- Model and where it runs, set out in writingEvery agent
- Tested against instructions hidden in messagesEvery agent
- A person on every case at firstEvery agent
- Independent penetration testIn progress
Connections and API
How agents reach your systems.
Agents read your ERP, your e-invoicing provider, WhatsApp and email where the data already is, and write back only what you allow, after the checks you set.
Scoped and revocable
Credentials are scoped to one deployment and yours to revoke at any time.
Authenticated and encrypted
Every call between an agent and your systems is authenticated and encrypted, over private connections where your network allows.
Every read and write logged
Every read and every write is a line in the log, kept in your country and sent to your own systems when you want it.
Nothing replaced
Your systems stay where they are. Agents work inside them, with the permissions your IT team chooses.
- 10:14:02Orders agentread
erp.sales_orders/48213Allowed - 10:14:03Orders agentread
erp.credit_limits/C-2210Allowed - 10:14:05Orders agentasked
credit.releaseTo a person - 10:21:40Sales managerapproved
credit.releaseApproved - 10:21:41Orders agentwrote
erp.sales_orders/48213Written
Every line is kept in your country, and can be sent to your own monitoring.
For regulated industries and markets
Banks, health providers, government-linked groups and anyone holding personal data answer to rules of their own. Bring them, and the deployment is built inside them.
| Country | Personal data law | Regulator | Where your data stays |
|---|---|---|---|
| Oman | Royal Decree 6/2022 | Ministry of Transport, Communications and Information Technology | In Oman, unless you agree otherwise in writing |
| Saudi Arabia | Personal Data Protection Law | Saudi Data and AI Authority | In Saudi Arabia, unless you agree otherwise in writing |
| UAE | Federal Decree-Law 45 of 2021 | UAE Data Office | In the UAE, unless you agree otherwise in writing |
| Qatar | Law 13 of 2016 | National Cyber Security Agency | In Qatar, unless you agree otherwise in writing |
Sector rules reach suppliers through your contracts: the NCA's controls and SAMA's framework in Saudi Arabia, DESC's regulation in Dubai, ADHICS for health in Abu Dhabi. Bring yours to the first conversation.
Security controls
The controls we hold ourselves to
Grouped by area. Each is in place or being put in place as part of our ISO/IEC 27001 work, and is part of what the auditors will examine.
Infrastructure security
- Data encrypted at restAES-256 for the record, the documents and the log.
- Data encrypted in transitTLS 1.2 or higher on every connection.
- One deployment per customerNo customer's data is pooled with another's.
- Production access restricted and loggedOnly named people, with your approval, every session recorded.
- Multi-factor authentication for our staffOn every system that reaches a deployment.
- Network access limited to needEach service reaches only what it must.
Organizational security
- Confidentiality agreementsSigned by every employee and contractor.
- Security trainingOn joining, and every year after.
- Background checksWhere the law of the country allows.
- Managed, encrypted laptopsEvery device that reaches a deployment.
- Access removed on leavingThe same day someone leaves.
Product security
- Agents run on past cases before going liveMarked by your team, in Arabic and English.
- Tested against hostile inputInstructions hidden in messages and documents.
- A person above every thresholdActions above your limits wait for approval.
- Independent penetration testBy an outside firm, with findings fixed and retested.
- Vulnerability scanningContinuous, with critical findings fixed first.
Internal security procedures
- Information security policiesWritten, owned and reviewed every year.
- Incident response planWritten and tested, with notice to you in writing.
- Backups and continuityBackups in your country, restores tested.
- Risk assessmentEvery year, and before every new kind of deployment.
- Supplier reviewsEvery subprocessor reviewed before it is used.
Data and privacy
- Your data is yoursThe record's contents belong to you, and leave with you.
- Kept in your countryWhere exactly is agreed in writing before anything is built.
- No training on your dataNever pooled, never sold, never used to train a model.
- Return and deletion at the endIn standard formats, then deleted and confirmed in writing.
- Retention rulesHow long each kind of data is kept, set with you.
Subprocessors
The companies that process data in a deployment, the cloud region and the models it calls, are named in your contract before anything is built, with where each one runs.
What reviewers ask
Are you certified?
Not yet. ISO/IEC 27001, ISO/IEC 42001 and SOC 2 Type II are in progress, and we will publish each certificate or report when it is issued.
Do you train on our data?
No. No model is trained on your data, and it is never pooled with another customer's or sold.
Where is our data kept?
In your country: in a cloud region there, in your own cloud account, or in your building. Where it runs answers it country by country.
Who at Qantara can see our data?
Only the engineers named on your deployment, with access you approve, scoped to it and logged line by line, like an agent's.
Will you complete our security questionnaire?
Yes. Send it before anyone visits: SIG Lite, CAIQ or your own. We answer in writing.
Who do we tell if we find a vulnerability?
Write to us through Contact and choose the security question. Leave customer data, passwords and access keys out of your message.
Report a problem
If you find a vulnerability, or something that looks wrong, tell us through Contact and choose the security question. Leave customer data, passwords and access keys out of your message.
The mechanism behind the paper
Bring your data rules.
Send your questionnaire before anyone visits. We answer in writing.
Qantara · Muscat