Privacy policy
What this app can access
Tringify wrote this section from version 1.3.2 of Tringify for Google: 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
- Locations — Read. View store locations and inventory addresses
- Markets — Read. View market configuration and tax settings
- Orders — Read. View orders and fulfillment orders
- Pages — Read. View storefront pages and policies
- 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.
- Google 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. Visit started, Page viewed, Product viewed, Search, Added to cart, Cart updated, Removed from cart, Added to wishlist, Removed from wishlist, Customer signed in, Customer signed up, Checkout started, Purchase, Payment method chosen, Newsletter sign-up, Contact form sent. Sent by the app’s script on your storefront.
- From Tringify’s servers — Ad data sharing. Product viewed, Added to cart, Cart updated, Customer signed up, Checkout started, Purchase, Payment method chosen, Newsletter sign-up, Contact form sent. Tringify sends them to google.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
- Order cancelled
- Order refunded
- Policy updated
- Product created
- Product deleted
- Product metafield value created
- Product metafield value deleted
- Product metafield value updated
- 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
- Variant metafield value created
- Variant metafield value deleted
- Variant metafield value 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@tringify.com.
Privacy policy
Tringify for Google connects your store to Google Merchant Center and Google Ads: it sends your products to Merchant Center, measures shopper activity with the Google tag and server-side conversions, and keeps customer match audiences 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 |
| The Google account email you connected and the refresh token Google gave the app, encrypted | To send products, conversions and audiences to your Google accounts | Until you disconnect Google or uninstall the app |
| Your settings: Merchant Center and Google Ads ids, conversion labels and actions, feed settings and which events are on | To send to the right Google accounts the way you chose | Until you uninstall the app |
| Each product's sync state and Google's review status for it | To send only what changed and show you Google's issues | Until you uninstall the app |
| Each conversion sent to Google Ads (order id, status, Google's answer) | To send each conversion once and show you failures | Until you uninstall the app |
| The Google product codes of your products, and the ids of store events already handled | To send each product under the same code and handle each event once | Until you uninstall the app |
What goes to Google
- Products: titles, descriptions, prices, stock, images and links, for each market's feed.
- Shopper activity and conversions: page views, product views, carts, checkouts and purchases, sent from the shopper's browser with the Google tag and from our servers for purchases. Only when the shopper allows it under Google's consent signals. Email and phone are sent only hashed, and only when the shopper allows advertising data.
- Customer match audiences: your customers' hashed email addresses and phone numbers, only for customers who agreed to marketing.
On checkout and order confirmation, the Google tag runs in an isolated frame and only receives the checkout events; it cannot read the page.
Who we share data with
- Google, under your agreements with Google.
- 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. Data already sent to Google is handled by Google under its own policies. To ask for a copy or deletion at any other time, email support-apps+google@tringify.com.