Privacy policy
What this app can access
Tringify wrote this section from version 1.3.2 of Tringify for Facebook & Instagram: 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.
- Currencies — Read. View currency configuration and exchange rates
- Customers — Read. View customer profiles, addresses, tags, and groups
- Inventory — Read. View inventory groups, stock levels, and movements
- Markets — Read. View market configuration and tax settings
- Products — Read and write. Manage products, categories, attributes, tags, vendors, and brands
- Site verification — Read and write. Manage site verification tags shown on storefront home pages
- Preferences — Read. View storefront settings and sales channels
Storefront scripts
What the app adds to your storefront, and when it runs.
- Meta 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 meta.apps.tringify.com.
Store events the app receives
Tringify sends the app these events about the stores that install it, with only the fields the app declared.
- Currency updated
- Customer created
- Customer deleted
- Customer updated
- Domain added
- Domain removed
- Domain updated
- Exchange rates updated
- Market created
- Market deleted
- Market updated
- Product created
- Product deleted
- Product published to sales channel
- Product unpublished from sales channel
- Product updated
- Published product updated
- Stock level changed
- Storefront languages updated
- Text marketing consent changed
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@tringify.com.
Privacy policy
Tringify for Facebook & Instagram connects your store to your Meta business: it sends your products to your Meta catalog, sends shopper activity to your Meta pixel, and keeps a customer list audience up to date. Tringify builds and runs this app. This policy explains what the app keeps, why, for how long, and who else sees it.
Data we keep
| Data | Why | Kept for |
|---|---|---|
| The access Tringify gives this app to your store, encrypted | To read your products, orders and customers and receive store activity | Until you uninstall the app |
| Your Meta business's id and name, and the access token Meta gave the app, encrypted | To send products, events and audiences to your Meta business | Until you disconnect Meta or uninstall the app |
| Your settings: pixel id, catalog id, ad account and audience ids, Limited Data Use and which events are on | To send to the right Meta assets the way you chose | Until you uninstall the app |
| The Meta product codes of your products | To send each product under the same code | Until you uninstall the app |
| The ids of store events already handled | To handle each event once | Until you uninstall the app |
What goes to Meta
- Products: titles, descriptions, prices, stock, images and links.
- Shopper activity: page views, product views, carts, checkouts and purchases, sent from the shopper's browser and from our servers with the same event id. Only when the shopper allows advertising. Contact details (email, phone, name, address) are sent only hashed, and only when the shopper allows advertising data.
- Customer list audience: your customers' hashed email addresses and phone numbers, only for customers who agreed to marketing.
On checkout and order confirmation, the pixel runs in an isolated frame and only receives the checkout events; it cannot read the page.
Who we share data with
- Meta Platforms, under your agreement with Meta.
- Cloudflare hosts the app and its encrypted database.
We don't sell data and don't use it for our own advertising.
Deleting your data
Uninstalling the app removes its access to your store at once. When Tringify asks the app to delete your store's data, 48 hours after you uninstall it, the app erases everything it keeps for your store. When a customer asks to be forgotten, the app removes them from your customer list audience. Data already sent to Meta is handled by Meta under its own policies. To ask for a copy or deletion at any other time, email support-apps+meta@tringify.com.