ConsentCheck
consentcheck.site
Scanning policy
ConsentCheck scanning policy
This page describes the intended operating boundaries for ConsentCheck public-web scans.
Public-web-focused scope
- ConsentCheck is intended for public pages and publicly reachable website surfaces.
- It is not intended for authenticated sessions, account areas, or private content.
- It is intended to help developers and site operators review observable consent-related behavior.
Request behavior
- ConsentCheck aims to respect robots directives where applicable.
- Requests are intended to be conservative, rate-limited, and non-aggressive.
- No credentialed access is attempted.
- No attempt is made to bypass access controls, bot protections, CAPTCHAs, or similar site protections.
- When enabled, request-signature verification support is exposed publicly at https://consentcheck.site/.well-known/http-message-signatures-directory.
Handling denials and access limits
- Blocked or denied runs are treated as access-limited outcomes.
- Access limitations are not treated as proof that a consent surface or disclosure is absent.
- The scanner is expected to cool down after denial, rate limiting, or similar access restriction signals.
Operator review path
Site operators can request review, suppression, or follow-up discussion by contacting xlprep@gmail.com.
Important disclaimers
- ConsentCheck provides informational scanning and testing support only.
- ConsentCheck does not provide legal advice.
- Scan results do not constitute legal certification or regulatory approval.
- Public-site scans may be limited by site protections, robots rules, or access restrictions.
- Inability to verify a public surface does not necessarily mean the surface is absent.