This guide covers the complete operating flow: creating an account, adding websites, installing the snippet, configuring policies, running scanner checks, reading reports, exporting evidence and planning corporate deployments.
Start from the public registration flow, then use the dashboard as the control room for every website profile linked to the account.
Use the registration page to create a beta workspace. The platform creates the user, initial customer profile and first site onboarding path.
The dashboard shows the sites associated with the account, active integrations, consent records and platform version.
Pro accounts can onboard additional websites under the same user account without seeing or affecting other tenants.
Every site has a unique site key. The install pattern is simple, but each website remains separated by its own profile, domain rules and consent evidence.
Enter the public domain, site name, banner heading, policy details, language and consent categories.
Copy the generated JavaScript snippet into the website, preferably before the closing body tag or through the site's approved tag manager/template workflow.
Open the website, save a consent choice and confirm that a new consent record appears in the platform.
The hosted documents are generated from the website profile. They should be reviewed and completed with accurate owner, contact and processing details.
Each site can expose hosted Privacy Policy and Cookie Policy pages with version and banner metadata.
Technical, analytics and marketing categories drive the banner and the consent evidence stored by the platform.
Associate trackers and third-party services such as analytics, pixels, embeds or anti-spam tools to each website profile.
Pro focuses on the repeatable work after installation: scan, verify, export, document and keep the consent setup aligned with the website.
Run the scanner from the site dashboard to verify snippet installation, review findings and update readiness status.
Generate site-level compliance reports and export consent evidence when a client or internal process needs documentation.
The Pro add-on supports WordPress-oriented workflows such as managed scripts, embed blocking and connector-style installation.
Use this sequence for each production website before handing it to a client or internal owner.
Public institutions and large companies may require a dedicated instance on their own infrastructure rather than the shared SaaS model.
Use the corporate path when procurement, data residency, internal security review or infrastructure ownership rules make shared SaaS unsuitable.
A dedicated installation can include private deployment, hardening baseline, update workflow, backup strategy, restore testing and technical documentation.
Define hosting environment, database, TLS, mail delivery, backup retention, access policy, monitoring, update windows and responsibility boundaries before launch.