Wishlist Stack

Data Use Disclosure

Updated November 12, 2026

Wishlist Stack processes information needed to deliver wishlist infrastructure for Shopify merchants.

Data Accessed

Store and installation identifiers, merchant session details and authentication credentials, subscription status, Shopify customer IDs, product and variant data, selected metafields, wishlist and group metadata, quantities, notes, custom properties, sharing settings, and activity timestamps. Imports and privacy requests can contain additional merchant-provided data. Infrastructure also processes technical request and security information.

Data Use

Wishlist management, shopper authentication, public sharing, product hydration, CSV migration, aggregate merchant analytics, usage measurement, billing support, customer-data requests, reliability, and security.

Service Providers

Cookies and Monitoring

The embedded app uses PostHog analytics and error monitoring, which can use cookies or local storage. This public website does not add an advertising pixel or a site analytics script. Merchant-built storefronts have their own privacy and storage requirements.

Retention

Wishlist data is retained while the app is installed so merchants can provide the service. Uninstallation disables the installation and invalidates cached access; it does not immediately erase every record. Merchant-data cleanup is scheduled after Shopify sends its shop-redaction request, with safeguards against deleting a reinstalled store. Customer-redaction requests remove the relevant customer’s active wishlist records and related import data.

Unconfirmed import uploads have a 24-hour expiry. Confirmed imports have a seven-day retry window; source files are scheduled for deletion when an import completes, is canceled, or expires. Processing and cleanup retries can affect the time deletion finishes. Operational logs, telemetry, and managed backups follow their separate retention schedules; deletion from active app storage does not mean immediate removal from all backups.

See the Privacy Policy for the complete disclosure or contact [email protected].