ChatGPT Ads Pixel & Feed · Last updated: 2026-11-16
ChatGPT Ads Pixel & Feed (the “app”) is a Shopify app provided by Lucas Albornoz, an independent software developer registered in Argentina (sole proprietor, Monotributo regime), trading as “Ecomtuc” (“we”, “us”). The app installs a Shopify web pixel and a product feed that send shopper events (such as product views, add-to-cart and purchases) and your product catalogue to the OpenAI (ChatGPT) Ads account that the merchant connects, so the merchant can measure and run ads there.
Contact for privacy requests: support@ecomtuc.com
| Category | Examples | Purpose | Retention |
|---|---|---|---|
| Shop and plan | myshopify.com domain, Shopify shop ID, Shopify plan name, Plus flag, country, currency, locale, app plan, install and uninstall dates, onboarding and demo-mode flags | Operate the app, apply plan limits, show the right messages | Until shop/redact (48 hours after uninstall); the shop is then deleted |
| Settings | Events to send, retention period (7, 30 or 90 days), feed rules, dismissed banners | Apply the merchant's choices | Until shop/redact |
| Shopify access token | Offline access token and refresh token, granted scopes. The app does not use online (per-staff) tokens, so no staff name or email is stored. | Call the Shopify Admin API (read products, manage the pixel, check the plan) | Deleted when the app is uninstalled |
| Ads account connection | Pixel ID, CAPI key, Ads API key and feed SFTP password (the keys and password are encrypted), feed ID, connection status, last error | Send events and the feed to the merchant's OpenAI Ads account | Deleted when the app is uninstalled, or when the merchant disconnects |
| Product feed records | Upload history with rejected rows (product titles and reasons), pending price/stock changes | Show feed results and push changes | Upload history until shop/redact; pending changes deleted on uninstall |
| Audit log | Time, action (e.g. settings saved, account connected, feed downloaded) and the internal ID of the Shopify session that performed it; no names or emails | Security and access records | 12 months, or until shop/redact if earlier |
| Support and request records | Privacy-webhook log: shop ID, shop domain, topic, customer and order IDs | Prove that privacy requests were handled | 1 year |
Legal basis: performance of our contract with the merchant (Art. 6(1)(b) GDPR) and our legitimate interest in operating a secure, reliable service (Art. 6(1)(f) GDPR). Subscription charges are processed by Shopify; we never receive payment card data.
| Category | Examples | Purpose | Retention |
|---|---|---|---|
| Shopper events (only after the shopper accepted analytics and marketing cookies) | Event type, time, page URL, product variant IDs and quantities, order amount and currency, order ID, ad-click IDs (oppref, obref); IP address and browser user agent while the event waits to be sent | Forward the events to the merchant's OpenAI Ads account for ad measurement | Sent and rejected events: the merchant's retention setting (7, 30 or 90 days; default 30). IP and user agent are removed once the event is sent or rejected. |
| Consent and attribution link | Checkout token, order ID, ad-click IDs, time of consent | Match a paid order to the shopper's consented session before sending a purchase event | The merchant's retention setting, at most 90 days |
| Order data from the orders/paid webhook | Order ID, total, currency, time, order status URL, purchased variant IDs and quantities. Names, emails, phones and addresses in the webhook are not stored. | Send a server-side purchase event, only if a consent record exists for that checkout | Stored as the event above |
| Pixel receipts (before an ads account is connected) | Event name and time only | Show the merchant that the pixel reaches the app | 7 days |
The app does not store customer names, email addresses, phone numbers or postal addresses. Shopper events are only collected from shoppers who accepted analytics and marketing cookies: Shopify withholds the pixel otherwise, and the pixel checks consent again before reading any data. The merchant is responsible for its cookie banner and for informing shoppers.
We process this data only to provide the app's features to the merchant. We do not sell it, do not use it for advertising or profiling of our own, and do not use it to train AI models.
| Party | Purpose | Data | Location | Safeguards |
|---|---|---|---|---|
| Fly.io, Inc. | Hosting of the app, its database and job queue | All data described on this page | USA (US East, Ashburn) | EU-U.S. Data Privacy Framework certification |
| Tigris Data, Inc. | Storage of encrypted daily database backups (30 days) | All data described above, encrypted by us before upload; Tigris holds no key to read it | USA (company seat); data in Tigris' storage regions | Tigris Data Processing Addendum (part of Tigris' service terms); EU Standard Contractual Clauses (Decision (EU) 2021/914) |
Independent recipients the merchant chooses to connect (they act under their own terms, not as our sub-processors):
| Party | Purpose | Data | Location | Safeguards |
|---|---|---|---|---|
| OpenAI (ChatGPT Ads) | Receives shopper events and the product feed for the ads account the merchant connects; events go to bzr.openai.com, the feed via api.ads.openai.com and SFTP | Shopper events (including IP address and user agent), product catalogue data (titles, descriptions, images, prices, availability) | As set by OpenAI | OpenAI's own terms with the merchant; chosen and connected by the merchant |
Shopify provides the platform the app runs in; the merchant's relationship with Shopify is governed by Shopify's own terms and privacy policy.
Data is hosted by Fly.io, Inc. in the US East region (Ashburn, Virginia, USA). The developer operates the service from Argentina, a country the European Commission recognises as providing adequate protection (Decision 2003/490/EC). Fly.io, Inc. is a US company certified under the EU-U.S. Data Privacy Framework. Encrypted database backups are stored with Tigris Data, Inc. (USA) under its Data Processing Addendum; they are encrypted before upload and Tigris holds no key to read them. Where another transfer outside the EEA is needed, we use the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914).
When the merchant uninstalls the app, the app immediately deletes the Shopify sessions (access tokens), the saved ads account credentials, queued unsent events and pending feed changes, and stops all sending. The shop record, settings, delivered event history, consent records and audit log stay for now. About 48 hours later Shopify sends shop/redact, and the app deletes the Shopify sessions, the shop record and everything linked to it (settings, events, consent records, feed rules, upload history, pixel receipts, audit log) and earlier privacy-request records. Only the shop/redact record itself (shop ID and domain) is kept for 1 year as proof of deletion. If the merchant reinstalls before shop/redact arrives, the previous record is reused.
Shopify's mandatory privacy webhooks are implemented: customers/data_request (we provide the merchant with the customer's data we hold), customers/redact (we delete that customer's data, subject only to legal retention duties stated above) and shop/redact (we delete the shop's data, except for what is listed above as retained).
The app takes no decisions with legal or similarly significant effects on shoppers. It does not profile shoppers, does not decide on prices, orders or access, and does not run any scoring. Its automated steps are technical: events are forwarded only when consent exists, and products that do not meet ad-platform feed rules (for example gift cards or missing images) are left out of the feed. The merchant can see these results in the app and change the feed rules, events and connection at any time. Any decision about advertising shoppers is made by the merchant and the ads platform they connect; shoppers should contact the merchant to contest it.
Under the GDPR you have the right to access, rectify and erase your data, to restrict or object to processing, to data portability, and to lodge a complaint with a supervisory authority. Customers of a merchant should contact the merchant (the controller) first; we support the merchant in answering the request. Merchants and their staff can contact us directly at support@ecomtuc.com. We answer within one month.
We update this policy when the app or its sub-processors change and show the date above. Material changes are announced in the app.