Privacy policy

Last updated 2 October 2026. Feedwatch is operated by Saliga Software.

What you are asked to allow

Shopify shows you two permissions when you install Feedwatch. This is what they say, and what each one is for.

• View and edit store data — Products. Reading your products is the entire point: the checks run over your catalog. Writing is what the fixes do, and only to the fields named below.
• View staff and contributor data — Store owner: name, email address, phone number, physical address. Feedwatch uses one field of this: the store owner’s email address, so the weekly summary has somewhere to go. It never reads the phone number or the physical address, and reads nothing about staff or contributors beyond the store owner’s contact address that Shopify returns. This permission cannot currently be asked for any more narrowly than Shopify words it.

What Feedwatch reads from your catalog

For each active product: the title, the Shopify product ID, the status, whether it is a gift card, the product category, the product type, the vendor, the description, and whether it has an image; and for each variant its name, SKU, barcode and price. Feedwatch does not read stock levels.

What Feedwatch cannot read

Feedwatch does not request access to orders, customers, buyers, payments, shipping addresses, or cost and profit data. This is not a promise about our intentions — Shopify enforces it. The app holds no permission for that data, so the API refuses those requests.

It has no connection to Meta, TikTok or any ad account. It works from data Shopify already holds, and connects to Google only if you connect your Google Merchant Center account yourself, as described below.

Google Merchant Center, if you connect it

Connecting is optional, and starts only when you press Connect Google Merchant Center in the app’s Settings. Google then asks you to let Feedwatch use its Merchant Center permission. Google offers that permission only as read and write; Feedwatch only reads with it, and never creates, changes or deletes anything in your Merchant Center account.

What Feedwatch reads from Google: the Merchant Center accounts your Google account can reach, so you can choose one; and, for the account you choose, each product’s ID and title, its status for each Google surface and country, and the issues Google reports for it, in Google’s own words. It reads this when you connect and once a night after that, to show you Google’s verdict in the app and in the weekly summary.

What Feedwatch keeps: the access Google issues, as a token encrypted on our server; the chosen account’s ID and name; the counts from each nightly read, for two weeks; and, for the latest read only, each product Google disapproved, limited or reported an issue for, with Google’s status and issues.

Google is the source of this data, not a processor of yours: Feedwatch sends Google nothing about your store beyond the requests for it. Nobody at Feedwatch reads it except to fix a problem you report, or where the law requires it, and it is not used for anything but showing it to you.

Disconnecting in Settings deletes the token and everything Feedwatch read from Merchant Center at once, and asks Google to revoke the access. Uninstalling Feedwatch deletes it too. You can also remove Feedwatch’s access at any time from your Google Account’s security settings.

Who Google data is shared with: no one. Feedwatch does not share, sell, rent, transfer or disclose the data it receives from Google to any third party — not to advertisers, data brokers or AI providers; the AI services listed under “Where your data is held” never receive it. It is not used to train or improve any AI or machine-learning model. It is shown to you in the app and, as one number (how many of your products Google disapproved that week), in the weekly summary sent to your own email address through Resend, our email delivery service. It is stored on our own server, which Hetzner Online GmbH hosts for us in Germany. Feedwatch would disclose it only if the law required it.

How it is protected: every connection to Feedwatch, and from Feedwatch to Google, is encrypted with HTTPS (TLS 1.2 or later). The Google access token is encrypted with AES-256-GCM before it is stored, with a key kept outside the database. The database is not reachable from the internet: only the app on the same server can connect to it, and access to the server is limited to Feedwatch’s operator. The nightly database backup is encrypted before it leaves the server. Feedwatch only reads from Google, keeps only what is listed above, and deletes it as described when you disconnect or uninstall.

Feedwatch’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What Feedwatch writes

Only four fields: a variant’s barcode, and a product’s category, brand and description. Feedwatch writes them when you press a fix in the app, or — for categories only — each night, if you have switched automatic apply on. A description is only ever written to a product with no description text, and it is the text you saved. Feedwatch never changes prices, inventory, titles or publication status, and never replaces a description a product already has.

What Feedwatch stores

• Your store’s myshopify.com domain, its currency, and the date you installed.
• The Shopify access token that lets the app read your catalog. It is stored on our server and never sent anywhere else.
• Scan results: which products are missing which piece of data, and the lowest price each of those products is listed at, taken from your own prices.
• The email address the weekly summary goes to — the store owner’s address from Shopify, or another one if you type it into the app.
• Whether each weekly summary reached that address — delivered, bounced, or reported as spam — as Resend reports it back.
• Your subscription status, cached from Shopify for a few minutes at a time.
• For each description you save from the app: the text, and what the product’s description held before, so the save can be undone.
• For each description draft Feedwatch writes: which product, when, and how much of the writing service it used. Not the draft itself.
• If you connect Google Merchant Center: the encrypted access token, the account you chose, and what Google reported about your products, as described above.
• When the app was first and last opened from your Shopify admin, so we can tell a store that uses Feedwatch from one that only receives the email.

Email

Feedwatch sends the weekly summary through Resend, an email delivery provider. The message contains product titles and list prices from your own catalog. Every message carries an unsubscribe link, and you can also turn the summary off inside the app.

If a summary bounces because the address cannot receive mail, Feedwatch stops sending to that address until you save one in the app. If a summary is reported as spam, Feedwatch stops sending to your store altogether.

Free store check

When someone uses the free store check at feedwatch.co/check, Feedwatch reads that store’s public product catalog and nothing else: no login, and nothing from the store’s admin.

• It stores the store’s address, the counts it found, and up to five example product links for each check, for 30 days.
• It keeps a log of checks and of clicks on the install button: the store’s address, what happened and when, kept for 180 days. Nothing about the person who ran the check is in it. If the link that brought you to the check carried a campaign tag — from an ad, for example — the log also notes that the page was opened from that link, and the tag is kept with the log entry.
• The visitor’s IP address is held only in the server’s memory, briefly, to limit how many checks one address can run. It is not written to the database. Like every request to this site, the request also appears in the web server’s access log.

None of this is shared with anyone.

Visits to this website

feedwatch.co uses Cloudflare Web Analytics to count page views. It sets no cookies, and it collects no personal data and builds no profile of visitors from their IP address.

Where your data is held

• Our server and database, hosted with Hetzner Online GmbH in Germany.
• Resend, for delivering the weekly summary email.
• TypeSafe, for suggesting product categories and for checking description drafts. For a category, it is sent a product’s title, type and brand and the start of its description. For a draft, it is sent the draft and the product details the draft was written from.
• Groq, for writing a description draft when you ask for one. It is sent a product’s title, brand, type, category and variant names, any description text it already has, and the language your Shopify admin is set to.

None of this includes anything about your customers: Feedwatch has no access to customer data to send. What these services do with what they receive is governed by their own terms.

Feedwatch does not sell your data, does not share it with advertisers, and does not use it to train anything.

How long it is kept

Scan history is pruned automatically: only the most recent scans of your catalog are kept, and older ones are deleted along with their findings.

When you uninstall Feedwatch, everything the app holds about your store is deleted immediately, and deleted again when Shopify sends its confirmation 48 hours later. Nothing is retained for analytics beyond the encrypted nightly database snapshot, which ages out on its own schedule.

Customer data requests

Feedwatch answers Shopify’s mandatory data request and erasure webhooks. In every case the answer is the same: the app holds no data about your customers, so there is nothing to return and nothing to erase.

Contact

Questions about this policy, or about what the app holds for your store: salih@feedwatch.co. You will get a reply within one business day, from the person who wrote the code.