Skip to content

Governance

SDAIA AI Ethics Principles (2025): What to Prove Before You Launch an AI System

Read the 2025 SDAIA AI ethics principles as a pre-launch review: what each principle asks you to prove, the evidence to bring and a review record to download.

4 sources · Evidence review
The SDAIA logo, the subject of this guide to SDAIA's AI Ethics Principles
In this guide6 sections
  1. What do SDAIA's seven AI ethics principles ask you to prove?
  2. Does your AI system need a risk category or registration before launch?
  3. What evidence should be on the table at the review meeting?
  4. How does one failed test change the launch decision?
  5. Who signs the launch decision, and what goes in the record?
  6. What should reopen the review after launch?
  7. Sources
  8. Frequently asked

SDAIA's 2025 AI Ethics Principles name seven principles: fairness; privacy and security; humanity; social and environmental benefits; reliability and safety; transparency and explainability; and accountability and responsibility. Before an AI system goes live, each one turns into a question your team should answer with evidence it can show: who the tests covered, where the data goes, how an affected person reaches a human, what happens on a wrong answer, and who owns the launch decision. The matrix below gives every principle its page in the official PDF, a proposed review question and the evidence to attach, and you can download it as a blank review record without signing up. It is our working aid, not an SDAIA form, and it does not certify anything or decide legal compliance. We checked the official source on 12 September 2026.

Ting working aid · not an official form

Review the missing evidence, not just the heading

These are proposed working questions for each principle, not SDAIA's complete checklist. Page references point to the English 2025 document. There is no automated assessment or deployment approval.

AI ethics review recordSDAIA AI Ethics Principles · 2025 edition

System and version
Intended use
Excluded use
Accountable decision-maker
PrincipleQuestion to answerEvidence to attachIf a gap remainsStatus
01Fairnessp. 12Which affected groups and language variants are represented?Test-set description, group-level errors and an explanation of missing coverage.If a relevant group is missing, collect approved examples or narrow the use case before deciding.Not reviewed
02Privacy and securityp. 15Where do inputs, outputs and logs go, and who can access them?A data-flow map, access rules, retention settings and the relevant privacy review.Keep real data out of the pilot while the authorized data flow remains unresolved.Not reviewed
03Humanityp. 18Can an affected person understand the system's role and reach a responsible person?The disclosure, escalation path and a test of the handoff.Repair a dead-end escalation path; do not substitute an automated response for the missing owner.Not reviewed
04Social and environmental benefitsp. 20What benefit is intended, and what wider costs or harms need examination?A stated benefit, relevant resource-use observations and an impact assessment.Record unmeasured effects as unknown; do not turn an intended benefit into a claimed result.Not reviewed
05Reliability and safetyp. 22What happens on a wrong answer, missing source, timeout or unsafe request?Versioned test results, rejection behavior, rollback steps and the incident owner.Do not release the affected scope while a material failure lacks a tested containment path.Not reviewed
06Transparency and explainabilityp. 24Can a reviewer trace an output to its inputs, version and declared limits?A sample trace, source/version references and a plain-language explanation of limits.Resolve missing provenance before using the output as a basis for consequential action.Not reviewed
07Accountability and responsibilityp. 26Who owns the decision, unresolved issues and post-release monitoring?Named role owners, decision rationale, open issues and review triggers.Keep the decision pending when ownership or resolution responsibility is absent.Not reviewed

Decision

  • Proceed
  • Proceed with conditions
  • Do not proceed
Pending review

Ting working aid · not an SDAIA form, assessment or approval

Download the review record (PDF)Spreadsheet (CSV)Blank record (JSON)

Fill it in locally: nothing is sent or saved by this page. Store the completed copy in your organization's approved storage.

Want an independent check of the system before launch? That is Ting's AI Solution Evaluation.

What do SDAIA's seven AI ethics principles ask you to prove?

