Trust and data
Data protection and PDPL alignment in AI work Your data, your rules. Agreed before we start.
Security, data and procurement teams ask the same questions before an engagement starts. This page answers them: where your data lives, who sees it, how we use AI in our own work, and which Saudi frameworks we design against.
Where your data lives
In your environment, in the Kingdom.
We design and build on your systems. What we build runs in your data centre, or with a sovereign cloud provider in the Kingdom that you approve. Data stays in the Kingdom by default. Any exception needs your written approval.
- Your data classification decides where each piece of work happens.
- Where your rules require it, our team works inside your environment, on your devices or accounts.
- Working copies outside your environment are made only where your classification allows, in a location agreed with you in the contract.
- The hosting decision is documented with your security team before the build starts.
Confidentiality
Need to know. Nothing more.
Your material is used for your engagement, and for nothing else.
- Confidentiality terms are agreed in writing before discovery starts.
- Only the people working on your engagement have access to your material.
- We agree retention with you in the engagement contract, and delete or return your data at the end.
- Our published case studies do not name the client. Nothing about your engagement is published without your agreement.
How we use AI
AI in our work. Your rules on your data.
AI is part of how we work: interviews, process mapping, drafting and testing are AI-assisted, which makes discovery faster. That raises fair questions, and these are our answers.
- Before we use any AI tool on your material, we agree with you which tools, where they process data, and what stays out of them.
- Where your classification does not allow outside tools, we work without them, or with tools inside your environment.
- Your material is not used beyond your engagement, including to train any model, unless you agree to it in writing.
- Senior people lead every engagement and review AI-assisted work before it reaches you.
Saudi frameworks
Designed against Saudi frameworks. We claim no certificate from them.
From the first workshop, we design and document controls against these frameworks, on your systems. That is what we mean when we say our work is aligned with them. Octopus does not claim certification or accreditation from any of the bodies below.
Personal Data Protection Law (PDPL)
We map the personal data in each workflow and design how it is handled with your data protection team.
How we apply itNCA Essential and Cloud Cybersecurity Controls (ECC and CCC)
Hosting, access and logging are designed against the controls your organisation is subject to, and documented for your security team.
How we apply itSDAIA's AI Ethics Principles
Every AI system has a person accountable for it, a risk class and a human review path for low-confidence cases.
How we apply itNDMO data management standards
Data readiness and classification work builds on your data governance under the NDMO standards.
How we apply itSDAIA's AI Adoption Framework
Our six practices map to its seven components, and we track pilot-to-production, the KPI it names.
How we apply it- See every framework we apply
For security and procurement teams
Questions we are asked before a contract is signed.
In your environment, in the Kingdom by default. What we build runs in your data centre, or with a sovereign cloud provider in the Kingdom that you approve. Your data classification decides where each piece of work happens.
Data stays in the Kingdom by default. Any exception needs your written approval before it happens, and your classification may rule it out entirely.
Only tools agreed with you before the engagement starts. For each one, we tell your security team where it processes data and what it will and will not be used for. Where your rules allow no outside tools, we work inside your environment.
Not unless you agree to it in writing. Your material is used for your engagement only.
We do not list certifications on this website. Ask us, and we will share our current status and the documents behind it as part of your procurement process. When this page says our work is aligned with Saudi frameworks, it describes how we design, not a certificate.
Yes. Send it with your invitation, or during procurement, to hello@pioctopus.ai.
Confidentiality terms are agreed in writing before discovery starts. Send your standard agreement with the invitation and we will review it.
We agree retention with you in the engagement contract, and delete or return your data at the end. Your team owns the code, the configuration and the documentation of what we built, under the engagement contract.
We have no model to sell and no alliance to defend. Every model and vendor decision is written down with its criteria, test results and exit path, so your team can check it.
A question we have not answered?
Security questionnaires and vendor risk forms: hello@pioctopus.ai, with "Security" in the subject.