Skip to content
  • Everything we checkThe four areas, each test and the plan it needs.
  • How it worksWhat a scan does, step by step.
  • Every rule we checkEach rule, with the law behind it.
  • Sample reportA real report, name removed.
  • Trackers we detect41 vendors and the consent tools we know.
  • AccuracyHand-checked runs, misses included.
  • AgenciesProspect scans and client reports.
  • Online storesShops selling to the EU and UK.
  • SaaS companiesSign-up flows and product sites.
  • PublishersAd-funded news and content sites.
  • Shopify storesTheme apps and Shopify’s own banner.
  • WooCommerce storesPlugins and WordPress consent tools.
Pricing
  • StudyCookie consent on 168 European shops.
  • Case studiesReal scans: banner versus trackers.
  • Free toolsQuick checks, no signup.
  • GuidesCookie banners, dark patterns, the withdrawal button.
  • BlogNotes from the scanner and the rules.
  • Compareuntick next to other scanners.
Sign inStart free
What we check
  • Everything we check
  • How it works
  • Every rule we check
  • Sample report
  • Trackers we detect
  • Accuracy
For agencies
  • Agencies
  • Online stores
  • SaaS companies
  • Publishers
  • Shopify stores
  • WooCommerce stores
Pricing
Study
  • Study
  • Case studies
  • Free tools
  • Guides
  • Blog
  • Compare
Sign in

Cookie consent·Dark patterns·Withdrawal·Accessibility

Privacy policyTermsRefundsSecurity
On this page
  1. How scans are isolated
  2. How your account is protected
  3. Report a vulnerability

Last reviewed 27 October 2026 · report problems to hello@untick.io

Security

In short
  • Every scan runs in a fresh browser profile.
  • Scans can only reach public addresses.
  • Passwords and API tokens are stored hashed.
  • Report a problem by email; we reply within 2 working days.

Each scan runs in its own fresh browser on Cloudflare, can only reach public addresses, and never signs in to your shop unless you give it a test login. Report a problem to us by email and we’ll answer within 2 working days.

How scans are isolated

  • Every visitor in a scan is a fresh browser profile: no cookies, storage or earlier choices, thrown away afterwards.
  • Every address is checked before it loads, so a scan can’t be pointed at a private network or our own systems.
  • Service workers and downloads are switched off in the scan browser.
  • We only visit public pages, unless you add a login for a test account so we can check pages behind it.

How your account is protected

  • Passwords are hashed, never stored as text. Session cookies are HTTP-only and secure.
  • Payments go through Paddle, our Merchant of Record. We never see card numbers.
  • API tokens are stored hashed, and you can turn them off in Settings at any time.
  • What we keep and for how long is in the privacy policy. Deleting your account deletes your sites, scans and screenshots straight away.

Report a vulnerability

Email hello@untick.io with the steps to reproduce. Please don’t access other people’s data or disrupt the service while testing. We’ll reply within 2 working days and keep you posted until it’s fixed. Our security.txt has the same details.

Checks your cookie banner and accessibility the way a visitor would, plus dark patterns and the EU withdrawal button.

Start freehello@untick.io

Product

What we checkPricingSample reportHow a scan worksAccuracyAPI & CI checks

Features

Change watchProspect scannerEvidence recordFix kitTeam seats30-day price checkLogged-in pages

Resources

Study: 168 shopsCase studiesGuidesFree toolsBlogCompare

For

Online storesSaaS companiesAgenciesPublishersShopify storesWooCommerce stores

Company

AboutSupportSecurityPrivacyTermsRefunds
Cookie consentDark patternsShop rulesAccessibilityEvery rule we check

untick

© 2026 untick · Operated by Mahmoud Shayeb · Payments by Paddle.com (Merchant of Record) · Automated checks, not legal advice.llms.txt