Start by citing the right document. When we checked, SDAIA's official Artificial Intelligence page linked a 50-page English AI Ethics Principles PDF with 2025 on its cover.12 The older link this article used to cite still serves a different document, dated September 2023 and marked Version 1.0, so open the file and read the cover instead of trusting a search-result title. This review uses the 2025 document and its printed page numbers. SDAIA also publishes an Arabic edition of the 2025 document, and its seven principles start on the same pages, so Arabic and English reviewers can cite the same page.3

Read the 2025 document's principles as launch questions; the matrix above sets out our proposed version row by row. Fairness (page 12): which affected groups and language variants did your tests cover, and where do errors differ between them? Privacy and security (page 15): where do inputs, outputs and logs go, and who can open them? Humanity (page 18): does an affected person understand the system's role, and can they reach a responsible person? Social and environmental benefits (page 20): what is the intended benefit, and which wider costs did you examine? Reliability and safety (page 22): what happens on a wrong answer, a missing source, a timeout or an unsafe request? Transparency and explainability (page 24): can a reviewer trace an output to its inputs, version and declared limits? Accountability and responsibility (page 26): who owns the decision, the open issues and the monitoring after release? These are our working questions, not SDAIA's wording.

Does your AI system need a risk category or registration before launch?

Page 9 states the framework's scope across AI stakeholders in Saudi Arabia and describes four risk levels: little or no risk, limited risk, high risk and unacceptable risk.1 It says high-risk systems must undergo pre- and post-conformity assessments and describes unacceptable-risk uses as not allowed. Those are the document's words. This article does not place your system in a category or decide which assessment applies; that classification belongs to your governance owner, in writing, before the review meeting.

Page 31 labels the registration mechanism Optional Registration and describes optional reports for registered entities.1 That does not make every privacy, sector or other legal obligation optional. Saudi Arabia's Personal Data Protection Law, for example, sets its own scope: it applies to processing of personal data in the Kingdom (Article 2).4 Two systems built on the same model can carry different obligations, depending on whose data they process and what they decide, and no paragraph here means every business needs the same license, job title or assessment. Ask your legal and governance owners to list the applicable instruments, the authority, the scope and any interpretation still open for this specific system.

What evidence should be on the table at the review meeting?

Bring one evidence packet, not a slide deck. It opens with a system description: intended use, excluded use, users, affected people, the model and application version, and every connection to another system. Add a data-flow map with the processing you are permitted to do, test inputs with expected answers, the failures you observed, how incidents are handled and the proposed rollout boundary, for example one branch or one entity first. Where evidence is missing, mark the row as missing; a benefit statement is not a substitute.

The framework discusses lifecycle activities on pages 10–11, reliability tests and oversight on pages 22–23, traceability and third-party documentation on pages 24–25, and roles on pages 28–31. Our proposed packet groups those concerns for one meeting; it does not reproduce SDAIA's full controls and is not an exhaustive compliance checklist. If a vendor built the system, its documentation belongs in the packet as well. Give each item an owner, a version or date, and a location an authorized reviewer can open.

How does one failed test change the launch decision?

Take a fictional internal assistant that answers staff questions from an approved equipment-support knowledge base and cannot change business records. This is an illustrative scenario, not a client deployment or a completed benchmark. The proposed test: ask a question whose answer is not in the approved material. Expected behavior: the assistant says it has no supported answer and offers the agreed escalation path. Do not invent a pass rate, and do not call the system low risk from a description this short.

Suppose the observed result is an unsupported answer and an escalation link that does not work. That one row touches reliability and humanity at once. Record the exact test and version, the expected behavior that failed, the application owner and the proposed action: remove the unsupported-answer path, repair the escalation link and repeat the related tests. The affected release scope stays pending. The privacy review, the authorization to use the documents and any other necessary checks remain separate open items; passing this one test would not close them.

Who signs the launch decision, and what goes in the record?

