PIING
Reading Security and privacyGDPR and your customers
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
- Who handles a customer request
- The GDPR webhooks Piing acts on
- Lawful basis
- What you can do yourself
Search or browse documentation
Security and privacy 3 / 6
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.
Under UK GDPR and EU GDPR, you are the data controller for your customers' data and Piing is a data processor acting on your behalf. This article explains how data subject requests are handled and what the GDPR webhooks do.
Who handles a customer request
When one of your customers exercises a right, such as access or erasure, the request comes to you as the controller. Piing assists you with the part of the request that relates to data it processes. Piing will not respond to a data subject directly without your authorisation, unless the law requires it.
Piing holds operational records for the features you enable. Customer identifiers and contact details are included where they were needed to resolve a visit, issue a pass or show staff context. Much of a customer's wider record remains in your commerce platform, where you can act on it directly.
The GDPR webhooks Piing acts on
For Shopify merchants, Piing subscribes to the three mandatory privacy webhooks. Each request is verified, logged, and acted on automatically.
Customer data request
When Shopify sends a data request for one of your customers, Piing compiles the data it holds for that customer so you can fulfil the request. For Piing: Intelligence this includes the intelligence metafields written under the app namespace, plus any pixel browsing data held for that customer. The export notes that the inference path does not store raw name, email, address or phone. Where Piing holds a customer identifier or contact detail for a visit, a Wallet pass or staff context, that record is included. The request is recorded so support can confirm it was handled.
Customer redact (erasure)
When a customer is deleted in Shopify, Piing removes the records tied to that customer across its tables. This includes check-in and event records, wallet pass instances, member links, attribution events, and any sync queue rows. Physical card records are kept as your inventory but are unlinked from the customer and set back to unassigned. Shopify removes the app metafields for that customer as part of the same flow.
Shop redact
This fires about 48 hours after the app is uninstalled. Piing wipes all data tied to your shop. See Uninstall and data deletion for the full sequence.
Note
Acknowledging a webhook is not the same as completing the work. Piing both acknowledges each request and carries out the deletion or export, and keeps an auditable record so the request can be confirmed within the required timetable.
Lawful basis
You are responsible for ensuring an appropriate lawful basis exists for processing your customers' data through Piing, such as legitimate interest or consent. The Data Processing Addendum sets out the roles, the categories of data, breach notification, and the rest of the processor obligations in full.
What you can do yourself
- Delete a customer in your platform to trigger erasure of the references Piing holds for them.
- Read or export the intelligence metafields Piing has written, directly from the customer record.
- Uninstall the app to begin removal of all shop data.
If you receive a data subject request and are not sure which part relates to Piing, contact us and we will help you scope it.
Related guides
Was this guide helpful?
Next guide in Security and privacy
AI and your order data
What Piing: Intelligence sends to the AI model. Only your order and product metadata is sent, the provider does not train on it, and retention is short.
Still need a hand? Contact us