SAMA & Security
Data Residency & Hosting
Where Sarj runs, where your customers' audio, transcripts and data are stored, and the deployment options for strict residency rules.
Sarj is built for organisations whose data has to stay in the Kingdom. Recognition, reasoning, speech and storage all run in-region, so call audio and transcripts never leave the region you choose.
Deployment options
In-Kingdom sovereign cloud
The standard deployment: Sarj runs on sovereign cloud infrastructure inside Saudi Arabia, with all processing and storage in the Kingdom.
GCC region
For organisations operating across the GCC whose rules allow regional hosting.
Air-gapped private cloud or on-premise
For the strictest residency and security requirements, Sarj can be deployed in an air-gapped private cloud or installed on your own infrastructure.
Your Sarj deployment team recommends an option based on your regulator, your data classification and your security team's requirements.
What stays in-region
- Call audio and chat messages
- Transcripts and the details extracted from them
- Logs of every action taken in your systems
- Any model tuned on your data
Why it matters for latency
Hosting close to your callers also keeps conversations fast. With the whole pipeline in-region, Sarj holds sub-120ms conversational latency without routing audio abroad.