The downloadable JSON is a blank working record. Fill it in locally with the system scope, evidence references, findings, responsible roles, proposed mitigations and the reasons for the decision. Its default status is pending review. It does not calculate a compliance score, issue an approval or send the completed record anywhere. Before the meeting, the review owner names who may make the real launch decision under the organization's own process; in a group of companies, settle that for the entity that will run the system.

For every unresolved material issue, record the next action and its owner. If you narrow the scope to launch sooner, for example to one user group, state exactly what stays excluded and which evidence supports the narrower decision. A row with text in it is not a closed issue. The framework's roles section includes entity leadership/CDO, compliance, responsible AI and assessor responsibilities; the record asks for accountable roles without claiming that its field names create new statutory hiring duties.

What should reopen the review after launch?

A pre-launch record needs a handoff to the people who run the system. The framework describes continuing monitoring, performance information, incident logs and assigned alerts in its deployment controls, including pages 23, 25 and 28. We recommend writing down the chosen metrics, failure thresholds, alert recipient, rollback owner and the events that reopen the review: a changed data source, model version, user group or action permission. Rolling the system out to another branch or entity counts as a changed user group.

Keep the source edition and review date with the record, and recheck the applicable guidance when the system or the regulatory context changes; moving the date forward on an unchanged record is not a review. If you want someone outside the build team to run the tests, AI Solution Evaluation is our independent AI evaluation before launch: it tests the system against written cases for accuracy, Arabic quality, use of your data, safety, speed and cost, whoever built it, and you keep the cases and results. AI Readiness Assessment fits earlier, when the question is whether to build at all. Neither is SDAIA approval.

Practical decision tool

What to bring to the launch review

  • A bounded use case and the named person who makes the launch decision.
  • Versioned evidence for each of the seven principles, with gaps written down as gaps.
  • One proposed failure test with its expected behavior and a route for unresolved findings.
  • A scoped decision rationale, follow-up owners and the events that reopen the review.

The internal FAQ assistant walkthrough is fictional and reports no executed test. · The matrix is a working aid, not SDAIA's official controls or a legal assessment. · No risk category, certification, measured outcome or client endorsement is implied.

Sources

Evidence review ·

Primary sources: regulators, standards and official documentation

  1. AI Ethics Principles — 2025 editionSDAIARetrieved: November 6, 2026Official Saudi government source
  2. SDAIA Artificial Intelligence — official document linkSDAIARetrieved: November 6, 2026Official Saudi government source
  3. AI Ethics Principles — 2025 Arabic editionSDAIARetrieved: November 6, 2026Official Saudi government source
  4. Personal Data Protection Law (amended, English text)SDAIARetrieved: November 6, 2026Official Saudi government source

Frequently asked

Which edition of SDAIA's AI Ethics Principles should a review cite?

The English document marked 2025 on its cover, linked from SDAIA's official Artificial Intelligence page when we checked on 12 September 2026, with page numbers taken from that print. The older September 2023 Version 1.0 document is not the basis for this review.

Is this an official SDAIA checklist or certification?

No. The matrix and the blank record are our proposed working aid, with references to the official principles. Completing them does not certify compliance, prove the system is safe or confer regulatory approval.

If registration is optional, are the other obligations optional too?

No. Page 31 describes an optional registration mechanism. It does not settle privacy, sector or other legal requirements; confirm those for the actual system with its legal and governance owners.

Does the review decide our system's risk category?

No. Page 9 describes the framework's risk categories. The record holds your documented assessment and open questions; it does not infer a category, or the assessment process that follows, from a short description.

What happens when a principle has no evidence before launch?

Record it as unresolved and name an owner and the next action. Missing evidence is not an assumed pass. The accountable decision-maker then chooses whether to defer the launch or narrow its scope.

Where does the downloaded review record go?

The blank JSON file is generated in your browser and saved to your device. Nothing is submitted, and the page runs no automated assessment. Keep the completed record in your organization's approved storage.

Related serviceAI Solution Evaluation

Reviewed on November 7, 2026

Want this applied
to your operation?

Contact us