Privacy policy
What this app can access
Tringify wrote this section from version 1.1.0 of Tringify for Fake Ads: it lists what merchants allow the app to do when they install it. It changes when a new version of the app changes that access. The rest of this policy is written by the app's developer.
Store API access
Server-to-server access to store resources.
- Customers — Read. View customer profiles, addresses, tags, and groups
- Products — Read and write. Manage products, categories, attributes, tags, vendors, and brands
- Preferences — Read and write. Manage storefront settings and sales channels
Storefront scripts
What the app adds to your storefront, and when it runs.
- Fake Ads customer activity — Runs on your storefront pages. The app’s script runs in the page so ad and analytics tools can measure visits. Only after the shopper allows advertising.
Shopper activity
Store events the app receives, and the consent each one needs.
- From shoppers’ browsers — Advertising. Page viewed, Product viewed, Search, Added to cart, Added to wishlist, Customer signed up, Checkout started, Purchase, Newsletter sign-up, Contact form sent, Payment method chosen. Sent by the app’s script on your storefront.
- From Tringify’s servers — Ad data sharing. Page viewed, Product viewed, Search, Added to cart, Added to wishlist, Customer signed up, Checkout started, Purchase, Newsletter sign-up, Contact form sent, Payment method chosen. Tringify sends them to fakeads-app.tringify.store.
Store events the app receives
Tringify sends the app these events about the stores that install it, with only the fields the app declared.
- Product created
- Product deleted
- Product published to sales channel
- Product unpublished from sales channel
- Product updated
- Published product updated
Data deletion
Because the app can read customer data, Tringify forwards every shopper's request for a copy of their data and every erasure to the app, and the app must answer them.
48 hours after a store uninstalls the app (or at once when the store is deleted), Tringify asks the app to delete the data it holds for that store.
Developer: Tringify. Contact: support-apps+fakeads@tringify.com.
Privacy policy — Tringify for Fake Ads
Tringify for Fake Ads connects your store to Fake Ads, a demo advertising platform operated by Tringify for testing. No ads run and no real money moves.
What the app keeps
- Your store's access token for this app, encrypted.
- The Fake Ads access token for the account you connect, encrypted, and the names and ids of the ad account, pixel and catalog you choose.
- Your settings: which events are sent, Limited Data Use, and the test event code.
- Daily counts of the server events sent per event type (kept 30 days), and the last 50 problems that occurred while sending.
The app does not keep shopper data. Events pass through it on their way to Fake Ads and are not stored.
What the app shares with Fake Ads
- From the shopper's browser (the pixel): the events the shopper triggers, such as page and product views, carts, checkouts and orders, with the products by their catalog code. The pixel runs only when the shopper allows advertising.
- From the server (Conversions API): the same events, sent only when the shopper allows advertising data. Each event carries the shopper's browser identifier, IP address and browser, the ad click they came from, and their contact details, hashed (SHA-256) by Tringify before the app receives them.
- Your product feed: the products you publish to Fake Ads, which Fake Ads fetches from your store.
Deletion
- Disconnecting stops the pixel, server events and product feed, and deletes the Fake Ads token.
- Uninstalling deletes both tokens.
- Erasure: all remaining data for your store is deleted when Tringify sends the store data erasure request after the uninstall.
Data Fake Ads has received stays there under Fake Ads' own retention: events 30 days, reports 90 days.