OrderBrief Atlas data handling

Privacy Policy

OrderBrief Atlas reads only the Shopify order fields required to summarize merchant-authored order notes and fulfillment instructions. The app stores summaries, operational logs, and checklist state in its own database and does not write those results back into Shopify orders, tags, or metafields.

What OrderBrief Atlas accesses

Only the minimum Shopify data needed to build an internal fulfillment brief is requested.

  • Shop domain and installation metadata for tenant isolation
  • Order ID and order name
  • Merchant-authored order note, tags, and custom attributes
  • Webhook payloads for orders/create, orders/updated, uninstall, billing, and compliance topics

How OrderBrief Atlas uses data

The app is designed for internal fulfillment triage rather than customer-facing messaging.

  • Normalize merchant-authored note text and detect fulfillment signals
  • Generate an internal summary, action text, and risk score
  • Store checklist status so staff can track review completion inside OrderBrief Atlas
  • Keep webhook receipt and processing logs for operational diagnostics and replay safety
  • Encrypt stored order-derived text and raw webhook payloads at the application layer using a dedicated key kept outside the database

Retention and deletion

Stored data is retained only as long as the merchant-configured workflow requires.

  • Default retention is 90 days
  • Merchants can set retention between 1 and 365 days in the app settings
  • A daily maintenance job purges expired order snapshots and webhook logs
  • shop/redact and uninstall flows remove or deactivate shop-scoped records as part of compliance cleanup

Merchant-facing commitments

Support messaging, scopes, and documented behavior stay aligned with the live app.

  • OrderBrief Atlas keeps summaries and checklist state inside the app database only
  • The app requests the minimum Shopify scope currently required: read_orders
  • Stored protected customer data is encrypted before it is written to the app database, while transport remains protected with HTTPS and TLS-enabled SQL connections
  • If Shopify approval for protected customer data is missing, order actions fail with guidance instead of a raw server error
  • Questions about data handling should use the merchant support path documented during app review

Related merchant documents

Use these linked pages when reviewing operational and contractual expectations for the app.

Merchant Terms Scope of use, merchant responsibilities, and plan-aware workflow terms.
Data Protection Processing boundaries, retention, cleanup, and compliance support behavior.