Know what happens to your data before uploading

Accounts and access

Every company account requires password plus authenticator code, with recovery codes. Company records are separated. Owners assign roles and narrower permissions. All plans include these controls.

AI processing is optional for structured orders

The supported order CSVs, Excel template and structured API work without AI. General PDF/photo/spreadsheet reading sends the uploaded file to Anthropic's API. By default, Anthropic does not train on commercial API inputs/outputs; consent, feedback and account agreements may change those terms. Retention and processing location need to be reviewed for your agreement.

Anthropic training policy · API retention policy

Records and revisions

New/updated company records use authenticated encryption. Existing plaintext records require migration. Changes record old/new values, actor and time; they invalidate previous approval. A change history is not an independently certified immutable archive.

Production status

This beta is served over HTTPS. Company records are stored on the configured server, not on this device. Backup restoration, monitoring and data-processing terms still need deployment-specific verification. No SOC 2 report, independent audit or customer reference is claimed.

Scope you can evaluate

Export-document preparation and consistency checks for supported workflows. The US/UK focus describes the initial exporter markets. Examples include other destinations; destination-specific legal documents still need your specialist or forwarder.

QuickBooks/Xero are accounting connections. They are not native SAP, NetSuite, CargoWise, Oracle or Dynamics integrations. Those systems require a vendor-specific bridge. ECCN/licensing, restricted-party screening, USMCA eligibility, CITES and signed dangerous-goods declarations are outside the current product scope.