Feature
Preference Centre
Give people one place to review and update their non-cookie consent preferences.
People may need to revisit choices made in different product, service, or communication journeys. Support teams may handle routine preference changes manually.
What Preference Centre does
A preference centre is a customer-facing view of non-cookie preferences and available choices.
People may need to revisit choices made in different product, service, or communication journeys.
It retrieves relevant preferences, explains choices, and submits authorized updates.
Why Preference Centre matters
People may need to revisit choices made in different product, service, or communication journeys.
Support teams may handle routine preference changes manually.
Preferences are scattered across individual journeys with no central review point.
How Preference Centre works
- Identify the person or account.
- Load relevant preference categories.
- Display current choices and explanations.
- Accept selected updates.
- Reflect the updated state in connected workflows.
Key capabilities
- Central preference review
- Non-cookie preference categories
- Current-choice display
- Customer initiated updates
- Linked preference state
Configuration & controls
Define which preferences appear, eligibility rules, explanatory copy, update permissions, and the identity context needed to show them.
Workflow & architecture
The centre is a review-and-update surface for non-cookie preferences; cookie settings and formal withdrawal journeys can be designed separately.
This preference centre manages account or service preferences beyond browser cookies. A cookie preference centre manages browser-level cookie categories, while withdrawal is a separate revocation workflow.
Integrations
It can request current preferences from connected consent records and submit updates through defined interfaces. Account resolution depends on the surrounding application.
Security & audit
Record the preference category, prior and new selection, update time, and the authenticated or verified session context.
Implementation
- List preference categories.
- Design customer-facing labels.
- Define account lookup behavior.
- Map update destinations.
- Test changes across linked channels.
Related features
Product context
Preference Centre is a capability withinConsentifyAI's Consent Management Platform. Use the product page for commercial evaluation; this page explains the operational capability.
Solution context
See how this capability can support a broader business or compliance problem on therelated solution page.
Industry context
For sector-specific journey patterns, explore therelated industry page.
DPDP context
This feature page explains the product capability. Related DPDP glossary pages own the legal and regulatory explanation. The capability can support operational implementation; it does not by itself guarantee legal compliance.
FAQ
What is a consent preference centre?
A preference centre is a customer-facing view of non-cookie preferences and available choices. It retrieves relevant preferences, explains choices, and submits authorized updates.
How does a preference centre work?
It retrieves relevant preferences, explains choices, and submits authorized updates. Typical sequence: 1) Identify the person or account; 2) Load relevant preference categories; 3) Display current choices and explanations; 4) Accept selected updates; 5) Reflect the updated state in connected workflows.
How can users change their consent preferences?
Define which preferences appear, eligibility rules, explanatory copy, update permissions, and the identity context needed to show them. It retrieves relevant preferences, explains choices, and submits authorized updates.
Why do organizations need a preference centre?
People may need to revisit choices made in different product, service, or communication journeys. Support teams may handle routine preference changes manually. Without a defined control, preferences are scattered across individual journeys with no central review point.
How is a preference centre different from a cookie preference centre?
This preference centre manages account or service preferences beyond browser cookies. A cookie preference centre manages browser-level cookie categories, while withdrawal is a separate revocation workflow. Keeping these responsibilities separate prevents teams from treating related controls as interchangeable.
Who should own preference centre?
Ownership usually sits with the team accountable for the affected journey and policy, with privacy operations providing governance oversight. Define which preferences appear, eligibility rules, explanatory copy, update permissions, and the identity context needed to show them.
What should be configured first for preference centre?
Define which preferences appear, eligibility rules, explanatory copy, update permissions, and the identity context needed to show them.
Does preference centre guarantee DPDP compliance?
No. preference centre can support operational implementation of preference centre, but it does not by itself guarantee DPDP compliance because legal obligations depend on the organization’s processing context and controls.
See preference centre in your consent operations
Discuss how privacy platform administrators can use preference centre to address people may need to revisit choices made in different product, service, or communication journeys.
Book a Demo