AtlasCore Market

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

Amazon SP-API Compliance & Acceptable Use

Last updated: August 23, 2026

This addendum summarizes AtlasCore alignment with the Amazon Selling Partner API (SP-API) Developer Agreement, Acceptable Use Policy, and Data Protection Policy for connected Seller Central accounts.

Independent application status

AtlasCore is an independent software application. Amazon, Selling Partner API, and related marks are trademarks of Amazon.com, Inc. or its affiliates. AtlasCore is not sponsored, endorsed, or affiliated with Amazon.

Permitted SaaS sync operations

AtlasCore uses SP-API only after explicit seller authorization. Permitted operations include:

- Catalog sync: listing metadata, ASIN/SKU mappings, and workspace inventory snapshots for seller-operational visibility

  • Order ingest: order headers, line items, and fulfillment status for seller-operational dashboards
  • Inventory: AtlasCore reads workspace inventory snapshots from synced listing metadata. Live seller inventory routes are read-only; AtlasCore does not write quantity or price updates back to Amazon unless a future write-back feature is separately enabled and disclosed

AtlasCore does not scrape Seller Central, use undocumented endpoints, or aggregate Amazon data across unrelated sellers.

Rate limits & API discipline

- AtlasCore respects Amazon SP-API rate limits and implements backoff/retry for throttled responses

  • Sync jobs are batched and scheduled to minimize redundant calls
  • Failed requests are logged for operator review without persisting excessive error payloads

Credential security & prohibited practices

- LWA tokens: Login with Amazon refresh and access tokens are encrypted at rest (AES-256-GCM, `enc:v1:` format). Access-token expiry is stored from LWA `expires_in` and is not inferred from catalog or order sync timestamps.

  • Transport: All production API traffic uses TLS 1.2+ (HTTPS)
  • Workspace isolation: Amazon data is scoped to the authenticated seller account row (`user_id` and that row’s `tenant_id` when bound). Webhook tenancy is resolved from the matched Amazon account by `seller_id` only (fail-closed on multiple matches), never from untrusted notification body tenant fields. Persisted webhook envelopes are an allowlisted operational snapshot (notification type, seller id, event id, Amazon order id).
  • Prohibited: screen scraping, credential sharing, reverse engineering SP-API, re-identifying buyer PII for unrelated purposes, or reselling Amazon API data

Restricted buyer/shipping PII is accessed only through Restricted Data Token (RDT) flows when explicitly authorized. See our Amazon SP-API DPP Disclosure for data governance controls, including the 30-day post-fulfillment and 90-day unfulfilled retention clocks.

Seller controls

- Disconnect Amazon in AtlasCore to stop sync and destroy locally stored credentials and cached Amazon data. Remote token invalidation requires revoking AtlasCore in Seller Central → Apps & Services.

See our Privacy Policy and Disconnect Marketplace guide.