MarketplaceHub's use and transfer to any other app of information received from Google APIs will adhere
to the
Google API Services User Data Policy,
including the Limited Use requirements.
Google, Google Shopping, Google Merchant Center and Google Ads are trademarks of Google LLC. MarketplaceHub uses
Google's APIs but is not endorsed or certified by Google.
1. AUTHORISATION
A merchant connects their own Google Merchant Center account to MarketplaceHub through Google's
official OAuth 2.0 sign-in. The merchant signs in on Google's own pages and approves what we ask for:
-
Manage your product listings and accounts for Google Shopping
(
https://www.googleapis.com/auth/content), so we can send the merchant's products to
their Merchant Center account and read back Google's review of them.
-
Your Google account ID and email address (
openid, email),
so we can show which Google sign-in a store uses ("Connected as").
-
Only if the merchant turns on Google Ads for a store:
See, edit, create and delete your Google Ads accounts and data
(
https://www.googleapis.com/auth/adwords), so we can show the merchant the Google Ads
campaigns that sell that store's products and change a campaign's daily budget when the merchant
approves it. Google asks for this separately; the merchant can connect Merchant Center without it.
We never ask for, receive or store a Google password. A merchant can remove our access at any time at
myaccount.google.com/permissions;
the store then shows as disconnected in MarketplaceHub.
2. WHAT WE READ
- The Merchant Center accounts the merchant can manage, with their names, so they can pick one.
- The account's website and whether it is claimed, because Google shows products only for a claimed website.
- The account's data sources, to find the one MarketplaceHub made and to warn when another source may send the same products.
- Account issues that can stop products from showing, so we can tell the merchant.
- Google's review of the products MarketplaceHub sent: approved or not, and the reasons, in each country.
- The account's daily API quota, so we stay within it.
-
Only when the merchant asks to import products from Merchant Center: the products already in the
account, so they can be copied into the merchant's MarketplaceHub catalogue.
-
Only for a store the merchant gives a store code: the Google Business Profile accounts linked to the
Merchant Center account and its local selling settings, to tell the merchant whether Google can show
that shop's stock.
Only for a store the merchant turned on Google Ads for:
-
The Google Ads accounts the merchant's Google sign-in reaches directly, with their name, currency and
status, and which Merchant Center accounts each one is linked to, so the merchant can pick the one
that runs their Shopping ads.
-
In the chosen account, the Shopping and Performance Max campaigns that sell that store's products:
their name, status, dates, bidding strategy and budget, with their ad groups (and default bid) or
asset groups. We show the merchant when we last read them.
We do not read Google Ads billing, payment details, users, audiences or search terms.
3. WHAT WE WRITE
-
One data source per store, named "MarketplaceHub" with the store's country. Everything we send goes
there.
-
The merchant's own products from their MarketplaceHub catalogue: title, description, product page
link, images, price, availability, identifiers (such as GTIN, brand and MPN), category, product
attributes, and custom labels for stock level and how new a product is.
-
Only if the merchant turns on margin labels for the store: a custom label with a priority group
(
priority_a, priority_b or priority_c) worked out from the
product's cost and price in MarketplaceHub. Google receives only the group, never the cost or the
margin.
-
Only for a store the merchant gives a store code: the in-store availability and quantity of
each product for that shop, and the pickup option the merchant chose.
- A subscription to Google's product status notifications, so a change in Google's review reaches the merchant sooner.
- Changes to price and availability, and the removal of products the merchant removes.
- The removal of that data source when the merchant disconnects the store, so its products leave Google.
We do not change the merchant's other data sources, account settings, website, shipping, tax or users.
In Google Ads, the only change we make is a campaign's daily budget amount, and only after a person in the
merchant's MarketplaceHub account has approved that change. We check the budget again just before
sending it, and do not send it if it was changed in Google Ads since the approval or is shared with
other campaigns. We do not create or remove campaigns, and we do not change ads, bids, targeting,
billing or account settings.
4. HOW WE USE IT
We use Google user data only to provide the Google Merchant Center and Google Ads features the merchant
sees in MarketplaceHub: publishing their products, keeping price and availability current, showing
Google's review and any problems to fix, and, if they turned on Google Ads, showing their own campaigns
and budgets and making the budget changes they approve. In line with the Limited Use requirements:
- We do not sell Google user data, and we do not transfer it to anyone except as needed to provide these features, for security, or to comply with the law.
-
We do not use it for our own advertising, or for retargeting, personalised or interest-based ads.
Managing the merchant's own Google Ads budgets, at their request, is the only advertising use.
- We do not use it to develop, improve or train AI or machine-learning models.
-
Our staff do not read it, except with the merchant's permission (for example, to answer a support
request), for security, to comply with the law, or in aggregated form for running the service.
When a merchant asks MarketplaceHub's assistant about their listings, the assistant may read Google's
review of those listings to answer them. The assistant runs on Microsoft Azure AI, which does not use
this data to train its models (see section 6 of our Privacy Policy).
If a merchant connects their own AI assistant to MarketplaceHub, that assistant reads the same
information at the merchant's direction, under the merchant's agreement with its provider.
5. STORAGE AND RETENTION
-
Google access tokens are encrypted with a key that belongs to the merchant's own MarketplaceHub
account before they are stored, and are used only to act for that merchant's stores.
-
When a merchant disconnects a store, we delete its MarketplaceHub data source in Merchant Center and
stop calling Google for it. When no other store of theirs uses the same Google sign-in, we delete the
tokens too.
-
The Google account ID and email address are kept with the merchant's account to show which sign-in a
store used, and Google's review of a product is kept with that product. Both are deleted with the
product or the account, or on request.
-
The chosen Google Ads account and the campaigns and budgets we read are kept with the store while it
is connected. When the store is disconnected we delete them, and clear Google's values from the
store's record of ads changes; we keep only who approved which kind of change, and when.
6. STOPPING AND TAKING BACK CONTROL
-
Pause all ads on the Advertising settings page stops MarketplaceHub reading or
changing the merchant's ads at once, on every marketplace. Their campaigns keep running in Google Ads
as they are.
-
Disconnecting the store deletes its MarketplaceHub data source in Merchant Center and the Google Ads
data we kept for it, as described above.
-
Removing MarketplaceHub at
myaccount.google.com/permissions
ends our access to both Merchant Center and Google Ads.
-
A request sent to [email protected] to stop
using the merchant's Google data, or to delete it, is acted on within 3 business days.
