PIING
Reading Security and privacyWhat data Piing stores
Security and privacy
- Data and privacy overview
- What data Piing stores
- GDPR and your customers
- AI and your order data
- Sub-processors
- Uninstall and data deletion
In this guide
- Operational records stored by Piing
- Customer data processed when needed
- Data kept outside Piing
- Where outputs live
- Retention
Search or browse documentation
Security and privacy 2 / 6
What data Piing stores
The operational records Piing stores, the customer context it processes when needed and the sensitive data that remains outside Piing.
Piing stores enough operational data to run the products a merchant enables. It also retrieves customer context from the merchant's connected systems when recognition, Wallet, attribution, staff context or Intelligence needs it.
Operational records stored by Piing
Depending on the products in use, this can include:
- Check-in and visit events: store, time, source and the references required for reporting and attribution.
- Store and hardware configuration: locations, reader assignments, kiosk sessions, printed scan-in routes and Shopify POS mappings.
- Wallet configuration and instances: pass design, programme fields, claim state, platform, message configuration and delivery records.
- Integration configuration: destinations, subscribed event routes, credentials or references, attempts and delivery status.
- Piing: Alerts: feed appearance, notifications, audience rules, automations, experiment settings and consent-gated engagement.
- Operational and audit records: merchant account, administrative actions, health and support records needed to provide the service.
Customer data processed when needed
A configured workflow can require Piing to process:
- identity and contact details to find the right customer, issue a pass or display permitted staff context;
- loyalty points, tier and rewards from a connected loyalty provider;
- merchant-selected Shopify customer metafields;
- recent orders for Shopify POS, attribution and Piing: Intelligence;
- first-party browsing signals where the merchant has enabled the Intelligence pixel or Alerts targeting;
- wishlist references for staff context, Wallet messages and conversion attribution.
These values remain owned by their source system. Their use and persistence differ by feature, so do not interpret this list as a bulk profile import from every connected platform.
Data kept outside Piing
Piing does not use or store:
- payment card details;
- facial recognition templates;
- biometric identification profiles.
The merchant's commerce platform remains the primary customer record.
Where outputs live
Piing visit fields can be written to Shopify customer metafields when enabled. Piing: Intelligence writes selected attributes, confidence, source and status to app-owned metafields under $app:piing-intelligence.
Those Shopify fields can be read, segmented, exported or removed using the tools available to the merchant and the app. Intelligence does not retain a separate copy of the customer's full order history as its persistent output.
Retention
Retention is record-specific rather than one universal number. Visit, delivery, operational and audit records are retained for the support, analytics and contractual periods that apply to the product, then deleted or aggregated. Account and billing records can also be kept where needed to administer the relationship or meet legal obligations.
For deletion after uninstall or a customer request, see Uninstall and data deletion and GDPR and your customers. The Security page gives the same data boundary in a visual ledger.
Related guides
Was this guide helpful?
Next guide in Security and privacy
GDPR and your customers
How Piing supports data subject requests and the GDPR webhooks it acts on, including data access, customer deletion, and shop deletion.
Still need a hand? Contact us