Privacy policy
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.