Privacy policy
The short version: every validator on this site runs in your browser. What you type into a validator is never sent to a server, never stored, and never seen by us.
Last updated: 8 July 2026
What this site does with the data you enter
Validatelist is a static site. Its validators — format checks, checksum calculations, regex tests — are plain JavaScript that runs entirely on your device, in your browser. When you type a VAT number, IBAN, GSTIN, Aadhaar number, PAN, or any other identifier into a validator field:
- It is not sent to any Validatelist server. This site has no backend to send it to — there is no API request, no form submission, no database.
- It is not stored anywhere: not in a cookie, not in
localStorage, not in server logs, not anywhere else. - It is not shared with any third party.
The validation logic (format matching and checksum algorithms such as mod-97, Luhn-mod-36, and Verhoeff) executes locally and the result disappears when you close or refresh the tab. SeeAbout & methodology for how the validators themselves work.
Analytics
Validatelist uses Google Analytics 4 to understand which validators are used and how visitors move through the site — aggregate, statistical usage data only. It runs with Google Consent Mode v2 set to denied by default: no analytics cookies are set and no identifiers are stored until you accept in the cookie banner. If you decline (or ignore the banner), Google Analytics operates in a cookieless mode that reports only coarse, non-identifying signals.
Crucially, the analytics script and the validators are entirely separate code paths. Google Analytics only ever sees page navigation — which page you viewed, the referrer, approximate region, and device type. It never receives anything you type into a validator field; that value is processed locally and is never pushed to the analytics layer. Google processes this data under its own terms — see theGoogle Privacy Policy. You can change your choice by clearing this site's data in your browser, and you can opt out of Google Analytics on every site with theGoogle Analytics opt-out browser add-on.
Advertising
Some pages reserve visual space for an ad slot as part of the page layout. No ad network is currently connected, and no ad-related cookies, pixels, or scripts are active. If that changes, this policy will be updated to name the network and describe what it collects before any ad code goes live.
Cookies & local storage
Validatelist sets no cookies unless you accept analytics in the consent banner. If you accept, Google Analytics sets its standard measurement cookies (such as _ga) to count returning visits. We also store one small item in localStorage —vl-consent — which simply remembers your Accept or Decline choice so the banner does not reappear on every visit. Neither the analytics cookies nor that stored choice ever contain anything you type into a validator field.
Server & hosting logs
Like effectively every website, the hosting infrastructure that serves these static files may keep standard, short-retention web server logs (such as IP address, requested URL, user agent, and timestamp) for security and abuse prevention. These logs are generated by the hosting provider for infrastructure operation, not by Validatelist application code, and never contain the contents of a validator field — that data never leaves your browser in the first place, so it cannot appear in a server log.
Children's privacy
Validatelist is a general-purpose reference tool and does not knowingly collect personal information from anyone, including children, because it does not collect personal information from anyone at all.
Changes to this policy
If this policy changes — for example, if analytics or advertising is added — the "last updated" date above will change and the update will be described in this document.
Contact
Questions about this policy, or about how a specific validator works, can be sent toadmin@validatelist.com. Validatelist is operated by the Validatelist team. See the contact page for more ways to reach us.