AtlasCore Market

Wayfair Legal addendum · Legal version v1 · Last updated: July 13, 2026

Wayfair Data Handling

Last updated: August 24, 2026

AtlasCore is an independent software application. Wayfair and related marks are trademarks of Wayfair Inc. or its affiliates. AtlasCore is not sponsored, endorsed, or affiliated with Wayfair.

Data accessed

When you connect a Wayfair supplier account, AtlasCore may access:

- Supplier identifier (`supplier_id`) and Partner Home `client_id` as operational identifiers; merchant client secrets and access tokens (encrypted at rest)

  • Product catalog metadata (supplier part number, title, price, stock quantity, listing status)
  • Operational purchase-order metadata only: PO number, status, totals, currency, dates, and line-item SKU/quantity

AtlasCore does not scrape Wayfair Partner Home admin surfaces. Cached dropship PO blobs store an allowlisted operational subset only. Buyer, ship-to, and warehouse address blocks are not persisted.

Seller dashboard reads (`GET /orders/`, `GET /orders/cache/`, and `GET /products/cache/`) return local cache rows only. Live server-side Wayfair GraphQL reads run for background scheduled syncs, `GET /status/` health probes, and credential validation at connect — not for seller dashboard order or product lists. Manual `POST /sync/` and catalog/inventory POSTs also fetch live when the seller starts them.

Encryption & transport

- Merchant client secrets and access tokens are stored using AES-256-GCM encryption at rest with the `enc:v1:` format. `client_id` and `supplier_id` are stored as operational identifiers (not encrypted)

  • Cached order payloads are encrypted at rest and redacted per retention policy
  • Production API traffic uses TLS 1.2+ (HTTPS)
  • OAuth token exchange uses the canonical auth host `https://auth.wayfair.com`

Authentication

AtlasCore uses OAuth 2.0 client credentials against Wayfair Partner Home. Seller writes (`inventory.save` and `purchaseOrders.shipment` ASN) run only when both `WAYFAIR_INTEGRATION_ENABLED` and `WAYFAIR_WRITE_APPROVED` are true. A write-capable Partner API grant is not sufficient by itself. Inbound purchase-order webhooks never issue inventory mutations — Wayfair already decrements managed stock when a PO is created.

Fulfillment responses return only operational identifiers (`handle`, `status`). Raw GraphQL address blocks are not returned to the seller UI.

Webhook security

Inbound Wayfair notifications at `POST /api/v1/wayfair/webhooks/` are verified using HMAC-SHA256 (`X-Wayfair-Signature`) over the raw request body before timestamp freshness (±300s) and JSON parsing. Unknown supplier identifiers that present a valid HMAC are acknowledged with `200` so Wayfair does not retry-storm. If the same `supplier_id` is active in more than one workspace, webhook resolve fail-closes. Connect enforces one active supplier ID globally.

Success-path webhook rows store identifiers only (`event_id`, account binding, `supplier_id`, `order_id`, event type). Leftover failed-row ciphertext is scrubbed after 24 hours. App revocation and supplier deauthorization events persist the event id before credentials and cached data are purged.

Tenant isolation

- Wayfair supplier data is isolated by authenticated `user_id` and tenant/account-bound operational models (`wayfair_accounts`, orders, products), together with the `X-Tenant` workspace header

  • Order, product, and status queries are scoped to the authenticated supplier account within the active workspace
  • AtlasCore never aggregates Wayfair supplier data across accounts for comparative insights or public display
  • AtlasCore strictly prohibits re-identification, sale, or unauthorized secondary use of Wayfair supplier or buyer data

Retention

AtlasCore redacts cached Wayfair order payloads after 30 days post-fulfillment or 90 days unfulfilled from native `poDate` / `created_date`, whichever applies. Fulfillment clocks start at the first terminal PO transition (`SHIPPED` / `DELIVERED` / `CANCELLED` / `CANCELED` / `FULFILLED` / `COMPLETED` / `CLOSED`) and are not reset on later syncs.

Disconnect & deletion

- Disconnect Wayfair from the dashboard purges encrypted credentials and cached orders/products for your tenant workspace

  • Replay defense identifiers in `wayfair_processed_webhook_events` are retained in an unlinked state after credential purge so a later reconnect cannot ingest the same notification twice
  • GDPR export includes all Wayfair tenant bindings per user with `tenant_id`

Contact

For data handling questions: privacy@atlascore-market.com