WebopsyRun a scan

What the scan verifies, and what it can't.

Webopsy reads a site the way a visitor, a crawler, or a regulator's first look would: the served pages, the headers, the scripts that load, the policies that are linked. That is a real and useful slice of compliance, and it is only a slice. This page lists every check, the laws each one touches, and the things no outside scan can see. It is not a compliance certification and not legal advice.

Checks and the laws they touch

Each row is something the scanner can observe from outside. The law column names the rules that make it matter; enforcement is by regulators and, for accessibility, by private suits.

CheckWhat we look atLaws and rules
Privacy policy presentThe site's own links, ranked by path and link text (so a blog tag called "privacy" never counts), a /legal hub or legal.* sub-domain, the sitemap, and common paths that must actually serve the document. JavaScript apps are rendered first. English, French, German, Spanish, Portuguese, Italian and Dutch page namesCalOPPA; GDPR Art. 13–14 / UK GDPR; PIPEDA and Quebec Law 25; CCPA/CPRA and the other US state privacy laws; Australia APP 1; LGPD; Apple App Store and Google Play; Google Analytics terms
Privacy policy contentWhether the policy names the controller, the data collected, purposes, sharing, retention, user rights, contact, children, and a date, in template or plain language. A policy in another language is noted, not judged by English phrasesGDPR Art. 13 required disclosures; CCPA/CPRA notice at collection; PIPEDA openness principle
Trackers before consentWhat a real browser does on load with no click: every network request and every cookie, matched against the data-sending calls of 18 analytics, advertising and session-recording services, with the time each one first sent data. Also scripts in the page when there is no consent banner, no consent-management platform (Cookiebot, OneTrust, Usercentrics, Didomi, CookieYes, Termly and others) and no Google Consent Mode defaulting to denied. A Consent Mode ping reporting storage denied is not counted. Session recorders (Clarity, Hotjar, FullStory, LogRocket) are named separatelyePrivacy Directive and PECR (EU/UK) opt-in consent; GDPR lawful basis. In the US, session recording without consent is the basis of wiretap claims under California Penal Code §631
Policy against the siteThe trackers the browser saw, compared with the policy text: advertising pixels when the policy never mentions advertising, a session recorder when it never mentions recording, any tracking when it mentions neither analytics nor cookies. Vendors the policy never names are listedCCPA/CPRA disclosure of sharing for cross-context behavioural advertising; GDPR Art. 13(1)(e) recipients
Cookie policyA cookie policy page or section is linkedePrivacy Directive; PECR; CNIL, ICO and other regulator guidance
"Do Not Sell or Share" linkPresent when ad or analytics trackers are used by a site likely reaching CaliforniaCCPA/CPRA §1798.135; similar opt-out rights in Colorado, Connecticut, Virginia, Texas, Oregon and other states
Terms of serviceLink or page for terms of useNot mandated everywhere; consumer-protection and e-commerce rules in the EU, UK, Canada and Australia expect stated terms for paid services
Business identity and contactA contact email or page; a legal name and address in the footer where requiredGDPR controller identity; German TMG §5 Impressum; EU e-Commerce Directive; consumer law; Stripe and app-store requirements
Newsletter or signup consentEmail capture forms with no consent or privacy language nearbyCASL (Canada); GDPR consent; CAN-SPAM; Australia Spam Act; PECR
Child-directed contentKids-oriented copy combined with data collection and no compliant noticeCOPPA (US, FTC-enforced); GDPR Art. 8; UK Age Appropriate Design Code
HTTPS and headersTLS on the final URL; Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, frame protections; mixed contentGDPR Art. 32 security; PCI DSS for payment pages; FTC "reasonable security" enforcement; state breach laws
Exposed secretsThe page and up to six JavaScript bundles it loads, where build tools inline environment variables: Stripe secret and restricted keys, OpenAI, Anthropic, AWS, GitHub, Slack and SendGrid keys, private keys, and Supabase keys whose role is service_role. Publishable keys, documentation examples, placeholders and keys inside code samples are not flagged. Values are only ever shown maskedGDPR Art. 32; provider terms; breach-notification duties if data is exposed
StackHosting from response headers (Vercel, Netlify, Cloudflare, GitHub Pages, Firebase, nginx, Apache…) and framework from the page (Next.js, Nuxt, Vite, WordPress, Webflow, Lovable…). Decides which config file the header fix is written forNot a legal check. Makes the fix paste-ready for the host you actually use.
Third partiesServices the page loads (analytics, advertising, payments, backend, chat, fonts, video, email, monitoring), recognised by host and SDK. The generated privacy policy names them as processors; the cookie banner knows which to hold backGDPR Art. 13(1)(e) recipients and Art. 28 processors; CCPA categories of third parties; ePrivacy consent for the ones that set cookies
Open databasesA real Supabase project URL or Firebase config in the page or its bundles, which needs a row-level security or rules review. The scanner never queries your databaseGDPR Art. 32; state breach laws; provider terms
Accessibilityaxe-core runs the WCAG 2.2 A and AA rules that can be tested automatically: contrast, labels, alt text, landmarks, keyboard focusADA Title III (US; the most litigated web rule, thousands of suits a year); Section 508; AODA (Ontario); European Accessibility Act; UK Equality Act 2010
AI design tellsImpeccable's detector flags patterns visitors read as generatedNot a legal check. Trust and conversion.

Jurisdictions the checks map to

Which rules apply depends on where your users are, not where you are. The scan reports what it finds; whether a rule applies to you is a question about your users and your revenue.

European UnionGDPR, ePrivacy Directive, Digital Services Act (trader information for marketplaces), European Accessibility Act.
United KingdomUK GDPR, PECR, Equality Act 2010, Age Appropriate Design Code.
United States, federalFTC Act §5 (unfair or deceptive practices), COPPA, CAN-SPAM, ADA Title III, Section 508 for government-facing sites; HIPAA, GLBA and FERPA in their sectors.
United States, statesCCPA/CPRA and CalOPPA in California; comprehensive privacy laws in force in roughly twenty states including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Delaware, New Jersey, New Hampshire, Tennessee, Minnesota and Maryland, most with revenue or volume thresholds; state breach-notification laws everywhere.
CanadaPIPEDA, Quebec Law 25, CASL, AODA in Ontario, provincial private-sector laws in BC and Alberta.
ElsewhereAustralia Privacy Act and Spam Act; Brazil LGPD; India DPDP Act; Japan APPI; South Korea PIPA; Switzerland FADP; China PIPL.
PlatformsApple App Store and Google Play require a privacy policy and data disclosures; Stripe requires business identity and terms; Google Analytics and Meta pixel terms require disclosure; PCI DSS applies to any page that handles card data.

When a site blocks automated visitors

Some sites answer bots with a challenge page (Cloudflare, DataDome, Akamai, Imperva and others) or a rate-limit response. The scanner then opens the page in a real browser that names itself as WebopsyBot, the way Google's Lighthouse does. If even that only reaches the wall, the scan stops and says so, instead of reporting the wall's missing privacy policy as yours. It never tries to get around a block, and it honours robots.txt.

What no outside scan can see

These decide compliance as much as anything above, and they live inside your company. The full report lists them as a checklist; the Done For You tier reviews them with you.

The promise, in one sentence

Webopsy finds what is observable from outside, fixes what can be fixed in code and documents, and tells you exactly what it could not see. A clean report means the visible gaps are closed, not that nothing else needs doing.