Privacy policy
FeedGuard audits product data so that shopping platforms can list it. This page says, in plain English, exactly what we collect, what we do with it, what we never do, and how to get it deleted. It describes the app as it is built today, not as we might build it later. Last updated 1 October 2026.
The short version. We read the product data you point us at and store the audit so the report keeps working. We never write to your store. We never sell your data. There are no advertising or analytics trackers on this site. If you leave your email for weekly re-audits, we send you that one email a week and stop the moment you ask. Anything you want removed, email feedguard-0764c4b8@ctomail.io.
Who we are
FeedGuard is a product-data audit tool. You point it at an online store — a store domain, a product feed URL, an uploaded CSV, or a Shopify store connected with the FeedGuard app — and it checks the products against the requirements Google and Meta enforce for Shopping listings, explains what fails, and hands back corrected data to download. The free audit needs no account.
For anything on this page, write to feedguard-0764c4b8@ctomail.io.
When you run the free audit, we collect…
- What you submit. The store domain or feed URL you type in, or the name of the CSV file you upload. That value is stored against the audit so the report can say what it audited and so a weekly re-audit can fetch the same source again.
- The product data that source contains. If you give us a store domain we read the catalogue the storefront publishes publicly (its product list, and the store's own declared currency). If you give us a feed URL or upload a file we read that instead. That is product data: titles, descriptions, brands, prices, stock, identifiers, categories, image addresses. We also fetch your product images and pages from your own site to check that they load.
- The audit itself. The score, which requirements failed on which product, the corrected CSV we generate, and when it ran. Audits are stored in our own database.
- Your email address — only if you type it in. It is optional, and it is only asked for on a report page, to send you the weekly re-audit. Nothing else is collected and there is no form field anywhere else that asks for it.
Report pages are public links: anyone who has the address can open the report and download the corrected CSV. The links carry a random id and are not listed or linked anywhere, but treat one as shareable — it is designed to be sent to a colleague or an agency. Ask us and we will delete a report.
When you connect the Shopify app, we collect…
- The store and the permission you granted. Your store's
*.myshopify.comdomain, the scopes Shopify reports back to us (the app asks forread_productsand nothing else), your shop's currency setting, when you installed it, and what our syncs did — when one ran, whether it finished, which audit it produced. - Your product catalogue, read through Shopify's Admin API with that read-only permission: the same product data listed above, plus the variant barcode, which a store's public catalogue does not publish. It is stored as the audit record described above.
- The access and refresh tokens Shopify issues us. These are stored as AES-256-GCM encrypted ciphertext, never in plaintext, and they are never shown on any page, in any email or in any log. The encryption key lives in the deployment's secret settings, not in the code.
What we do not receive from the app: your customers, their orders, their addresses, your payments, your staff accounts, or anything else outside the product catalogue. The app never asks Shopify for a customer or order scope, so Shopify never sends us that data, and no table in our database has a customer name, email, address or order in it.
What we do with it
- Run the audit and show you the score, the failing requirements and the exact fields at fault.
- Produce the corrected CSV and publish the report on its link.
- If you left your email: re-run the same audit every week and email you the short summary — the score before and after, and what got worse. One email a week, nothing else.
- Keep a connected Shopify store working: renew the access token when it expires, using the refresh token, without you having to do anything.
- Keep the service running and fix faults — we log errors (for example, that a sync failed for a store domain), never tokens and never anything about a store's customers.
That is the whole list. We do not build advertising profiles, we do not enrich your data with other sources, and we do not use your catalogue to train anything.
What we never do
- We never write to your store. Not product edits, not prices, not settings. The Shopify app asks for read-only product access, and there is no code path in FeedGuard that sends a write, update or delete to Shopify.
- We never sell, rent or trade your data, and we don't share it with anyone except the email provider that delivers the weekly re-audit you asked for.
- No analytics, no advertising, no tracking. This site sets no cookies and loads no third-party scripts — no Google Analytics, no advertising pixels, no session recording. The only third party involved anywhere is our email provider (Knock), which receives the address and the contents of a weekly re-audit email in order to send it.
- We don't store your customers' data, because we never ask for it.
- We don't invent product data. Where a fix would mean guessing (a GTIN, a brand, a category), the report asks you for it instead.
How long we keep things, and how to get them deleted
- Audits and report links: kept so the link keeps working and so each weekly re-audit can compare against the previous score. There is no automatic expiry date yet. Ask us and a report, its data and its link are deleted.
- Email addresses: kept for as long as you are on the weekly list. Reply to any re-audit email, or write to us, and we remove the address and stop sending. There is no unsubscribe link in the email yet — a reply is how you stop it, and we act on it by hand.
- Tips-and-updates signups: if you enter your email in the “Want help fixing these?” section of a report, we store that email (and your name only if you type one) so we can send tips and updates from DigitalDownloadsTMT — the exact consent text shown next to the form is stored with it. The list is kept until you ask us to remove you: write to support@digitaldownloadstmt.com and we delete the entry. We do not sell or share the list, and signing up is never required to use any part of FeedGuard.
- A connected Shopify store: the connection record and its encrypted tokens are kept while the app is installed. When the store removes the app, Shopify revokes the tokens immediately (they stop working at that moment), and Shopify then asks us to erase the shop — about 48 hours later — at which point we delete the store's connection record including both tokens, every audit we produced for that store, any email address stored against those audits, and any pending connection request. You can also ask us to do this the moment you uninstall, without waiting.
- Pending connection requests (OAuth nonces): deleted as soon as they are used, and swept out within a day either way.
- A record of Shopify's data requests: we keep the topic, the store domain, Shopify's delivery id and our outcome for each mandatory webhook we handle, so we can prove we answered it and recognise a repeat delivery. We do not keep the contents of those requests, which for the customer topics can include a customer's email address.
To have anything deleted, email feedguard-0764c4b8@ctomail.io from the address concerned (or tell us the store domain the audit was for). We answer within 30 days, usually much sooner.
Security
Everything travels over HTTPS. Shopify access and refresh tokens are encrypted with AES-256-GCM before they are stored, and the key is held in the deployment's secret settings rather than in the code. Tokens are never displayed in the app, printed in an email or written to a log. Corrections we make to your catalogue are generated as a file for you to download — we never push them into your store ourselves.
Your rights
If you are in the UK, the EEA, California or anywhere with similar rules, you can ask us for a copy of what we hold about you, ask us to correct it, delete it, or restrict what we do with it, and you can object to the weekly emails. Write to feedguard-0764c4b8@ctomail.io and we will do it. We only hold what is listed on this page, so the answer will be short: the audits we ran on the store you name, and your email address if you left one.
If you are a shopper, not a store owner, this is worth knowing: FeedGuard has no record of you. We audit product listings, so a store's customers never appear in our data at all. If a store using FeedGuard tells you otherwise, write to us and we will confirm what we do and do not hold.
Requests that come from Shopify
Shopify requires every app that lists in its App Store to handle three privacy requests, and FeedGuard does:
- A customer asks a store for their data (
customers/data_request): we record the request and confirm we hold no customer data. There is nothing to hand over, and we say so. - A customer asks a store to erase them (
customers/redact): same answer — we hold no customer data about them to erase. - A store removes the app (
shop/redact): we delete that store's connection record and encrypted tokens, the audits we produced for it, and any email address stored against those audits. This is a real deletion from the database, not an acknowledgement.
Every one of these requests is verified against Shopify's signature before anything happens, so a forged request cannot delete anything.
Changes to this policy
If what the app does changes, this page changes with it, and the date at the top moves. Nothing here is aspirational: every statement describes behaviour that is in the shipped code today.
Last updated 1 October 2026.