Privacy Policy
Pixelstack, by JimuTech · Last updated: November 12, 2026
Pixelstack ("the App") helps Shopify merchants send storefront and order conversion events to Meta (Facebook) Pixels via the Meta Conversions API. This policy explains what data the App processes, why, and how it is protected.
1. Data we store
- Merchant configuration: your shop domain, the Meta Pixel IDs and labels you configure, and your Meta Conversions API access tokens. Access tokens are encrypted at rest with AES-256-GCM.
- Delivery diagnostics: event metadata (event name, event ID, pixel ID, delivery status and error category). Purchase diagnostics can be linked to an order. Detailed logs expire after 30 days and aggregate counters after 90 days. Scheduled cleanup runs independently of merchant visits.
- Checkout matching: for up to 24 hours we match an order ID and a digest of the checkout token to its payment amount, currency and tracking permission. Browser matching data used for purchases is encrypted while awaiting delivery or retry.
- Shopify sessions: session and authorization records let the embedded app operate on your store.
2. Data sent to Meta
Depending on the event, your active pixels can receive event type, time, storefront origin, product identifiers, amount and currency, hashed customer identifiers, browser identifiers, user agent and IP address. We remove page paths, query strings and fragments from the event source URL. We do not send the checkout token to Meta.
3. Consent
Shopify’s Web Pixel framework controls when the browser pixel loads. A server-side Purchase requires both a signed payment notification and a matching checkout with permission for analytics, marketing and data sharing. A missing or denied permission prevents purchase delivery. A withdrawal received before delivery stops pending retries.
4. Access and deletion
Customers can request access or deletion through their merchant. The store owner can review Shopify data requests in Pixelstack under Support. Customer redaction removes order-linked delivery and matching records. To prevent duplicate notifications from recreating them, we keep a keyed suppression digest for 30 days. Uninstalling removes the store’s configuration and records. For information already sent to a merchant’s Meta pixel, contact the merchant about its Meta data controls.
5. Subprocessors
- Vercel Inc. — application hosting (data in transit)
- Neon Inc. — database hosting for configuration, diagnostics and short-lived matching records
- Meta Platforms, Inc. — destination of conversion events, as directed by the merchant
6. Security
Pixelstack uses HTTPS. Meta access tokens and stored purchase matching identifiers from the browser are encrypted at the application layer with AES-256-GCM.
7. Contact
For privacy questions or data requests, contact us at support@jimu-tech.com.