Save Consent

Save Consent

What it is

Adds a primary action button to the banner that confirms the visitor’s current choices (Access Level, Purposes, and Consent Duration).

Where to configure these settings

What happens when clicked

• Compliance by Hu-manity.co records consent (banner → app, when plan/limits allow) and stores a consent cookie in the visitor’s browser.

  From that moment until the selected duration expires, the banner and autoblocking engine apply the visitor’s choices:

  • Access Level (Private, Balanced, or Personalized) controls which categories can run.
  • Purposes you expose in the UI are respected.
  • Integrations/Consent Modes (Google, Microsoft, Facebook) receive updated signals.
  • Autoblocking allows or continues to block scripts/iframes/links according to the chosen level/purposes.

Customize it

• Button label (default): “Save my preferences”.
• Consent Duration choices: configure in the app to show one or more of the available options (see duration list below).
• Languages: label and helper text follow your language settings.

Consent Duration options

When configuring the banner’s Duration dropdown, the following options are available:

• An hour
• 1 day
• 1 week
• 1 month
• 3 months
• 6 months
• 1 year
• Infinity (the banner never re-prompts the visitor)

Both the accepted-consent duration and the rejected-consent duration use this same set of options. Configure them separately in the portal.

WordPress Admin: Cookie Expiry Settings

For unconnected (Basic/banner-only) users, the WordPress admin Settings tab > Cookie Expiry section shows two dropdowns — one for accepted-consent duration and one for rejected-consent duration — using the same 8 options listed above.

The Cookie Expiry accordion is shown only to Basic / unconnected users. For connected users (Free or Professional plan), the Cookie Expiry accordion is hidden in the WP admin. Consent duration is managed through the portal at Configuration > Consent and surfaces in the WP admin as a read-only Compliance Behavior card on the Settings tab. The card shows the current expiry value with a Manage in web app link that opens the portal in a new tab.

Default Consent Level

What it is

Sets the preselected Access Level shown on first load — before the visitor interacts. It determines the banner’s initial toggles and how autoblocking behaves until a visitor chooses and clicks Save.

Compliance by Hu-manity.co uses a three-level Access Level model:

• Private — non-essential categories OFF. Only basic operations run. This is the safest default under GDPR/ePrivacy-style rules.
• Balanced — Functional and Analytics categories ON. Marketing/personalization remains OFF.
• Personalized — all non-essential purposes enabled, including marketing and personalization. Visitors grant the highest level of data sharing.

Compliance-first default

• By design, all non-essential technologies remain blocked until the visitor gives consent.
• The only fully compliant preselection under GDPR/ePrivacy-style rules is Private — non-essential categories OFF by default.

Business-flex option (use with caution)

• You can set Balanced as the default to start with Functional + Analytics ON.
• This can improve short-term analytics continuity but may not meet strict consent-by-default expectations in many jurisdictions.

How autoblocking reacts

• Private default → non-essential tags remain blocked until the visitor consents.
• Balanced default → Functional/Analytics may run prior to an explicit click, depending on your purposes mapping and local rules. This is why risk increases.
• Personalized default → all non-essential scripts are permitted immediately on page load. Use only if your legal basis permits opt-out consent.