Privacy
This site sets no cookies. The plugin sends nothing to us or to anyone else. That is most of the policy — the rest is detail you are welcome to check.
Updated 12 November 2026 — the add-on for Google Sheets: from version 1.1 it also checks product data (prices, names, descriptions, images, brands and SKUs) in the sheet you check, and answers in German and Spanish too. 2 November 2026 — Storefront Scan: a store on Shoper is checked from the data file it makes available to Google, its home page and the start of at most 20 images. 1 November 2026 — the plugin: from version 0.3.10 the audit opens up to three of your own product pages, the way a visitor does; nothing is sent anywhere. 16 October 2026 — the add-on for Google Sheets: the permissions Google asks for when you install it from the Marketplace. 15 October 2026 — new section on the add-on for Google Sheets. 11 October 2026 — short addresses and clicks through to the plugin: we also tell people from automated clients by whether the page saw a mouse movement, a touch or a key press (the fact only); the service’s owner gets a marker so that their own visits are not counted. 30 September 2026 — the full scan with a code: what we record when a code is activated or sold, and how long the result lives; a counter of visits through short addresses (merchlint.com/o/…) and failed checks in the journal. 29 September 2026 — new section on the free catalogue audit.
Who is responsible for your data
Behind Baltano, publisher of the Merchlint plugin, stands one person, and that person is the
controller of the personal data described on this page. Everything to do with data goes to
contact@merchlint.com — questions, corrections, requests to delete something. We answer from the
same address, and it reaches the person who wrote the code. There is no data protection officer,
because the scale of processing described below does not call for one.
The plugin
Merchlint sends nothing anywhere. Not to us, not to anyone. It has no account, no sign-up, no licence check and no telemetry — not even anonymous usage counts. Nothing about your store, your catalogue, your orders or your customers reaches us or any third party, because there is no code in the plugin capable of sending it.
The one request it makes stays on your store. From version 0.3.10, an audit opens up to three
of your own product pages, at your own store’s address, the way a visitor does, to see what Google
gets from them. Those requests go to your store and nowhere else, and they carry nothing about your
store to anyone. The merchlint_open_product_pages filter turns them off.
That the plugin connects nowhere else is checked by an automated gate on every build, and it is required by the WordPress.org plugin directory guidelines, which prohibit phoning home without explicit consent.
Everything the plugin stores stays in your own database: the scan results table and the list of findings you chose to hide. Uninstalling removes both, across every site of a multisite network.
One clarification about links. From version 0.2.1, findings in the plugin link to the matching explanation on this site. Those are ordinary links: nothing is sent until you click one, and then it is your browser making the request, exactly as if you had typed the address. The link carries one parameter — your site’s language, so you land on the right version of the page. It carries no domain, no version, no identifier of any kind.
The add-on for Google Sheets
GTIN & EAN Check is an add-on for Google Sheets that checks product codes (what it does). It runs on Google’s servers, inside your spreadsheet, and there is no server of ours behind it.
- What it reads: the cells you select (or, if you select one cell, its column and the table it belongs
to); for Check product data (from version 1.1), the whole sheet you check; the spreadsheet’s locale and
your language setting — the last two only to answer in your language (English, Polish, German or Spanish). The functions
GTIN_CHECK,GTIN_VALIDandGTIN_ADD_CHECK_DIGITread only the cells you pass to them. - What it writes: when a check finds codes or product data to fix, one new sheet with the report, in the same spreadsheet. It never changes your cells.
- What it sends: nothing. The add-on makes no network requests, stores nothing outside your spreadsheet and has no analytics. Error reports are switched off, so even a crash sends us nothing.
- Permissions: the add-on itself needs one — to see and manage the spreadsheet in which you use it
(
spreadsheets.currentonly). When you install it from the Google Workspace Marketplace, Google also asks to let it see your email address and basic profile (userinfo.email,userinfo.profile): the Marketplace includes these two for every app, and the add-on does not read them. You can withdraw all of them at any time by uninstalling the add-on.
Merchlint’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
This site
No cookies are set. There is no consent banner because there is nothing to consent to. One exception belongs to the hosting provider: during a detected attack it may ask your browser to pass a check that needs a cookie (once a day) — protection against automated traffic, not tracking. A second exception does not concern visitors: the panel where the service’s owner issues full-scan codes sets a session cookie only after the owner signs in, and only on its own path, plus — again only for the owner — a site-wide marker so that the owner’s own visits are not counted in the statistics.
Analytics. We use Cloudflare Web Analytics — no cookies and no cross-site identifiers; it does not recognise people by IP address or browser. It tells us how many people visited a page, where they came from and roughly where they are (country level). It cannot identify you, and it does not follow you anywhere else. It shows data for the last 6 months. The provider is Cloudflare, Inc. (USA) — the only recipient outside the European Economic Area; it is certified under the EU-U.S. Data Privacy Framework, so the transfer relies on the European Commission’s adequacy decision of 10 July 2023.
Hosting. The site is a set of static files on a web server. Like every web server on earth, it processes request data — your IP address, the page requested, your browser’s user agent — in order to send you the page, and keeps it briefly in access logs for security and abuse prevention. There is no database, no application and no session behind these pages — with one exception, described in the section below: the store check you start yourself.
Fonts are hosted here. The typefaces come from this domain, not from Google Fonts or any other font service. Apart from the analytics beacon above, a page makes no requests to third parties — no images, scripts or stylesheets are loaded from anywhere else.
No embeds, no trackers, no advertising pixels, no chat widget. If a page ever embeds something external — a video, for instance — it will say so on the page itself.
Storefront Scan — checking a store without installing
This is the only place on this site with a running application behind it. You start it yourself by entering a store address, and it takes a dozen seconds or so — a full scan with a code up to two minutes.
What we fetch. Only public data of the store whose address you gave: its robots.txt, up to 150
products (up to 2,000 with a full-scan code) and the category list, through the same public API the
store’s own cart uses, and the headers of three product pages — to check that they open. When the API
has an image with no alternative text, we fetch the full page of at most two products to see what the
store shows in its place. When the store has no public API, we ask for the headers of its home page to
tell which platform it runs on. A store on Shoper we check instead from the product data file the
store makes available to Google through Shoper’s integration, its home page and the start (the first
bytes) of at most 20 product images. A full scan also asks for the headers of the main images of 40
products — the file size only, without downloading the images. We sign in nowhere and change nothing
in the store.
What we store, and for how long:
| What | Where | How long |
|---|---|---|
| The result: store domain, finding counts, up to five example product names per finding with links to those products, whether product pages open and — if we checked a product page — the text it shows in place of a missing image description (up to 60 characters) | a page at an address that cannot be guessed, not indexed | 7 days, then gone |
| A full-scan result (with a code): the same, but with the complete list of product names and links for every finding — to the product and to editing it in the store admin — also as a CSV file | a page at an address that cannot be guessed, not indexed | until the end of access — 30 days from activating the code, or longer if an offer with a group or partner code says so (terms, section 13); then gone |
| A journal line: date, store domain, counts or the reason the check failed, which site you came from (the site name only) and through which short address, if any | with us, never published | indefinitely |
A visit through a short address, e.g. merchlint.com/o/al1 from a listing or a post: date, which place it is, whether a person or an automated client came (by the browser’s name), a random number for that visit and — if you move the mouse, touch the screen or press a key on the page — the bare fact that this happened and after how many seconds (not what you did); automated clients that only load the page do not do this — no IP address, nothing about you | with us, never published | indefinitely |
| Counter for the check, code-activation and wrong-code limits: a hash of the IP address, not the address itself | with us | one day |
| A full-scan code activation: store domain, code, activation date and end of access, the short address you came through, ids of the full-scan results | with us, never published | indefinitely |
| A purchased code: the code, date and amount of the sale, the transaction number from the listing site — not the buyer’s name, username or email | with us | 5 years from the end of the tax year — the sales record requires it |
| A hit on the activation or wrong-code limit: date, which limit, the code — no IP address | with us, never published | indefinitely |
| Working data of the scan | with us | deleted on completion, at most one hour |
| A click through to the plugin: date, the checked store’s domain, the result id and whether an automated client (by the browser’s name) or a person with a real press of the link clicked — no IP address, nothing about who clicked | with us, never published | indefinitely |
What we do not store. Your store’s content beyond those few example names and the image text from one product page — no prices, no product descriptions, no images. Your customers’ data: the public API does not expose it, and on a product page, where signed reviews may appear, we do not go looking for it — only the image text from that page goes into the result. An email address, because we never ask for one. The IP address in the journal — everything is there except that. For a purchased code — your name, username or email address: those stay with the listing site where you bought the code, under its rules.
What we never publish: store names. If we ever show numbers from these scans, they will be aggregates without names, with the method and sample size stated. The directory holding the journal is cut off from the web, and the service checks that itself and refuses to work if it ever stops being.
Legal bases. Performing the service you asked for — Article 6(1)(b) GDPR. Limits that guard against abuse and against overloading other people’s servers — Article 6(1)(f), our legitimate interest and that of the owners of the stores being checked. The register of purchased codes — performing the contract (point (b)) and the legal duty to keep a sales record (Article 6(1)(c)).
One note about the store address itself. It is usually business data rather than personal data. With a sole trader it can nevertheless point to a particular person, so we treat it as carefully as personal data and do not publish it.
The rules for using the service are in the terms.
If you write to contact@merchlint.com, your message and address sit in a mailbox until the
conversation is done, and are kept afterwards only as long as they are useful for support history.
They are not added to any mailing list, because there is no mailing list.
Free catalogue audit
Until 15 November 2026 we review plugin exports from up to ten stores, on request; the offer is on the Polish side of this site (darmowy audyt). If you send us an export, the file reaches us because you send it — the plugin itself still sends nothing.
- What is in the file: product names, amounts and links to edit screens in your store’s admin. No data about your customers.
- Who reads it: the person who answers the email, and a small script on their computer. Apart from the mailbox, the file goes to no other service, AI tools included.
- How long we keep it: 30 days after we reply, or less if you ask. The correspondence itself is kept like any other email (section above).
- What we don’t do with it: we don’t publish the file or the store’s name. Numbers from your store go into any summary only with your separate consent.
Legal basis: performing the service you asked for — Article 6(1)(b) GDPR.
Your rights
Under the GDPR you may ask what personal data we hold about you, ask for a copy, ask for it to be
corrected or deleted, and complain to a supervisory authority. In practice the only personal data
we are likely to hold is an email conversation you started — and a transaction number, if you bought
a full-scan code. Write to contact@merchlint.com.
Controller: Baltano, publisher of Merchlint. Contact: contact@merchlint.com.
Changes to this page
If this policy changes, the date at the top of this page changes with it. Material changes will be noted in the changelog as well, so they are not made quietly.