OwnerLoop helps Shopify merchants publish a parts and compatibility finder. We process shop, product, and configuration data required to provide that service.
The Sub-parts & Compatibility product does not store Shopify customer profiles, emails, phone numbers, or addresses.
When ownership-graph ingest is enabled for a shop (off by default; requires optional read_orders after Shopify protected-customer-data approval), OwnerLoop stores only hashed analytical owner ids and product/order GIDs needed to map a purchased variant to a compatible part. Identity (email, name, phone, address) is not written to logs, analytics events, or graph records. Shopify customer GIDs are hashed before storage so GDPR export and redaction can still find the analytical records.
Default order history is Shopify’s recent read_orders window (60 days). Older history would need read_all_orders and is not enabled.
Storefront analytics, when enabled, record only shop and product identifiers for OwnerLoop exposure and interaction events (block renders, recommendation clicks, and successful add-to-cart). Those events do not include customer names, emails, session ids, or search queries. Theme beacons respect Shopify customer privacy / cookie consent before they are sent.
A customers/data_request webhook exports the hashed graph records stored for that customer. A customers/redact webhook deletes those nodes and edges.
When you uninstall OwnerLoop, Shopify sessions are deleted immediately. Shop configuration and compatibility data stored in OwnerLoop are deleted when Shopify sends the shop/redact webhook (typically about 48 hours after uninstall).
Published Finder files on Shopify Files are deleted on a best-effort basis during shop redaction when an authenticated Admin API client is available. After uninstall, session credentials are gone, so some CDN file objects may remain in the shop's Files until removed manually or cleaned up later. Those files contain compatibility catalogue data, not customer profiles.
Questions: privacy@elevixa.app