Privacy Policy
Tracking Bridge: Meta CAPI · Effective June 23, 2026
This Privacy Policy explains how Tracking Bridge: Meta CAPI (“the App”, “we”, “us”) collects, uses, shares, and protects information when a Shopify merchant (“Merchant”, “you”) installs and uses the App, and when shoppers interact with a storefront that has the App installed. The App is a server-side and browser conversion-tracking bridge that sends ecommerce events to Meta (Facebook & Instagram) via the Meta Pixel and the Meta Conversions API (CAPI).
1. Who is responsible for the data
For shopper personal data processed through the App, the Merchant is the data controller and the App operator acts as a data processor on the Merchant’s behalf. Meta is an independent controller for the advertising and measurement data it receives. Merchants are responsible for maintaining their own customer-facing privacy policy and for obtaining any consent required in their jurisdiction.
2. Information we collect
2.1 Merchant & store data
- Store domain (
.myshopify.com) and installation status. - Shopify OAuth session and offline access token used to call the Shopify Admin API on your behalf.
- Your Meta configuration: Meta Pixel (Dataset) ID, an optional Meta Test Event code, and a Meta Conversions API access token. The CAPI token is encrypted at rest (AES-256-GCM).
- Subscription and billing state (plan handle, status, trial dates) from Shopify App Pricing.
2.2 Order & attribution data
For orders placed on your storefront we process and store the following non-plaintext attribution data, keyed to the Shopify order:
- Meta browser identifiers
_fbpand_fbc(cookie values / click IDs). - Marketing parameters:
utm_source,utm_medium,utm_campaign,fbclid, andgclid. - Landing page URL, the shopper’s browser user-agent, order value, and currency.
- Marketing-consent state captured by Shopify’s Customer Privacy API.
- The status and outcome of each event we dispatch to Meta (for diagnostics and retries).
2.3 Hashed identifiers sent to Meta (not stored)
To improve ad match quality, the following customer fields are hashed (SHA-256) — in the browser or on our server — and sent directly to Meta. We do not retain these values in readable form: email, phone number, first/last name, city, state, postal code, country, and a hashed external ID derived from the order.
3. How we use information
- To send ecommerce events (PageView, ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo, and Purchase) to Meta via the Pixel and Conversions API.
- To deduplicate browser and server events using a shared event ID so conversions are not double-counted.
- To attribute orders to marketing sources and to power the App’s setup, health, and diagnostics screens.
- To operate, secure, troubleshoot, and bill for the App.
4. How information is shared
| Recipient | Data | Purpose |
|---|---|---|
| Meta Platforms, Inc. | Conversion events, hashed identifiers, _fbp/_fbc, IP & user-agent, order value | Conversion measurement, attribution, and ad optimization |
| Shopify | App configuration, order & customer-event data via official APIs | Required for the App to function on your store |
| Hosting / infrastructure (Railway) | All data above, while processed and stored | Application hosting and database storage |
We do not sell personal information. Meta’s use of data it receives is governed by Meta’s Data Policy.
5. Consent
The browser pixel only fires when the shopper has granted analytics and marketing consent, as managed by Shopify’s Customer Privacy API. When consent is denied, no personal data leaves the browser and the server-side Purchase event is suppressed for that order.
6. Data retention & deletion
- Order attribution rows are retained only as long as needed for measurement and diagnostics.
- customers/redact: when Shopify requests redaction of a specific customer, we delete the related order attribution and dispatch records.
- shop/redact: approximately 48 hours after you uninstall the App, we erase all data for your store — sessions, configuration (including the encrypted CAPI token), and all attribution records.
- customers/data_request: we surface the limited order-linked data we hold so you can respond to a shopper data request.
7. Security
Data is transmitted over HTTPS. The Meta Conversions API access token is encrypted at rest using AES-256-GCM. Customer identifiers used for matching are hashed with SHA-256 before transmission and are not stored in plaintext. Access to production systems is restricted.
8. International transfers
Data may be processed in countries other than where the shopper or Merchant is located, including the United States. By using the App you acknowledge such transfers, which are carried out consistent with applicable data protection law.
9. Your rights
Depending on your jurisdiction (e.g. GDPR or CPRA), shoppers may have rights to access, correct, delete, or restrict processing of their personal data. Such requests should be directed to the Merchant, who can use Shopify’s data request and redaction tools; we honor the resulting Shopify compliance webhooks as described in Section 6.
10. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be reflected by a revised effective date at the top of this page.
11. Contact
Questions about this policy or your data can be sent to [email protected].
Tracking Bridge: Meta CAPI — this page is provided for transparency and for the Shopify App Store listing privacy policy URL.