Data inventory
List the client systems, source files, personal-data categories, Company Brain sources, logs, and dashboard records the Agent may use.
Loading AI Team page
A client-safe data map for each Agent, covering data classes, connected systems, storage, processing, model route, subprocessors, transfers, retention, and review ownership.
Buyer question
Buyers can inspect the data path before they share access. UAE SME buyers may be mainland, DIFC, ADGM, another free zone, or outside the UAE. A short deployment map turns that complexity into a reviewable record instead of a vague privacy promise.
Package outcome
Buyers can inspect the data path before they share access.
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.
List the client systems, source files, personal-data categories, Company Brain sources, logs, and dashboard records the Agent may use.
Show storage, processing, model route, analytics, backup, and support locations at the level a buyer can review without exposing secrets.
Record the client owner, AI Team reviewer, transfer review, subprocessor review, retention rule, and reassessment trigger.
Artifact template
Give the buyer a client-safe map of what the Agent can access, where data moves, which providers are involved, and who approved the path.
Name the Agent, workflow, included scope, excluded scope, channel, and owner.
approved_scope_record
List each CRM, inbox, storage, messaging, analytics, website, or finance system the Agent may read or write.
connected_systems_and_permission_map
Classify business data, personal data, public-safe Company Brain sources, internal Company Brain sources, and manual-review data.
data_classification
Show client-safe storage, processing, model route, analytics, support, and backup posture without exposing secrets.
transfer_assessment
Link the approved provider, model route, subprocessor, and transfer review status.
subprocessor_approval
Explain what is retained, what can be deleted, who can request deletion, and what triggers reassessment.
retention_rule
Record the client owner, AI Team reviewer, decision date, and next review trigger.
agent_evidence_review
Before go-live and whenever system access, data class, provider route, retention, or scope 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.
Buyers can inspect the data path before they share access.
The buyer requires a dedicated or all-processing-inside-UAE setup. The workflow includes sensitive, regulated, or excluded data. A provider, storage path, model route, or subprocessor changes. The client cannot identify a data or access owner.
Use config/compliance-governance.json, config/agent-evidence-pack.json, src/lib/compliance.ts, src/components/site/setup-intake-form.tsx as the starting source records for this package.