Legal
Privacy policy for this website
Updated 26 September 2026
What this document covers
It describes the website legitcheck-ai.com, plus one internal tool of ours that works with a Google account and has its own section at the end. The mobile apps handle data differently and EACH has its own policy, both linked at the end of this page. We make no claims about the apps here.
What this website does not do
- It sets no cookies: checked on 26 August 2026, neither the analytics nor the site itself set a single one.
- It writes nothing to localStorage or sessionStorage.
- It has no forms, no sign-up, no login and no payments.
- It accepts no photo uploads: the photo check runs in the app, not here.
The free decoders
The four tools on this site, for Louis Vuitton date codes, Chanel serial numbers, Rolex serials and Nike style codes, run as a script inside your browser. Whatever you type is never sent anywhere and never stored: this website has no handler that could receive it.
What is processed anyway
Claiming that we collect nothing would be untrue. Loading any web page means making a request, and a request carries an IP address, a User-Agent, the page address and the referrer. Those are received by:
- Ahrefs Web Analytics, a traffic counter we added ourselves. It works without cookies.
- Cloudflare, which hosts this site and provides its own web analytics, added on the hosting side. Also without cookies.
What we see is aggregate statistics: how many people opened a page, where they came from, what device they used. What Ahrefs and Cloudflare retain on their side, and for how long, is governed by their own policies, and we will not make claims on their behalf.
The apps
Data handling in the apps is documented separately, and we do not restate those documents here.
Google Ads API (a separate internal tool)
Besides this website and the apps, we run an internal tool that works with a Google account. It is not part of this website, but it shows the same name when it signs in with Google, so we describe it here.
It is a set of scripts that run on our own computer and talk to the Google Ads API. They sign in to one Google account – ours – with a single permission, https://www.googleapis.com/auth/adwords, and they see only our own advertising account. No other person’s Google account is involved, and nothing about visitors to this website or users of the apps passes through them.
What they read. The list of advertising accounts we have access to, and reports from our own account: campaigns, budgets, impressions, clicks, spend, keywords and bids.
What they change. On our explicit command, the same scripts create and adjust campaigns, budgets, bids and keyword lists in our own advertising account. Nothing else.
Where it is kept. The access token sits in a file on our own computer and never enters a repository. The reports are saved on the same machine, in a local database and a file that feed a dashboard running there, and we keep them for as long as they are useful for analysis. We do not publish them, sell them or hand them to anyone. These scripts connect to nothing but Google’s own servers.
Questions
For anything about this page or about data handling on this website, write to us.
Terms of use
The rules for using this website are documented separately.
Changes
If the practice changes, this text changes with it and the date above is updated. We will not notify separately: the page is always accurate as of the date shown.