Data handling and security architecture.

Operator data is stored in isolated workspaces. No operator can access another operator's records.

Data transfer uses industry-standard transport encryption. Record uploads, API requests, and artifact delivery are protected in transit.

Stored records and artifacts use cloud-provider encryption at rest where available.

Access is restricted to assigned team members. No broad shared credentials. Operator workspaces are separated.

Access to operator data is logged where system logs are available. Operators can request activity summaries.

Operator data is retained only as long as needed for active reviews. Operators can request deletion at any time.

Operator data is never used to train general-purpose models or shared with third-party AI services.

Operator data is never shared with partners, vendors, or other operators without explicit written consent.

Basket economics and leakage analysis

Sales and category contribution mapping

Vendor drift detection and COGS modeling

Zone risk and courier exposure analysis

Pick/pack labor exposure estimation

Substitution behavior and margin impact

Refund root-cause analysis

Stockout and dead-stock analysis