Your Banner Speaks Three Languages and Your Site Speaks One: Consent Language Matching
Consent has to be informed, and a request written in a language the visitor does not read informs nobody. If your site serves a market in its own language, the banner, the purposes, and the settings layer must exist in that language too, at the same quality, not as a machine translated afterthought on the second layer only.
Where the mismatch usually lives
The first layer gets translated because it is visible in screenshots. The settings layer, where purposes are actually described, stays in the site's head office language, so the visitor can click accept in their own language but can only read what they accepted in another one. Purpose descriptions are the legally operative text. A translated button wrapped around untranslated purposes is consent theatre.
Detection logic creates a second mismatch. Banners that key language off browser settings while the site keys off the URL will serve a French page with a German banner to the bilingual visitor whose browser is set to a third language. Pick one source of truth, the page's own language is the defensible one, and let the banner follow the page rather than the device.
What has to be translated, in full
The full consent surface: first layer text, every purpose name and description, vendor layer labels where the framework allows, the save and reject controls, and the privacy notice section the banner links to. Partial translation fails in a specific way: the untranslated remainder is usually the part that describes sharing and advertising, which is the part a regulator or a complainant will quote.
Version records must note the language variant. When consent records store banner version, the version has to resolve to the exact text in the exact language the visitor saw, or the record cannot demonstrate what was agreed. Embedded Maps, Videos, and Widgets Set Cookies Your Banner Never Mentions sets out the record fields this requirement lands on.
Machine translation is a draft, not a control
Machine translation of legal purpose text produces errors in precisely the sentences that matter: negations, sharing verbs, retention phrases. Use it as a first draft for a human reviewer who knows the privacy vocabulary of the target language, and treat unreviewed machine output on a live banner as an unreviewed legal document, because that is what it is.
Then test as a native reader would. A reviewer reading only the banner in the target language should be able to answer three questions: what is collected, who it is shared with, and how to refuse. If the translation cannot carry those answers plainly, the consent it collects will not carry weight either.
Keep reading: Embedded Maps, Videos, and Widgets Set Cookies Your Banner Never Mentions How Long to Keep Consent Logs: Retention That Survives the Data It Covers Consent for Connected TV Apps: The Living Room Screen Nobody Audits.
Frequently asked questions
Does a consent banner legally need to match the site language?
Consent must be informed and given in response to a clear request. A banner the visitor cannot read undermines both. Regulators assess whether the information was genuinely accessible to the audience addressed, and serving a market in its language while asking consent in another is difficult to defend.
Is translating just the first banner layer enough?
No. The purposes and sharing descriptions in the settings layer are the operative information. If those stay untranslated, the visitor accepted in one language terms they could only read in another. The whole consent surface, including the linked notice section, needs the same language at the same quality.
Should banner language follow the browser or the page?
Follow the page. The page language is what the visitor chose by navigating to that version of the site, and it keeps banner, content, and notice consistent. Browser based detection regularly serves a mismatched banner to bilingual visitors on localised pages.
Can we machine translate purpose descriptions?
As a draft for human review, yes. Live and unreviewed, no. Purpose text turns on negations and sharing verbs where machine errors invert meaning. A reviewer fluent in the target language and the privacy terms should sign off the exact strings that ship.