Prompt
I'm building a multi-brand website and need centralized consent settings
Latest observation
A good way to handle centralized consent settings for a multi-brand website is to treat consent as a shared platform service with brand-specific presentation and policy layers.
Recommended approach
1. Create a single consent core
Use one backend service or consent store that manages:
- user consent status
- consent categories
- timestamps and version of policy accepted
- region/country rules
- audit logs
- brand associations
This ensures a user’s preferences are consistent across all brands.
2. Separate branding from logic
Each brand can have its own:
- logo
- colors
- copy text
- cookie banner style
- policy links
But all of them should read/write to the same consent engine.
3. Use a shared consent identifier
If users move across brands, use a shared identifier such as:
- a first-party cookie on a parent domain
- a central auth/identity profile if users log in
- a consent token synced through your backend
If brands live on different domains, you’ll usually need:
- a centralized consent API
- server-side synchronization
- user login or a shared identity layer for reliable cross-brand persistence
4. Support brand-level overrides
Even with centralized consent, some brands may need:
- different analytics vendors
- region-specific requirements
- brand-specific legal text
- separate optional categories
So define:
- global defaults
- brand-specific overrides
- market/region rules
5. Track consent by purpose, not just yes/no
Instead of one global “accept cookies” setting, store consent by purpose:
- necessary
- analytics
- marketing
- personalization
- functional
This gives better compliance and flexibility.
6. Version everything
Store:
- consent policy version
- banner version
- date/time consent was given
- source brand
- jurisdiction
This helps with compliance audits.
Suggested architecture
Frontend (each brand)
- consent banner UI
- preference center
- calls central consent API
Central consent service
- reads/writes consent preferences
- handles geo rules
- returns brand-specific config
- stores audit trail
Data layer
- consent database
- policy/version tables
- audit logs
Identity layer
- optional login-based sync
- anonymous-to-known user mapping
Example data model
{
"userId": "abc123",
"consent": {
"necessary": true,
"analytics": false,
"marketing": true,
"personalization": false
},
"brand": "brandA",
"region": "EU",
"policyVersion": "2026.1",
"updatedAt": "2026-10-29T12:00:00Z"
}
You could also store brand overrides like:
{
"brand": "brandA",
"allowedVendors": ["google_analytics", "meta_pixel"],
"bannerTheme": "dark",
"privacyPolicyUrl": "https://brandA.com/privacy"
}
Important compliance considerations
Make sure your implementation supports:
- explicit opt-in where required
- easy withdrawal of consent
- region-specific rules like GDPR/UK GDPR/CCPA
- no non-essential tracking before consent
- proof of consent and revocation
Best practice
If you want the cleanest setup, use:
- one centralized consent platform
- brand-specific configuration
- shared user consent profile
- server-side synchronization
- audit logging
If you want, I can also help you design:
- a database schema for this,
- a consent API spec, or
- a system architecture diagram.