TRUST
Intelligence should work under your authority.
TAWALI is being built around explicit permissions, bounded access, human approval for sensitive actions, a security decision before execution, fail-closed behavior, and evidence that can be verified later. Readiness here is stated precisely, not with badges.
TAWALI AI
Intellectual Property & Corporate Trust
Saudi-registered Establishment
TAWALI is developed and operated by a Saudi-registered establishment under Unified National Number 7053042599.
Registered Software Work
TAWALI AI is registered in Saudi Arabia as a computer software and applications work with the Saudi Authority for Intellectual Property (SAIP).
Registration No. 26-12-106719360Registered
Official Corporate Presence
TAWALI AI’s official LinkedIn Company Page.
Follow TAWALI AI on LinkedIn (opens in a new tab)Official Domain
The official website and corporate contact for TAWALI AI.
- Registered work title
- TAWALI AI – منصة توالي للذكاء الاصطناعي
- Certificate type
- Work registration certificate
- Registration authority
- Saudi Authority for Intellectual Property (SAIP)
- Category
- Computer Software and Applications
Registration documents the software work and its intellectual-property record. It does not constitute product, security, or regulatory certification.
CORE AUTHORITY MODEL
Connecting an account is not unlimited access
COMMUNICATION AUTHORITY
Every channel, its own authority level
Communication and social messaging follow the same canonical governance sequence above. Reading is not sending, and drafting is not publishing — each stage requires explicit permission to move past it. An example for a message-handling task:
Understand
Reading and summarizing an inbound message or mention.
Suggest
Organizing the conversation and preparing a draft reply.
Request approval
Nothing is sent or published until approval is explicitly requested.
Act within limits
Sending or publishing happens only within the limits you approved.
OPERATIONAL PROTECTIONS
Review, revocation, and safe behavior
Review and approval
Actions of consequence are designed to be reviewable, with approval requested before they take effect.
Revocable access
Every connection can be reviewed and revoked. Access never becomes permanent by default.
Safe failure and expiry
Expired or failed connections default to the safest behavior, never to broader access.
DATA & CONNECTION PRINCIPLES
Least privilege, most visibility for the customer
GOVERNANCE PRINCIPLES
Capability ≠ Authority ≠ Readiness
What an AI model can do, what this user, workspace, and connected account are permitted to do right now, and whether the credentials and controls are safe at this moment are three different questions. TAWALI keeps them apart and checks all three inside the execution path itself.
Least privilege
Connecting an account grants only the scope a task needs. Reading is not sending, and drafting is not publishing.
Human control
Sensitive governed actions require human approval where required, and that approval is bound to the exact draft, recipient, and operation.
Fail-closed behavior
When authority, credentials, or a required control is missing or uncertain, the action stops rather than proceeding with broader access.
SENTRA before execution
SENTRA evaluates risk before a governed action runs and signals proceed, review, or stop. Its decision is not execution authority.
Fresh authority and duplicate protection
Authority is checked again at execution time. Execution is designed to prevent duplicate execution through idempotency and to surface uncertain outcomes rather than retry blindly.
Evidence before claims
Outcomes are recorded with honest states: verified, attention, not observed, or not applicable. Absence is shown as absence, never as success.
CURRENT STATUS
What is verified, in which environment, and what that does not mean
These states are static and reviewed from TAWALI's public claim register; nothing here is read from a live system. Each item shows when it was last reviewed.
- VerifiedObserved working in the named environment under controlled conditions. Not a statement of public or Production availability.
- BuiltImplemented and tested within its defined boundary, not necessarily activated for customers.
- Not availableNot offered today. Merged code does not change this.
- Default-offCode and controls exist but are disabled and not customer-facing.
Email intelligence: reading, prioritizing, extracting tasks, dates, and risks, and drafting for your review
VerifiedLast reviewed:One governed real email send through the governed execution path
VerifiedLast reviewed:One governed scheduled send through the full control plane
VerifiedLast reviewed:SENTRA risk decisions (proceed, review, stop) evaluated before governed execution
VerifiedLast reviewed:Approval binding, fresh authority at execution time, governed execution, duplicate protection, and evidence records
BuiltLast reviewed:Files and untrusted-content security: database authority foundation
BuiltLast reviewed:Customer file upload
Not availableLast reviewed:Voice: governed voice intake foundations
Default-offLast reviewed:Public Early Access
Not availableLast reviewed:Production activation of governed capabilities
Not availableLast reviewed:
SECURITY DISCLOSURES
What we do not claim
SECURITY MATURITY
Security maturity expands alongside platform capability
Security maturity is expanding alongside platform capability, with controls introduced, tested, and validated in stages. Policy management, audit exports, risk tiers, and compliance readiness remain planned enterprise controls, not capabilities offered today.
