Trust
Sovereignty, stated so you can check it.
This page exists to be forwarded to someone who has to sign. It says where every layer runs, what PDPL requires and how we meet it, how the platform is secured, and the three or four things we deliberately are not.
Where it runs
Every layer, named.
| Layer | Where it runs |
|---|---|
| Model serving | UAE |
| Retrieval and vector store | UAE |
| Object storage | UAE |
| Key management | UAE, keys held by you |
| Audit log | UAE, append only |
| Training on your data | Never, for shared models |
This table also appears in the product's settings screen, word for word. If the site and the settings screen ever disagree, the site is wrong.
Jurisdiction
In-country is not the same as sovereign.
Data residency is a question about geography. Jurisdiction is a question about which courts can compel the company holding the data. They are not the same question, and only one is answered by opening a regional data centre.
A provider incorporated in the United States is subject to US extraterritorial law, which reaches data under that company's control wherever it is stored. A provider incorporated in the EU carries its own equivalents. Neither is a criticism: they comply with the law they are under, exactly as we comply with ours. It is a fact about who can be compelled, and it does not change because the disks moved to Dubai.
KhalijAI is a UAE company operating its own models on its own hardware in the UAE. There is no foreign parent to serve an order on, no upstream model provider holding a copy of your prompts, and no support organisation reaching in from another jurisdiction.
In-country infrastructure, foreign jurisdiction
- ✓Data at rest in a UAE data centre
- ✓Low latency in the Gulf
- ✕The operating company is subject to its home country's extraterritorial law, wherever the disks sit
- ✕Support, operations and incident response often reach in from outside
- ✕Model weights and roadmap belong to someone else, and so does the price
In-country infrastructure, in-country company
- ✓A UAE company, under UAE law, with no foreign parent to compel
- ✓Every layer in the country: serving, retrieval, storage, keys, audit
- ✓Operations and support staffed here, in Arabic and English
- ✓Open weights we run ourselves, so nobody upstream can withdraw or reprice the model
- ✓Zero retention available: run with metering counters and no request logs at all
PDPL
What the law asks, and what we do about it.
| What PDPL requires | How KhalijAI meets it |
|---|---|
| Restriction on cross-border transfer of personal data | Processing, storage and logging occur inside the UAE. Strict residency refuses any destination outside the country rather than warning about it. |
| A lawful basis and stated purpose for processing | The DPA names the purposes. KhalijAI acts as processor, you remain controller, and we do not process for our own purposes. |
| Data-subject rights: access, correction, erasure | Material is addressable by subject across spaces and artefacts. Erasure removes content on your retention rules while the audit trail keeps the record of the act. |
| Security appropriate to the risk | TLS 1.3 in transit, AES-256 at rest, customer-held keys available, per-tenant isolation, SSO and role-based access. |
| Breach notification | Contractual notification timelines in the DPA, with a named contact and an incident process behind it. |
| Records of processing | The audit trail is the record: who, over what data, producing what, in which region. Exportable as an audit pack. |
Security
Shared silicon, never shared state.
Separate at every layer that holds data
Separate vector index, object store prefix, metadata, keys and adapters. Compute is shared, state is not.
Your IdP, SAML and OIDC
SCIM provisioning, so a leaver loses access where you already manage that.
Read as the signed-in user
The platform never widens what a source system granted, and an incomplete answer is marked incomplete in the run trace.
Reviewed, scanned, signed
Dependency and container scanning in the pipeline, signed builds, least-privilege infrastructure access with break-glass logged.
Treated as a real attack path
Untrusted connector content is marked untrusted through the pipeline, tool calls are scoped by the runtime, and every write into a system of record is gated by a human approval.
Annual third-party pen test
Summary letter under NDA, findings tracked to closure, and a published address for good-faith disclosure.
Over time
What happens to your material after the interesting part.
Never, for shared models
Prompts, files, corrections and outputs are not used to train anything served to another customer.
Yours to set
Retention rules per space, and API request logging can be turned off entirely, leaving only the metering counters.
Content goes, evidence stays
Deleting a space shows what goes and what survives. The audit trail is never put up for choice, because a trail that can be deleted proves nothing.
Held by you if you want them
In-country key management. Revoking a key ends access to what it protects.
Your material, on your way out
Export of spaces, artefacts and the audit pack in open formats. No hostage data.
A setting, not a negotiation
Turn request logging off and the platform keeps the metering counters and nothing else. It is where most regulated customers end up.
Deployment shapes
Shared capacity, your own capacity, or your own building.
Three named shapes rather than "shared or enterprise, call us". Moving between them does not mean re-integrating.
Shared capacity, per token
The default. Nothing to provision, prepaid in AED, scale as you go.
Your own capacity, per hour
Reserved GPUs serving a model only you use, including your own tuned adapter, at a fixed hourly rate. A steady workload gets cheaper as it grows.
Your own building, per contract
The platform installed inside your perimeter, for the entities whose rules do not permit anything else.
Administration
The controls a compliance officer asks for, before they ask.
Your IdP, SAML and OIDC
SCIM provisioning, so a leaver loses access where you already manage that.
Written out, not implied
Role-based access with the permitted actions stated rather than suggested by a name.
Shown, not asserted
A settings screen naming where each layer runs, in the same words as this site.
By team, space and person
Usage and cost broken down where the budget actually sits, with caps and alerts.
Exportable as a pack
Every action, the material it touched, what it produced and the region it ran in.
In-country, yours if you want them
Key management inside the UAE, with customer-held keys available.
What we are not
Worth saying plainly.
Not a reseller of a foreign API
The models run on hardware we operate in this country. There is no upstream provider quietly holding your prompts.
Not a data broker
We do not sell, share or analyse your material for any purpose other than serving your request.
Not owned by G42 or TII
We build on Falcon and we are independent of the people who make it. Nobody upstream sees your traffic.
Not a compliance certificate
KhalijAI removes the residency and traceability problems. It does not make your use of AI lawful on its own, and any vendor telling you otherwise is selling you a risk.