Ask clearly
PlannedConsent in a language the visitor reads.
A maintained translation catalogue, your own overrides where the default wording does not fit, and selection from the visitor's browser language.
Languages
- Translation catalogue
- Per-string overrides
- Browser-language selection
- Explicit fallback
How it helps
What you get with Languages
Override without forking
Change one string for your brand and keep every other translation maintained.
Framework text stays exact
Where a standard specifies wording, that text stays synchronized with the standard rather than being paraphrased.
Fallback is explicit
An unsupported language falls back to the one you nominate, not to whatever loads first.
Consent Experience
The rest of Consent Experience
Branded, accessible consent and preference experiences that belong on your site.
Banner Builder
Banner, modal and compact layouts with live preview by device and region.
Learn morePreference Center
Visitors can review, change or withdraw their choices whenever they want.
Learn moreGeo-targeting
Route visitors to the configured consent model for their region.
Learn moreAccessibility
Keyboard operation, focus management, screen-reader labels, contrast and reduced motion.
Learn moreKnow what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus