SHEIN Open Platform API Compliance

- Credential encryption: Merchant App Secret, open_key, and access tokens are encrypted at rest (AES-256-GCM). `app_key` and `open_id` are stored as operational identifiers

• Transport security: Production traffic uses TLS 1.2+ (HTTPS)
• Tenant isolation: Each AtlasCore user may link their own SHEIN seller account; one active `open_id` is allowed platform-wide. Cross-user seller access is denied at the API layer
• Webhooks: Incoming SHEIN webhooks require HMAC-SHA256 verification (`X-SHEIN-Signature`) over the raw request body before event persistence or dispatch. A bounded parse may run after HMAC solely to extract `open_id` for ledger namespacing. Replay keys persist after disconnect in `shein_processed_webhook_events` only — not an inventory adjustment ledger
• Order data: Only operational fields (order SN, status, totals, currency, dates, line SKU/qty) are stored. Buyer, receiver, and shipping fields are not persisted. Seller dashboard GETs return cache-only sanitized rows. Live server-side reads run for background scheduled syncs, `GET /status/` health probes, credential validation, and seller-initiated sync POSTs (`POST /sync/`, `POST /sync/catalog/`, `POST /sync/inventory/`, `POST /sync/orders/`)
• Fulfillment responses: Delivery mutations return `{ok, order_sn, status}` only

- AtlasCore respects SHEIN API rate limits and implements backoff on throttled responses

• Sync jobs are batched to minimize redundant API calls
• Failed requests are retried with exponential backoff

- Disconnect SHEIN in AtlasCore to stop sync and purge stored credentials

• Revoke authorized app access in SHEIN Seller Hub → Open Platform as needed
• Contact privacy@atlascore-market.com for data subject requests