Ticket ENG-3028

Description Of Changes

The GPC (Global Privacy Control) banner in the Privacy Center displayed raw i18n keys (exp.gpc_title, exp.gpc_description) instead of the actual translated text. This happened because the API returns null for GPC translation fields on newly created experiences, and there was no fallback to the bundled static defaults.

Code Changes

• clients/privacy-center/components/ConsentPage.tsx — In config-driven consent mode, map static GPC messages (static.gpc.*) to exp.* keys so the GPC banner can find them.
• clients/fides-js/src/lib/i18n/i18n-utils.ts — In notice-driven consent mode, fall back to static GPC messages when the API returns null for GPC translation fields.

Steps to Confirm

1. Create a Privacy Center experience with a GPC-enabled notice (OPT OUT mechanism) and a US location
2. Visit the Privacy Center with ?geolocation=US-CA&globalPrivacyControl=true
3. Navigate to Manage your consent — the GPC banner should show "Global Privacy Control detected" and the full description instead of raw keys

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required