AtlasCore Market

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

Pinterest Shopping Data Handling

Last updated: August 24, 2026

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

Data accessed

When you connect Pinterest Shopping, AtlasCore may access:

- Merchant account identifiers (`merchant_id`, optional advertiser metadata)

  • OAuth access and refresh tokens (encrypted at rest)
  • Product catalog metadata (titles, descriptions, prices, availability)
  • Commerce order notifications where authorized by granted scopes

AtlasCore does not scrape Pinterest surfaces or harvest pins outside authorized API scopes.

Encryption & transport

- OAuth access and refresh tokens are stored using AES-256-GCM encryption at rest with the `enc:v1:` format

  • Cached catalog JSON stores only an operational allowlist (item id, title, description, price, availability, link) and is redacted per the Pinterest-owned retention worker
  • Production API traffic uses TLS 1.2+ (HTTPS)

Webhook security

Inbound Pinterest merchant notifications at `POST /api/v1/pinterest/webhooks` are verified using HMAC-SHA256 (`X-Pinterest-SHA256-Signature`) against the raw request body. Requests outside a 300-second replay window (via `X-Pinterest-Timestamp`) are rejected before processing.

When Pinterest sends a merchant deauthorization event, AtlasCore revokes stored tokens and executes a tenant-scoped purge for the linked merchant account.

Tenant isolation

- Pinterest Shopping data is stored on a B2C seller base (the signed-in user), with optional workspace scoping when an enterprise tenant slug is bound

  • Personal-mode connections may have a null workspace; `X-Tenant` is not the only isolation key
  • Catalog and status queries are scoped to the authenticated seller (and workspace, when bound)
  • AtlasCore never aggregates Pinterest merchant data across sellers for comparative insights or public display
  • AtlasCore strictly prohibits re-identification, sale, or unauthorized secondary use of Pinterest merchant or buyer data

30/90-day retention

A Pinterest-owned retention worker redacts inactive, deleted, or delisted catalog JSON 30 days after the inactive/delist status change, and terminal channel-order payloads after 30 days. Open (non-terminal) channel-order payloads redact after 90 days. Active in-stock catalog items are never redacted by the catalog clock. See Pinterest Shopping DPP Compliance.

Seller controls

- Disconnect Pinterest Shopping in AtlasCore to purge encrypted tokens and cached catalog metadata for the active workspace

See also Pinterest API Compliance and our Privacy Policy.