OwnerLoop Privacy Policy

Marketing site

When you request a playbook PDF download on www.ownerloop.app, we store the email address you submit, the book you requested, whether you opted in to occasional OwnerLoop updates, the page path where you submitted the form, and the time of the request. We use that information to provide the download and, if you opt in, to send updates about product ownership and aftermarket revenue. Unlocking a PDF is not marketing consent; the optional updates checkbox is separate.

Analytics events for the marketing site (for example Plausible or PostHog, when configured) do not include the email address you enter on the download form.

To request deletion of a marketing-site email record, contact privacy@elevixa.app.

Data we process

• Shop domain and contact email used for account setup and support
• Product and variant identifiers you map for compatibility
• Models, aliases, and finder configuration you enter
• Published storefront snapshots (public Finder publication bundles hosted as Shopify Files CDN assets, without customer account PII)
• Compatibility search tokens written as product tags on mapped catalogue products (model numbers, aliases, and SKUs) so native Shopify search can find them — catalogue data only, not customer PII
• Optional product analytics and error reporting (for example PostHog and Bugsnag) when configured for the deployed app, using shop identifiers and operational events
• Support and learning-feedback messages you submit, which may include the shop contact email
• Transactional setup emails to the shop contact address (welcome and short onboarding nudges) to help finish Finder configuration

Customer personal data

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.

Retention and deletion

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.

Contact

Questions: privacy@elevixa.app