TagRelay — Privacy policy

Last updated: 2026-09-26

Who we are

TagRelay is a Shopify app operated by Lukasz Szczesiak (Marketing Online - Lukasz Szczesiak). Contact: lukasz9011@gmail.com.

Roles

The merchant who installs the app is the data controller for the personal data of their store's customers. We act as a data processor and process that data only on the merchant's behalf and to provide the app's functionality.

Data we access from Shopify

• Orders (read_orders) — order data used to send purchase events to the platforms the merchant configured, and to count monthly orders for the plan limit.
• Customer events (read_customer_events) — storefront events collected by the app's web pixel.
• Theme settings (read_themes) — read only to check whether the app's theme block is enabled.
• Store information from the Shopify session (shop domain, access tokens) needed to run the app.

How customer data is processed

Each store has its own Google Tag Manager server-side container. Events from the store (web pixel events and the order webhook) are processed in that container and forwarded only to the platforms the merchant has configured in the app: Google Analytics 4, Google Ads, Meta and TikTok. We do not sell data and do not use it for any other purpose.

• Email address, phone number, first and last name and address are sent to these platforms only in SHA-256 hashed form, and only when the customer has not declined marketing consent.
• Identifiers such as the analytics client ID and advertising click IDs (for example gclid, fbclid, ttclid) are stored in cart attributes and passed to the order, so that a purchase can be attributed to the campaign that led to it.
• Consent signals are read from the Shopify Customer Privacy API and passed to the platforms as Consent Mode signals.

Customer data from orders

The Shopify orders/create webhook is delivered directly to the store's own tag server container, not to the app. From the order the container reads the customer's email address, phone number, first and last name and address, together with the order ID, value, products and click identifiers.

• The email, phone, name and address fields are hashed with SHA-256 in the store's container, in memory, before anything is sent.
• The hashed values are sent only to the platforms the merchant has configured (Meta Conversions API, Google Ads enhanced conversions, TikTok Events API), and only in line with the customer's consent. The purchase is sent to GA4 via Measurement Protocol with the Shopify order ID as the transaction ID.
• The container itself does not store these fields. However, the app's web server keeps raw request logs, which may contain the body of the order webhook, including email, phone and address. These raw logs are accessible only to the administrator (files owned by root/adm, permissions 0640), are kept for at most 14 days and are then deleted automatically.
• The operator panel builds an order register from these logs for the attribution report. Before anything is written to the panel database, the personal fields (email, phone, first name, last name, address) are removed; the database keeps event and order metadata for up to 30 days.

Data we store

• Store configuration: platform identifiers and API credentials entered by the merchant, tracking domain settings, plan and setup status.
• Technical event metadata used to monitor delivery: time, path, IP address, user agent, event name, value, click identifiers (gclid, fbc/fbp, ttclid) and order ID, and order metadata for the attribution report, without personal fields. The operator panel database keeps this for up to 30 days.
• Raw web server logs, which may contain the body of the order webhook (including email, phone and address): administrator-only access, kept for at most 14 days, then deleted automatically.

Hosting

The app and the tag server containers run on infrastructure operated by us, on servers located in the European Union (Poland).

Uninstalling and deletion

• When the app is uninstalled, the store's tag server container is stopped, the store's sessions and access tokens are deleted, and the stored web pixel and order webhook references are cleared. Platform settings are kept so that a reinstall does not require setting everything up again.
• When Shopify sends the shop/redact request (48 hours after uninstall), we delete the store's configuration in the app, including platform identifiers and credentials, and any remaining sessions, delete the store's data in the operator panel, and make sure the store's container stays stopped.
• On customers/redact we delete the delivery metadata in the operator panel linked to the listed orders and customer. customers/data_request requests are acknowledged: the app does not keep a customer database; personal fields may exist only in raw web server logs for at most 14 days. Merchants can contact us about such a request. Customer events are processed in the store's container and forwarded to the configured platforms. Data already sent to those platforms is governed by their own policies and can be deleted there by the merchant.

Your rights

Store customers should contact the merchant, who is the data controller. Merchants can contact us at lukasz9011@gmail.com with any question or request about data processed by the app.

Data processing agreement and security

Our obligations as a processor are set out in the Data Processing Agreement. Technical and organisational measures are described on the Security & data protection page.

Changes

We will update this page when the way the app processes data changes. The date at the top shows the latest version.

Back to TagRelay