Data handling principles
Systems of record stay authoritative
ERP, CRM, accounting, and document systems remain the source of truth.
Ubik is reviewed action
Sensitive replies, writebacks, and owner handoffs require review before they move.
Access stays narrow
Users and integrations should only see the context needed for approved workflows.
The trail must explain the decision
Activity history should show what changed, who reviewed it, and where the work moved.
How AI uses business context
Ubik uses AI to plan, reason, summarize, compare, and draft actions. It should not be treated as an unattended employee. Operators still review sensitive work before it moves. Ubik minimizes what is sent to external models. Sensitive context such as RFQs, supplier pricing, margins, customer names, and credentials stays in Ubik’s context layer, local workspace, or private deployment depending on setup. Customer data is not used to train third-party models.What reviewers should check
| Risk | Review behavior |
|---|---|
| Pricing exposure | Remove internal margin, supplier notes, recovery strategy, or finance commentary from buyer-facing text. |
| Wrong account | Confirm source context, CRM account, and buyer identity before approval. |
| Stale data | Reject or assign if inventory, ETA, pricing, or owner context is not current. |
| Overbroad access | Ask an admin to reduce scope or remove users who no longer need access. |