Web Governance
What is the Web Governance script?
This article gives information about the script and where find step-by-step setup instructions to create and add it.
Not all of our features and modules require the script. The script only needs to be added to the HTML code of your website if you wish to make full use of our platform modules and features. The script can be configured in various ways to fit your needs.
For instructions on how to add the token to the HTML code of your website, visit Web Governance for Developers.
As long as it is internet-accessible, nothing needs to be installed or added to your current infrastructure for the scan to work on your website. The statistics and issue pages are prioritized by the number of views, and have a script that can be added to your Google Tag Manager.
The scan also works on password-protected or otherwise restricted web pages or documents with a couple of extra steps during setup, if this is permitted by your contract. It is your responsibility to make sure that the information in these web pages and documents is not confidential.
The script allows us to run a scan on your website to get data for the following modules and features:
For more information, visit Data Hosting and Security.
The crawler does a scan on data as it finds it. This is normally breadth-first, for example, the scan starts at level 0 (the front page of the website) and proceeds to level 1 (pages that are accessed via links from the front page), and continues in this way. XML sitemap is occasionally used if this is explicitly supplied or discovered through robots.txt.
Web Governance does a scan of your public-facing websites and does not access or store any confidential data. The only data that is stored (that may not be publicly accessible) are the names and email addresses of our customer's users, which we do not make publicly available. All data and backups that we collect is kept for at least 30 days before being permanently deleted if and when the client exits, with the exception of logs.
Unless otherwise agreed upon, the location of customer data is based on the geographical location, or branch, that your contract is with. This means that customer data for the United States offices and subsidiaries is processed and stored within the USA, customer data for Australian offices and subsidiaries is processed and stored within AU, and customer data for the European and United Kingdom offices and subsidiaries is processed and stored within the EU.
Login credentials (name, email, one-way hashed password, and data-location ID) are stored centrally in our login service, which resides in the EU.
Web Governance