Jurisdiction path
Route buyers through mainland UAE, DIFC, ADGM, other free zone, outside UAE, or unsure paths collected in setup.
A review pack for owners, operations leaders, IT reviewers, and procurement teams that need jurisdiction, legal, security, privacy, and evidence links before setup.
Buyer question
Sales has one controlled packet instead of improvising legal, security, and jurisdiction answers. UAE buyers may operate under different zone and sector expectations. A procurement pack makes the first review practical while still escalating legal questions to qualified review.
Package outcome
Sales has one controlled packet instead of improvising legal, security, and jurisdiction answers.
What buyers should see
Each section should be short enough for an SME owner, manager, or procurement reviewer to understand before approving access or go-live.
Route buyers through mainland UAE, DIFC, ADGM, other free zone, outside UAE, or unsure paths collected in setup.
Link terms, privacy, DPA, retention, subprocessors, security measures, AI governance, and transfer schedule.
Include data map, Production Evidence Summary, authority matrix, security pack, ROI baseline, and manual-review notes.
Artifact template
Give the buyer's owner, finance, privacy, IT/security, or procurement reviewer one jurisdiction-aware packet with links, limitations, and escalation rules.
Select mainland UAE, DIFC, ADGM, other UAE free zone, outside UAE, or unsure and route unsure answers to review.
compliance_profile
Show excluded sectors, manual-review categories, reduced-scope decisions, or decline decision when needed.
human_review_decision
Link terms, privacy, DPA, retention, subprocessors, security measures, AI governance, and transfer schedule.
legal_acceptance
Attach the Deployment Data Map, transfer assessment, retention rule, and subprocessor review.
deployment_data_map
Attach security pack, access map, revocation owner, credential review, and incident contact.
access_and_revocation_map
Record buyer reviewer, AI Team owner, unresolved questions, approval state, and follow-up date.
agent_evidence_review
Before procurement handoff and whenever jurisdiction, sector, legal terms, data route, or security posture changes.
Risk handling
A package only builds trust when it also explains when AI Team should pause, escalate, re-scope, or decline instead of pushing the Agent live.
Source records
These are the implementation records and public surfaces that should remain aligned as the package becomes a dashboard, PDF, or sales handoff.
Related paths
Use these links when a buyer needs supporting context before setup review.
FAQ
These answers are intentionally practical so owner-operators can decide whether the package is ready, needs review, or should pause setup.
Sales has one controlled packet instead of improvising legal, security, and jurisdiction answers.
The buyer is public sector, education/minors, legal privileged, high-impact HR, or residency-sensitive. The buyer requests regulated advice or excluded workflows. The buyer requires a special hosting architecture. Legal reviewer asks for terms outside standard public pages.
Use config/compliance-governance.json, scripts/verify-uae-compliance.mjs, src/app/uae-compliance/page.tsx, src/lib/compliance.ts as the starting source records for this package.