Compliance Check FAQ

Answers to our most frequent questions about Osano Compliance Check:

Q: Does Compliance Check scan all pages of my website?

A: Current checks are relevant to either the first page load experience (consent banner loading, GPC) or the Privacy Policy page (existence, date, and DSAR methods). As such, we do not scan every page of a website at this current time.   

Q: Does Osano's CMP or DSAR product need to be on my website to use Compliance Check?

A: No, the product is agnostic to the privacy platform used and does not require any scripts or code from Osano be on the website in order for the scan to happen.  

Q: How frequently will my site get scanned?

A: Sites are scanned on a default frequency determined by your Osano plan.

• Basic plans get 1 scan per site per month.
• Pro plans get 1 scan per site per day. Pro plan customers can update scan frequency to be less than 1 per day as well, if they wish. The options are daily, weekly, monthly.
• Both plans may also set a domain to not scan on a default frequency (the ’none’ option in the Scan Frequency dropdown), if you wish to pause scans for any specific reason. While set to 'None' you will be able to trigger a manual scan via the ‘New Scan’ button in the site details view, if your account has not used the allotted count of scans for that particular time period (eg. basic plan gets 1 per month per site, if not scanned for 32 days when set to ‘none’, 1 scan is available to trigger manually).

Q: What is the full list of regions we currently support scanning from?

A: Currently we support scanning from California, United States. We will be adding more regions in the upcoming months as we expand our functionality.  

Q: What is the full list of laws we check during scans?

A: CCPA/CPRA, and CIPA. We will be adding more laws in the upcoming months as we expand our functionality.

Q: I found an issue with a scan run on my site, what do I do?

A: Please report any issues through the Help Center within the Osano web application.

Q: My website’s firewall is blocking Compliance Check scans. How do I fix it?

A: You can allow Osano’s scans through your firewall in one of two ways:

If you use Cloudflare, turn on Verified bots in Super Bot Fight Mode. Cloudflare will recognize Osano’s scans automatically. If you use another firewall (such as AWS WAF) or want a narrower exception, set up a custom header. Go to Compliance Check → Custom headers, create a header group, assign it to your domain, and add a firewall rule that allows requests carrying that exact header value.

After saving your changes, run a new scan to confirm it goes through. Step-by-step instructions are at developers.osano.com/compliance-check/verified-bots.