Binance: a fake installer and a fake job interview opened the way to a $6.3 billion theft. Who on your team can reach production from their laptop? What to check this week →

Does your site break privacy or accessibility law?

Give us the address and three answers about your business. A real browser loads your page as a first-time visitor and shows what fires before consent, whether people can say no, and what fails WCAG, mapped to the laws that apply to you. Free, no signup, under a minute.

Where is the business registered?
Where are your customers?
About the business

We open one page of your site in a browser on our server, twice, the way a visitor would, and send the report back to you. We keep no record of the address or the result. Not legal advice: what it can and cannot tell you.

What it checks

The things regulators and plaintiffs look at first

Most complaints and fines over websites come down to a handful of visible mistakes. The checker looks for exactly those.

Before consent

Advertising pixels, session recording, analytics cookies, YouTube and Maps embeds and Google Fonts that load before the visitor has chosen anything. In the EU and the UK each of those needs consent first.

A real way to say no

Whether there is a cookie notice at all, and whether Reject sits on the first layer next to Accept. France’s CNIL fined Google €150 million and Facebook €60 million in 2022 for making refusal harder than acceptance.

Global Privacy Control

A second visit with the GPC signal on. California and several other states treat it as a valid opt-out of selling or sharing data, so advertising tags should stay off.

Policy and opt-out links

A privacy policy linked from the page, a “Do Not Sell or Share” link where US privacy laws ask for one, and an Impressum for businesses in Germany and Austria.

Accessibility

The axe-core checks for WCAG 2.2 A and AA: contrast, labels, alt text, names on buttons and links, tap target size. The standard behind ADA lawsuits in the US and the European Accessibility Act.

Security basics

HTTPS, forms that post over plain HTTP, HSTS and a Content Security Policy: the minimum the GDPR’s security of processing expects for a site that collects personal data.

FAQ

Before you trust the result

How does the checker work?

It opens your page in a real Chromium browser with no cookies, the way a first-time visitor arrives, and records every request and cookie before anyone clicks the cookie notice. It looks for the notice and its buttons, the privacy and opt-out links, the security headers, and runs the axe-core accessibility checks. Then it visits once more with Global Privacy Control switched on. Your three answers decide which laws the findings are mapped to.

Is the result legal advice?

No. It is an engineer’s automated first look at one page. It tells you what the site does; whether a law applies to your business and what it requires is for your lawyer to confirm. We fix the site and give your lawyer the facts.

What can it not see?

It checks one page and does not click anything, so it cannot test whether Reject really switches tags off, what happens on checkout or behind a login, or trackers hidden behind your own domain. Automated accessibility checks find only part of the problems; keyboard and screen reader testing finds the rest. A written audit covers all of that.

Do you keep the address I check?

No. The scanner loads the page, returns the report to your browser and keeps no record of the address or the result. To stop abuse it counts checks per visitor with a salted hash of the IP address, deleted after two hours. Details in our privacy policy.

Why does it ask where my business is registered?

Because the same site breaks different rules for different businesses. An EU company is under the GDPR for all its visitors; a US company is under it only when it serves people in the EU. California’s CCPA starts at a size threshold, CalOPPA does not. The European Accessibility Act exempts microenterprises providing services. Germany and Austria require an Impressum.

Found something? We fix it

Consent that actually blocks tags, a Reject button that works, GPC honoured, and accessibility fixed in the code, not with an overlay. Fixed price, agreed before we start.

See what we fix and the prices