AdCheckLab
for marketers
AdCheckLab
for marketers
Last updated: October 2026
Every tool on AdCheckLab, including the Pro features and Auto Fix, processes your files entirely within your browser. Your videos, images, audio and banner files are never uploaded to any server, ours or anyone else's. All processing uses native browser APIs: the HTML5 Canvas API, the File API, Web Workers and JSZip. No file data is transmitted anywhere, and there is no exception: AdCheckLab offers no service that asks you to send files, by upload or by email.
The VAST Inspector is the one tool that can make a request on your behalf. When you give it a tag URL, your browser requests that URL, and any wrapper it points to, directly from the ad server that hosts it, never through AdCheckLab. It never fires the trackers in the tag.
Auto Fix can make one kind of request too. When a banner loads a library such as GSAP or jQuery from a public CDN that the ad platform does not accept, Auto Fix downloads that same public library file from the CDN so it can be stored inside the ZIP. Only the library's address is requested; nothing from your banner is sent.
Once the page has loaded, all tools work fully offline, apart from those two requests. This makes them safe for use with NDA-protected, pre-launch, or otherwise confidential creative assets.
If you sign in, your account keeps a list of your checks: the file name, its size and dimensions, the rules used and the result. The file itself, its contents and the report stay in your browser, as described under AdCheckLab Pro and your account.
We use Google Analytics 4 (GA4, property ID: G-8100JCWEVK) to collect anonymous usage statistics: which pages were visited, how long sessions lasted, which country the request came from, and which device type was used. This data is aggregated and does not identify individual users. We also record anonymous events, such as a completed check, an export or a click on a checkout button. These events never include file names, file contents, reports, email addresses or account ids. A sign in sends one event, login or sign_up, with the method (Google or email) and nothing else, and a finished checkout sends purchase with the plan and its price. Google Analytics keeps this event data for 14 months, after which Google deletes it; visits from our own computers are filtered out and never counted.
Google Analytics uses cookies to distinguish unique sessions. For details on how Google processes this data, see Google's Privacy Policy.
To opt out of Google Analytics across all sites, you can use the Google Analytics Opt-out Browser Add-on.
We use Sentry for anonymous error monitoring. If a JavaScript error occurs in your browser while using the tools, an error report may be sent to Sentry. These reports contain the error message, stack trace, and basic browser information (browser version, OS). They do not contain your files or any personally identifiable information beyond a random session ID.
AdCheckLab shows no ads. Until 8 October 2026 some guides carried Google AdSense; it has been removed from every page, and the cookie notice now asks about analytics only. Advertising cookies a browser may still hold from that time (__gads, __gpi, _gcl_*) are deleted on your next visit. The site is funded by AdCheckLab Pro.
Every tool works without an account, except QR code downloads: the QR Code Generator previews every code for anyone and asks for a free account to download. An account keeps AdCheckLab Pro, your history of checks and your workspace on every computer you sign in on. You sign in with Google or with a link we send to your email address. There is no password.
What an account stores. Your email address. Your name, if you sign in with Google and Google shares it. The id of your Google account, so that the next Google sign in finds the same account; a sign in by email link stores no such id. When the account was created, and your active sessions, which record neither your IP address nor your browser. While an email link is open, a hash of its token; the link itself is never stored. Once you subscribe, your subscription status, plan, renewal or end date, and the ids the payment provider gives your customer record and your subscription. Your history of checks and your workspace, described below. To stop abuse, sign in links are counted for a short time per IP address, and for an hour per email address, kept as a keyed hash that does not reveal the address, and the history and workspace are limited to a number of saves per user every ten minutes. Your files, their contents and your reports are never sent to us and never stored, Pro features and Auto Fix included.
History of checks. While you are signed in, each check, Auto Fix and compression in the Banner Validator, Campaign Preflight, the Safe Zone Checker, the Ad Spec Checker and the Banner Compressor adds one entry to your account: the file or campaign name, its size in bytes, its width and height, the rules or platform it was checked against, the verdict, the number of errors and warnings, how many issues Auto Fix could repair or repaired, the number of assets in a campaign run, a short note such as the size before and after compression, and when the check finished. Never the file, never its contents and never the report. The account page lists these entries and counts them for the month. A Free account keeps the last 30 days, and older entries are deleted. A Pro account keeps them until you delete them, up to the newest 10,000, and can export them as CSV. The Keep a history of my checks switch on the account page is on for a new account; turned off, nothing new is sent. Delete history removes every entry from your account and from this browser at once, and the delete button beside an entry removes that one. When you sign in, the checks this browser kept while you were signed out are added to your account once; the account page says so.
Workspace. Your brand kits (the name you give each kit, the agency name for white label reports and a logo, which your browser makes 150 KB or smaller before it is saved), which kit is active, the naming convention you build in the UTM Builder and your default validator environment are kept with your account, so they follow you to every computer you sign in on. Free keeps one brand kit and Pro up to 20. A kit you delete on the account page is deleted from your account. Client presets are kept the same way: for each preset the client name you give it, the validator rules it uses, a naming convention, the click URL Auto Fix writes, a UTM template and which brand kit it uses. Free keeps one preset and Pro up to 20. Delivery packages, approval packs and version compares are built in your browser: their files, the SHA-256 fingerprints of your files and your client's feedback are never sent to us; only a delivery package adds a line to your history, with its name, the number of creatives and their counts, like a check.
QR codes. For a free account the account server counts the different QR codes and barcodes downloaded per calendar month, so it can allow 10. Your browser sends a one way fingerprint of each code (a SHA-256 of its content), and the server stores the account id, the month and a keyed hash of that fingerprint, never the code or what it contains, which stay in your browser. Pro codes are not counted. The record is deleted with the account.
Who processes it.
Payment. If you buy Pro, the payment is handled by Dodo Payments, the merchant of record. Dodo Payments collects your name, email address, billing address and payment details under its own privacy policy. When you start a checkout, our account server sends Dodo Payments your email address and your account id, so the subscription belongs to your account. Dodo Payments tells our account server when a subscription starts, renews, changes or ends, with the customer and subscription ids and the email address on the order. If a subscription arrives for an address that has no account here yet, the server keeps its status under a keyed fingerprint of that address, never the address itself, until an account with that verified address signs in, for at most 400 days. We use that only to turn Pro on or off for your account and to answer support requests. We never see your card details.
In your browser. Local storage keeps adcl-account, which says that this browser has signed in (so a browser that never signed in never contacts the account server), and adcl-pro, your last known plan and when it was checked. It also keeps adcl-history, the last 100 checks made in this browser, signed in or not, which is never sent anywhere while you are signed out; adcl-history-queue, checks waiting to reach your account; adcl-history-off, which remembers that the history switch is off; and adcl-workspace, this browser's copy of your workspace. A session cookie set by the account server keeps you signed in: it is strictly necessary, it cannot be read by scripts, and it is only sent to adchecklab.com. While you are signed in, your browser asks about your plan at most once an hour, fetches your workspace at most once an hour and whenever you open the account page, and Pro keeps working for 14 days when that check cannot be completed. Signing out removes the account's part of all of it from this browser: the plan, the workspace copy, the waiting checks and the checks kept while you were signed in. The brand and naming convention the tools use (adcl-brand, adcl-naming) stay in this browser, as they did before accounts.
Deleting your account. On the account page, Delete account removes the account, its sign in methods, its sessions, its history of checks and its workspace at once. While a subscription is still active you are asked to cancel it first in the payment provider's portal, so nobody keeps paying for a deleted account. The payment provider keeps its own order records as the law requires. You can also ask us to delete the account by email.
We set no tracking cookies of our own. If you sign in, the account server sets one strictly necessary session cookie to keep you signed in, as described above. The only other cookies on this site come from Google Analytics (_ga, _ga_*), and only for anonymous usage measurement. Your consent choice itself is kept in your browser's local storage under the key adcl-consent, which never leaves your device and is not sent to any server.
This site implements Google Consent Mode v2. Advertising storage is denied for everyone, always. If you are in the European Economic Area, the United Kingdom, or Switzerland, analytics storage starts denied too, and Google Analytics runs in a cookieless mode until you choose otherwise. Everywhere else it starts granted and the notice gives you a one click opt out.
You can change or withdraw your choice at any time using the Cookie settings link in the footer of every page. You can also clear or block these cookies in your browser settings.
If you are located in the European Economic Area (EEA), the United Kingdom or California, you have the right to request access to, correction of, export of, or deletion of any personal data we hold about you. Without an account we hold nothing that identifies you beyond what Google Analytics processes on our behalf. With an account, we hold the data listed under AdCheckLab Pro and your account, and you can delete it yourself on the account page.
To exercise any data rights or ask questions about this policy, contact: filip.djordjevic447@gmail.com
We may update this policy from time to time. The date at the top of this page reflects when it was last revised. Continued use of the site after a revision constitutes acceptance of the updated policy.
AdCheckLab is operated by Filip Đorđević.
Email: filip.djordjevic447@gmail.com