Govix Scanner

Last updated: 15 August 2026

If you have found this page from your server logs, you are in the right place. This explains who we are, what our crawler does, and how to stop it or talk to us.

1. Identifying the crawler

Our crawler sends this user agent on every request:

GovixHorizonScanner/1.0 (+https://www.govix.ai/scanner/; ops@govix.ai)

It is operated by Govix, a regulatory compliance company. We do not use a generic or browser-imitating user agent, and we do not attempt to disguise our traffic.

2. What it does and why

Govix helps regulated firms keep their policies aligned with the rules that apply to them. To do that we need to know when a regulator publishes or revises a document — a handbook, a code of practice, a consultation.

The scanner fetches a small number of published pages, compares them with what we saw last time, and flags anything that has changed for a person to review. That is the whole of it. We are watching for change, not collecting content.

3. What it fetches, and how often

• Scope: a specific, short list of pages, feeds and published documents. We do not crawl whole sites and we do not follow links to discover new pages.
• Frequency: once per day per page, at most. Some pages are checked less often.
• Rate: one request at a time. We do not fetch pages in parallel from the same site.
• Method: GET only. We never submit forms, never attempt to log in, and never access anything behind a paywall or authentication.
• Failures: if a request fails we retry at most twice, with an increasing delay, then stop until the next day.

4. How it behaves

• We read robots.txt before fetching and follow what it says. If a site does not serve one, or we cannot reach it, we treat that as no restrictions — so a robots.txt we are blocked from reading cannot block us. See section 5.
• We send conditional requests where a site supports them, so an unchanged page does not need to be sent again.
• We collect no personal data. The pages we watch are published regulatory material.
• If a site refuses us, we record that and stop. We do not attempt to work around access controls, rate limits or bot protection of any kind.

5. If you would rather we did not

Blocking us in robots.txt works, provided we can reach it:

User-agent: GovixHorizonScanner
Disallow: /

To exclude only part of your site, disallow those paths instead.

One caveat worth knowing. If your site challenges or refuses automated clients, we cannot fetch your robots.txt either, and a rule written inside it will never reach us. We treat an unreadable robots.txt as no restrictions, which is the usual convention but does mean it will not stop us on its own.

If you would rather have a guarantee than a convention, email ops@govix.ai and we will stop. A person replies, so you will know it reached us — and if you have not heard back within a few working days, please try hello@govix.ai, our general contact address. If you would prefer us to fetch less often, or at a particular time of day, ask and we will change it — you do not need to block us to get that.

6. If you would rather we could

Some sites challenge or block all automated clients, including well-behaved ones and including archival crawlers. If you run such a site and are happy for us to read your published material, we can work with whatever suits you:

• A rule that admits requests carrying a header and secret value you choose.
• An allowlist entry for our user agent.
• A static outbound IP address, if you would rather allowlist by address.

Please get in touch and we will follow your preference.

7. Contact

A person reads this address and will reply.

Govix
Crawler enquiries: ops@govix.ai
General: hello@govix.ai

See also our Acceptable Use Policy and Privacy Policy.