The Compliance page controls two things: the cookie-consent banner your board shows to visitors, and the legal agreements (privacy policy, terms, and so on) your board asks users to accept. To open it, click Settings at the bottom of the sidebar, then click the Compliance card.
Turn the consent banner on or off
In the Cookie consent card, use the Show the cookie-consent banner switch. It is on by default for new boards, and the card recommends keeping it on for boards with visitors in the EU/UK.
Click Save consent settings. You should see a Consent settings saved confirmation.
With the banner off, no banner is shown and all tracking code loads for every visitor. Only turn it off if you are confident your audience does not require consent.
What visitors see
With the banner on, first-time visitors get a bar at the bottom of the board: "We use cookies to run the site and, with your consent, for analytics and marketing", with three buttons:
Accept all: allows both the analytics and marketing buckets.
Reject all: allows neither. The board still works fully; only tracking is skipped.
Preferences: opens a panel with three rows: Strictly necessary (always on and not toggleable), Analytics, and Marketing, plus Save preferences.
The choice is stored in a cookie for 180 days, after which the visitor is asked again. While the banner is enabled, a Cookie settings link is added to your board's footer automatically, so visitors can change their mind at any time. If you have a published Cookie Policy agreement (see below), the banner links to it as "Learn more".
What consent gates
Consent applies to tracking code, sorted into buckets:
Analytics consent gates your Google Analytics and Tag Manager tags from Tracking settings, plus anything you paste into the Analytics bucket code box on this page.
Marketing consent gates your conversion trackers, plus anything in the Marketing bucket code box.
Your always-on head and body code injection is treated as strictly necessary and is not gated.
Use the two bucket boxes for third-party scripts that are not covered by the Tracking page: paste the full snippet (for example a heatmap tool into Analytics bucket code, or a retargeting pixel into Marketing bucket code), then click Save consent settings. Each bucket's code loads only after the visitor consents to that bucket, and loads immediately for everyone if you turn the banner off.
The built-in board analytics set no cookies and keep working regardless of the visitor's choice.
Set your DPO contact and reconsent placement
In the Data protection card, enter your Data Protection Officer email, for example
[email protected]. Leave it empty if you do not have one.Pick a Reconsent placement: Logged-in pages (the default), Everywhere, or Off. This controls where users are asked to re-accept an agreement after you publish a new version of it.
Click Save. You should see a Data-protection settings saved confirmation.
Add legal agreements
The Agreements card lists your versioned policies. To create one:
Click Add in the Agreements card.
Give it a Name (for example, Privacy Policy) and pick a Type: Terms & Conditions, Privacy Policy, Cookie Policy, Custom Agreement, or Simple Consent.
The URL slug fills itself from the name; it becomes the public page address on your board, under
/legal/.Either write the policy in Content (basic HTML is allowed and sanitized on display), or paste an External link if the policy is hosted elsewhere. When an external link is set, board links point there instead of the on-board page.
Under Ask for consent on, tick the forms that should show a checkbox for this agreement: Job seeker registration and Employer registration.
Set the three switches: Published (visible on the board and its footer), Required (users must tick the box to submit the attached forms), and Require reconsent on new versions.
Click Create agreement.
Back on the Compliance page, the agreement appears in the list with its type, version number, and attached forms. Unpublished agreements carry a Draft badge.
How reconsent works
Every agreement has a version number. When you edit the content of an agreement that has Require reconsent on new versions switched on, users who accepted the old version are asked to re-accept, in the location your Reconsent placement setting chose. Set placement to Off if you never want to re-prompt existing users. Agreements listed with a Reconsent badge have this behavior enabled.
Registration forms themselves are configured elsewhere: see the signup form builder.