# Localize the banner and honor GPC

> How default banner language, Business and Enterprise translation fetches, and Global Privacy Control defaults actually work in OptinStack.

Author: OptinStack Team  
Published: 2026-06-28  
Page: https://community.optinstack.com/articles/localize-the-banner-and-honor-gpc  
Markdown: https://community.optinstack.com/llms.md/articles/localize-the-banner-and-honor-gpc

OptinStack stores one published banner language on the site config, can fetch translated banner strings and tracker\-purpose text on eligible plans when the active page language is non\-English, and can honor the Global Privacy Control signal sent by the visitor's browser\. This article covers how the runtime picks a language, when translation requests happen, and how GPC changes consent defaults\.

## Choose the default banner language

The published site config stores one default language in presentation\.locale\.lang\. The runtime resolves the active banner language from the page html lang first and falls back to the configured language when html lang is missing\.

Translation fetches only happen for a resolved non\-English language\. The runtime normalizes locale variants to their primary language, so fr\-CA requests fr\. If the resolved language is English, no translation request is made even when the configured fallback differs\.

Business and Enterprise hostnames can publish a non\-English default language and use CDN translations for banner strings and tracker\-purpose text\. Free and Pro stay English\-only on development and custom hostnames; the platform never elevates a hostname beyond its assigned tier\.

## Honor Global Privacy Control

Respect GPC signal is on by default\. When it stays enabled and navigator\.globalPrivacyControl is true, the runtime marks GPC as active, includes gpc: true in consent sync payloads, and adjusts optional consent defaults before the banner UI renders\.

The default GPC behavior is reject\-all, which sets analytics, marketing, and preferences to false\. Business and Enterprise projects can switch GPC behavior to custom\. In custom mode, only the selected optional categories are forced to false, and any optional category not selected keeps the normal banner\-mode default\.

> **Info:** Non-English banner languages, automatic translation fetches, and custom GPC category behavior require Business or Enterprise. GPC itself is still honored on lower tiers while Respect GPC signal remains enabled.

### How does OptinStack handle Global Privacy Control?

When Respect GPC signal is enabled, navigator.globalPrivacyControl === true activates GPC handling. The default behavior rejects every optional category. On Business and Enterprise, custom behavior can reject only selected optional categories while the rest keep the banner mode default. The runtime also records that GPC was active in API payloads with gpc: true.

### How does OptinStack pick a locale?

The runtime resolves language from html lang first, then the configured banner language. It normalizes regional variants like fr-CA to fr for translation requests. English does not trigger a translation fetch, and missing translated keys fall back to the built-in English copy.