Shopify customer data: erasure versus profile deletion
How Shopify erasure differs from deleting a customer profile, the five-day cancellation window, and the checks for payments, apps and Shop Pay.
To process a customer’s erasure request in Shopify, open their profile under Customers, then choose More actions → Erase personal data. This redacts identifying details while retaining the profile and order history. Deleting a profile is a different operation, with different restrictions.
Shopify’s current data-request guide, checked on 15 November 2026, gives merchants five days to cancel an erasure request. Open the profile’s Erasure request submitted section and select Cancel request. Submission is not evidence that every external copy has already disappeared.
Why Delete customer can be unavailable
Shopify’s customer-management guide says profile deletion cannot be undone. It is unavailable for customers associated with orders, anyone who has ever had a subscription, profiles awaiting GDPR redaction, and recipients of undelivered scheduled gift cards.
Bulk deletion removes only eligible profiles; the others remain. A completed bulk operation therefore does not mean every selected profile was deleted. Use the operation that matches the request rather than treating the two menu options as interchangeable.
Follow the data beyond the profile
Shopify says an individual erasure request is forwarded to installed apps that might hold that customer’s information. Its app guidance tells merchants to confirm deletion directly with the developer. A request being sent is different from receiving confirmation of the result.
The store request also excludes information arising from the customer’s separate relationship with Shop or Shop Pay. The Shop account guide directs customers to Shopify Privacy controls for that data. Conversely, deleting a Shop account does not erase records held by stores where the customer bought something.
Keep a record of the outcome
Our suggested working log has four entries: the request received, the action submitted, the systems still awaiting confirmation, and the outcome checked. Keep that log proportionate and access restricted; avoid creating another unnecessary copy of the customer’s personal details.
Before acting, establish which records the request concerns and who owns each follow-up. This guide describes platform controls, not a universal retention period or a determination of what your business must legally erase. Check applicable obligations with your privacy adviser when those are unclear.
16 November: a dated case study in failed erasure checks
Keystone’s 26 October 2026 incident statement, reviewed in full on 16 November, describes an automated erasure tool whose failed tasks went undetected. The company said 25,964 buyer records still contained personal information, including records retained beyond its own 180-day policy. It separately identified 12,873 unpaid checkout records in its incident response. These are Keystone’s reported record counts, not a verified count of unique affected people.
Keystone attributed the intrusion to a third-party monitoring tool and said it shortened its retention period to 90 days. It also described erasure requests submitted on 24 October and expected completion on 3 November. The statement reviewed does not confirm that completion occurred. Its historical timetable should not replace the current Shopify instructions above.
The practical lesson is to check failed tasks and outstanding confirmations, not just whether an automation ran. Keystone’s chosen retention period is not a universal rule for Shopify merchants. This case adds evidence for monitoring the outcome; it does not establish a new Shopify platform vulnerability.
More from Shopify
See all →
Before Black Friday, test what a Shopify webhook retry sends twice

