# 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. [Send us your questionnaire](https://qantara.systems/contact?topic=security) ## Certifications and frameworks - ISO/IEC 27001:2022 (Information security): In progress. Our information security management system, built to be audited by an accredited certification body. - ISO/IEC 42001:2023 (AI management): In progress. How we govern the AI we deploy: risk, testing, human oversight and change. - ISO/IEC 27701:2025 (Privacy): In progress. Privacy information management, mapped to the Gulf's personal data laws. - SOC 2 Type II (Independent attestation): In progress. An examination of our controls over a period of time, by an independent CPA firm. - CSA STAR Level 1 (Cloud security): In progress. Our answers to the Cloud Security Alliance questionnaire, for its public registry. The laws we deploy under: Oman, Personal Data Protection Law, Royal Decree 6/2022; Saudi Arabia, Personal Data Protection Law; UAE, Federal Decree-Law 45 of 2021 on personal data; Qatar, Law 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. ## 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. ## 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. ## 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. ## 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. ## 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. - Oman: Royal Decree 6/2022, regulated by Ministry of Transport, Communications and Information Technology. In Oman, unless you agree otherwise in writing. - Saudi Arabia: Personal Data Protection Law, regulated by Saudi Data and AI Authority. In Saudi Arabia, unless you agree otherwise in writing. - UAE: Federal Decree-Law 45 of 2021, regulated by UAE Data Office. In the UAE, unless you agree otherwise in writing. - Qatar: Law 13 of 2016, regulated by 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. ## 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 rest: AES-256 for the record, the documents and the log. - Data encrypted in transit: TLS 1.2 or higher on every connection. - One deployment per customer: No customer's data is pooled with another's. - Production access restricted and logged: Only named people, with your approval, every session recorded. - Multi-factor authentication for our staff: On every system that reaches a deployment. - Network access limited to need: Each service reaches only what it must. ### Organizational security - Confidentiality agreements: Signed by every employee and contractor. - Security training: On joining, and every year after. - Background checks: Where the law of the country allows. - Managed, encrypted laptops: Every device that reaches a deployment. - Access removed on leaving: The same day someone leaves. ### Product security - Agents run on past cases before going live: Marked by your team, in Arabic and English. - Tested against hostile input: Instructions hidden in messages and documents. - A person above every threshold: Actions above your limits wait for approval. - Independent penetration test: By an outside firm, with findings fixed and retested. - Vulnerability scanning: Continuous, with critical findings fixed first. ### Internal security procedures - Information security policies: Written, owned and reviewed every year. - Incident response plan: Written and tested, with notice to you in writing. - Backups and continuity: Backups in your country, restores tested. - Risk assessment: Every year, and before every new kind of deployment. - Supplier reviews: Every subprocessor reviewed before it is used. ### Data and privacy - Your data is yours: The record's contents belong to you, and leave with you. - Kept in your country: Where exactly is agreed in writing before anything is built. - No training on your data: Never pooled, never sold, never used to train a model. - Return and deletion at the end: In standard formats, then deleted and confirmed in writing. - Retention rules: How 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. [Report it to us](https://qantara.systems/contact?topic=security) ## Bring your data rules. Send your questionnaire before anyone visits. We answer in writing. - [Where it runs](https://qantara.systems/platform/where-it-runs) - [Control: the thresholds and the log](https://qantara.systems/platform/control) - [The operating record, and how it leaves with you](https://qantara.systems/platform/record) Canonical: https://qantara.systems/company/trust