Compliance
Last updated: April 27, 2026
Regulatory compliance is a top priority at TheWebstats, not an afterthought. Our platform is built anonymous-by-design (see our Privacy Policy), which is what lets us meet the spirit of major global privacy laws without needing cookie banners or consent walls.
1. European Union & UK - GDPR / UK GDPR / PECR
Our script does not collect personal data, IP addresses, or any other Personally Identifiable Information (PII), and does not set tracking cookies. This aligns with the GDPR's core principles of data minimization and privacy by design, and generally falls outside the cookie-consent requirements of the EU ePrivacy Directive (PECR in the UK), since no personal identifiers or cross-site tracking cookies are used.
2. United States - CCPA / CPRA and other state privacy laws
Because we do not collect, sell, or share personal information, there is no personal data subject to the California Consumer Privacy Act (CCPA), the CPRA, or similar state-level laws (e.g. Virginia, Colorado, Connecticut). We do not require a "Do Not Sell or Share My Personal Information" link, as no such sale or sharing ever takes place. Our services are not directed at children and are not knowingly used to collect data from children under 13 (COPPA).
3. Other Regions
For jurisdictions we haven't named explicitly - including PIPEDA (Canada), the LGPD (Brazil), Australia's Privacy Act, and others - we apply the same anonymous, minimal-data approach globally rather than maintaining different tracking behavior per region. We monitor regulatory developments and will update our practices and this page as laws evolve.
4. Your Rights & Requests
Because our analytics data is anonymized and not tied to an identifiable person, most data subject access/deletion requests won't have a personal record to act on. If you believe otherwise, or have any compliance question, reach out any time via our contact page and we'll respond promptly.
5. Related Policies
This page summarizes our regulatory posture. For the full details on what our script processes, see our Privacy Policy, and for usage terms see our Terms of Service.