Enable GPC support for custom notices in TCF experiences

[gilluminate]

Closes ENG-513

Description Of Changes

Enable Global Privacy Control (GPC) support for custom notices in TCF experiences. Previously, GPC was completely disabled when TCF was enabled, but this change allows GPC to be applied to custom notices even in TCF contexts while still following TCF standards for purposes and vendors.

Code Changes

• Updated consent context logic to allow GPC when TCF is enabled but only for custom notices
• Enhanced RecordsList component to support rendering GPC badges for custom notices in TCF experiences
• Updated TcfPurposes component to display GPC badges for custom privacy notices but not for standard IAB purposes
• Added comprehensive test coverage for automated consent preferences with GPC support in regular and TCF experiences
• Added test coverage for consent context handling with GPC detection and query parameter support
• Updated comments to clarify that GPC can be applied to custom notices in TCF experiences

Steps to Confirm

1. Create a TCF experience with custom privacy notices that have has_gpc_flag: true (eg. "Data sales and sharing" and "Marketing")
2. Visit the demo page with GPC enabled in browser or add ?globalPrivacyControl=true query parameter
3. Verify that GPC badges appear only for custom notices, not for standard IAB TCF purposes
4. Confirm that GPC automatically opts out users from custom notices that support it
5. Verify that standard TCF behavior remains unchanged for IAB purposes and vendors

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
• 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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 2, 2025 6:40pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
fides-privacy-center	⬜️ Ignored (Inspect)			Jun 2, 2025 6:40pm

[eastandwestwind]

Great work, especially adding all those tests too!

[cypress]

fides    Run #12953

Run Properties:   Passed #12953  •  8d548edf02: Enable GPC support for custom notices in TCF experiences (#6176)

Project	fides
Branch Review	main
Run status	Passed #12953
Run duration	00m 49s
Commit	8d548edf02: Enable GPC support for custom notices in TCF experiences (#6176)
Committer	Jason Gill
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
View all changes introduced in this branch ↗︎