NarrowForge B2B Credit Control — Security

1. Scope

This policy describes the current security boundary for NarrowForge B2B Credit Control, an embedded Shopify app that provides store-scoped, read-only receivables visibility. It is an engineering description, not a penetration test or certification.

2. Shopify access

The documented workflow uses these permissions:

• read_customers — resolve the B2B company and customer references required for order context.
• read_orders and read_all_orders — import and reconcile historical and current orders.
• read_payment_terms — read the payment-term and schedule data used for due dates.

The app does not request theme, checkout, write-order or customer-write permissions. The all-orders grant is used for historical receivables reconciliation, not for unrelated data collection.

3. Authentication and tenant isolation

Shopify OAuth and authenticated Admin requests establish the store context. Server-side loaders, jobs, reports and exports scope records to the authenticated store; a browser parameter is never treated as an authorisation boundary. Sessions, tokens and database credentials remain server-side.

4. Webhooks and failure handling

Shopify webhook authenticity is verified before processing. Order, refund, uninstall and privacy events are handled with bounded jobs and auditable outcomes. API errors, rate limits, missing permissions and missing due dates remain visible as unavailable, partial or review states rather than being converted into a clean number by assumption.

5. Disclosure

Report a suspected security issue through the security support form or email support@narrowforge.com. Do not include credentials, tokens or unnecessary store data, and do not disclose the issue publicly before it has been reviewed.

B2B Credit Control does not currently claim SOC 2, ISO 27001 or another formal security certification. Last updated: 2026-09-13.