PIING
Reading Security and privacyData and privacy overview
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
- The three-part boundary
- Product-specific write-back
- Security and retention
- Where to read more
Search or browse documentation
Security and privacy 1 / 6
Data and privacy overview
How Piing separates operational records it stores, customer data it processes for configured features and data that remains outside Piing.
Your commerce platform remains the primary customer record. Piing stores the operational records needed to run recognition, Wallet, attribution, integrations and Alerts, and it processes customer context when a feature you enable requires it.
That is different from claiming that no customer data ever enters or remains in Piing. The exact boundary depends on the products, integrations, staff fields and messages the merchant configures.
The three-part boundary
Stored by Piing
Piing stores operational records such as:
- accepted and blocked check-in or visit events;
- store, device, kiosk and pass configuration;
- Wallet pass instances and delivery state;
- integration destinations, event routes and delivery status;
- Alerts configuration and consent-gated engagement;
- account, administrative and audit records needed to operate and support the service.
Processed when a feature needs it
Piing may retrieve and process:
- customer identity and contact details to resolve a visit, issue a pass or show configured staff context;
- loyalty balances, tier and rewards from the provider a merchant connects;
- order and browsing history for attribution and Piing: Intelligence;
- wishlist references for staff context, conversion attribution or configured Wallet messages;
- merchant-selected Shopify customer metafields.
The data used is scoped to the workflow and source system. It is not a claim that every connected profile is copied into Piing.
Kept outside Piing
- Payment card details stay with Shopify or the payment provider used for the agreed billing route.
- Facial or biometric templates are not part of Piing recognition.
- The primary customer record remains in the merchant's commerce platform.
Product-specific write-back
Piing can write visit fields to Shopify and route typed events to enabled destinations. Piing: Intelligence writes selected outputs to app-owned Shopify customer metafields. Those outputs can then be used by Shopify Flow, Shopify segments, Klaviyo, Attentive, Shopify POS and other metafield-aware tools.
Piing: Intelligence and Piing: Alerts are Shopify-only products. A non-Shopify implementation uses a separately scoped Retail ID connection.
Security and retention
Connections to Piing services use HTTPS. Administrative access is restricted to authorised people, and merchant and integration access is scoped to the relevant store or organisation.
Retention depends on the record and product. Operational event, delivery and audit records are kept for the support, analytics and contractual periods that apply to them, then deleted or aggregated. Avoid relying on a universal retention period unless it is stated in the applicable agreement or current product documentation.
Note
Piing Technologies Ltd acts as a data processor when it handles customer data to provide the contracted service. The merchant remains controller of its customer data.
Where to read more
For a security or procurement review, contact us with the products and implementation in scope.
Related guides
Was this guide helpful?
Next guide in Security and privacy
What data Piing stores
The operational records Piing stores, the customer context it processes when needed and the sensitive data that remains outside Piing.
Still need a hand? Contact us