Support & FAQs

Get Verified means the site owner authorized CookieInspector to run automated compliance scans and display the latest scan status publicly via the badge and verification page.

They land on the public verification page showing the latest scan status, risk score, and what areas were checked.

Yes. The verification page is public so visitors can confirm the most recent status, and it only shows compliance results—never account or personal information.

Verification updates after every successful scan, so the badge always reflects the freshest status.

Yes. Removing the badge stops the public verification display, but you can still run scans from your dashboard.

Compliance Monitor automatically re-scans your sites on a schedule and alerts you when something changes—ideal for teams that ship updates frequently.

It depends on your monitoring settings and plan. You choose the scan cadence in Compliance Monitor.

Your dashboard updates the status and you receive an alert according to your notification settings.

Yes. Site changes, third-party scripts, or tag updates can introduce new issues, and monitoring helps catch regressions early.

Yes. Plans support monitoring multiple sites, with limits depending on your subscription.

AI adds explanatory insights on top of scan data to help you understand what changed and what to review next.

It summarizes key risks, highlights likely causes, and suggests what to check—based on the scan signals we detect.

No. CookieInspector provides technical compliance signals and insights, but it is not legal advice.

The risk score is a 0–100 indicator derived from scan findings and signals like pre-consent tracking and consent behavior; lower is better. Each signal carries a published weight, and cookies set by the consent platform itself or by strictly-necessary services are not counted.

Results change as your site, consent settings, or third-party scripts evolve, so fresh scans provide the newest picture.

We use a clean, automated browser session; your personal browser may look different because of extensions, cached data, or previous consent decisions.

No. CookieInspector provides informational scan results and technical insights; it does not guarantee legal compliance or replace legal advice.

The website's firewall, CDN, or bot-protection system blocked some of the scanner's requests, so the report is marked as limited and some results may be incomplete. If you manage the website you can allow the CookieInspector scanner and re-run; if you don't, there is nothing to change on your side — retry later or contact Support. See /support/waf-blocked for details.

Because a third-party request is not the same as third-party tracking. Services the page needs to work—accessibility widgets such as UserWay or accessiBe, payment processors, CAPTCHAs, fonts and your own consent platform—are listed in the report for transparency but do not lower the score. Analytics, advertising and unknown third parties still count.

Scans aim to mirror a typical visitor, but accuracy depends on what the scanner can reach; the results show what it could access at the time of testing.