Skip to main content

Saleor Pulse Data and Privacy

Pulse needs commerce data to power charts and insights. It is deliberate about what it keeps.

What Powers the Views​

Pulse uses Saleor data from:

  • Orders — revenue, refunds, discounts, shipping, status, cancellations, channel, currency, and country for geo views
  • Customers — counts, new versus returning, and rankings by spend (identity is handled carefully; see below)
  • Products and variants — rankings, Product Insights, stock and sell-through context
  • Fulfillments — rates, timing, and related operational alerts
  • Promotions and vouchers — timeline context and discount attribution

After the first import, Pulse stays up to date as that store activity happens.

Customer Identity​

Pulse does not store customer names, emails, cities, voucher codes, or shipment tracking numbers in its analytics data.

Rankings and charts use pseudonymous customer IDs (Saleor global IDs). When someone with MANAGE_USERS opens Top Customers, names and emails are resolved from Saleor at display time — the same trust boundary as the rest of the Dashboard.

Country is kept so geographic charts work. City is not.

A useful way to think about it: analytics storage alone does not expose customer contact details. Showing a name still requires Dashboard permission and a live lookup from Saleor.

Exports​

Widget exports (CSV / JSON) are for the numbers you already see on screen.

Top Customers exports default to customer IDs only. Including names and emails is an explicit choice on that download, so identity does not hitch a ride on every file.

Staff Permissions​

Who can see identity or change sync and alert settings is controlled by Saleor staff permissions. See Configuration.

Next Steps​