Trust Center Migration Guide and FAQ
The Trust Center replaces outdated, fragmented tools like the DSAR portal and preference center with a single modern and easy-to-deploy platform, which is fully customizable and embeddable on any of your websites.
The Trust Center features drag-and-drop configuration, instant branding, robust localization, and mobile responsiveness, allowing you to launch powerful privacy experiences in minutes. Ongoing enhancements mean you can always have the latest in security, compliance, and user experience.
Review this guide and FAQ to for everything you should know about migrating from the preference center to the Trust Center.
Transitioning from the preference center to the Trust Center
There is no data migration involved, and you can freely have Trust Centers and preference centers coexist.
- Customize your Trust Center
-
:Build your new Trust Centeraccording to your preferences, orcopy your preference centerand adjust branding.
- Publish your Trust Center
-
: Once you are satisfied with the setup, publish it.
- Update links
-
: Replace all links to the old preference center on your websites, apps, footers, emails, etc. with a new Trust Center link.
Note:If you previously used an iFrame for your preference center, embed it instead.
- Adjust integration workflows
-
: If you haveintegration workflows that use event filters, ensure you add thecollection point ID of your new Trust Centerto these filters.
To facilitate this transition, two tools are available:
-
Copying the preference center into the Trust Center.
This process allows you to transfer all copiable content from your preference center into the Trust Center. All content, translations, and structure will be carried over. Branding will be automatically adjusted based on your organization's branding in OneTrust. Because additional branding cannot be copied, we encourage you to explore the Trust Center's new branding options.
-
Redirecting the preference center to Trust Center.
This process redirects all traffic from the old preference center to the Trust Center for a period of 90 days. This ensures a smooth transition and allows users to update their navigational workflow while outdated links are replaced.
Full feature parity between the Trust Center and the preference center is in progress. Functionality differences are currently being addressed individually so we can prioritize the most requested enhancements.
If you are not ready to migrate to the Trust Center due to missing features, visit the Trust Center ideas space to upvote existing ideas or submit new ones. Voting strongly affects the timeline for each enhancement.
You can also view the public roadmap for upcoming features over the next 3–6 months.
FAQ
When will the preference center be deprecated?
As part of our continued investment in the Trust Center, we are working toward achieving full feature parity with the Preference Center by early 2027.
Once feature parity is achieved, we will announce a one-year deprecation period for the current Preference Center, with planned retirement in early 2028. This transition timeline is intended to provide customers with sufficient time to plan and complete their migration activities.
Please note that the Legacy Preference Center (older than OneTrust version 6.2) was retired in Summer 2026 and is no longer editable by either external or internal users. We strongly encourage customers who have not yet done so to begin migrating to the Trust Center, which will serve as our strategic long-term platform for preference and consent management.
We will continue to provide updates and migration guidance throughout this transition to help ensure a smooth customer experience.
Why is OneTrust making this change?
This transition is necessary to shift from the current preference center technology to the Trust Center, which will enable us to innovate, deploy updates faster, meet accessibility standards, and address long-term usability challenges.
We believe that the business world is moving towards Trust Centers as a unified portal for showcasing your data and AI governance programs, empowering your users with greater control. Our vision is to create an adaptable and flexible architecture that supports a variety of use cases, helping organizations build trust with their consumers.
For your own users, this is an opportunity to create a single experience for anything related to data, AI, and their rights, and embed it wherever they already are.
Will the magic link tokens stay the same?
Yes, the tokens are unique to each data subject and are not tied to the preference center, so they will remain unchanged.
However, the magic link URLs will differ. When you use the Redirect to Trust Center functionality, magic links will redirect to the Trust Center.
Will the URLs change?
Yes, as we transition to the Trust Center, you will need to update any instances where the preference center URL is used.
To assist you during this transition, we recommend using the Redirect to Trust Center functionality. This will ensure that anyone attempting to access your previous preference center’s URL will be redirected to the Trust Center for 90 days.
Will custom CSS become available in the Trust Center?
Allowing custom CSS could hinder our ability to update the portal experience in the long run, as updates might disrupt existing customizations. The Trust Center is designed to be easy to configure while still offering customization options.
We plan to introduce more branding controls over time. We encourage customers to submit ideas in the Trust Center category for any customization features they feel are missing. We are actively implementing these to power up the Trust Center’s customization capabilities.
What about one-click unsubscribe?
Currently, one-click unsubscribe still relies on the preference center. We are developing a new version that will link to the Trust Center and address popular enhancement requests, which is expected to be available in 2026.
Can customers retain DSAR web forms?
Yes, DSAR web forms will continue to be the primary method for users to submit new privacy requests. The portal will be automatically replaced by a Trust Center by default, requiring no action on your part.
What should I do if my preference center is iFramed?
We recognized that iFrames presented security issues and lacked responsiveness for OneTrust users integrating portals on their websites.
The Trust Center can now be embedded as a web component, similar to the OneTrust embedded web form and CMP, eliminating the need for iFrames.
I am missing a feature I need. When will it be introduced in the Trust Center?
Our Product team actively reviews all ideas submitted in the Trust Center ideas space and links them to the enhancements that will be implemented. You can also check the public roadmap for visibility on upcoming features over the next 3-6 months.
We encourage you to vote for the features you are missing, as this significantly influences the timeline for introducing each enhancement!
Will reporting dashboards or metrics differ between the preference center and Trust Center?
The metrics being measured remain the same. Each Trust Center will appear as a separate collection point in the UCPM dashboards.
Will historical data migrate or remain separate?
Historical consent insights data will remain separate. You will be able to continue seeing historical data for your preference centers, even after deleting and redirecting them.
Are all current languages supported in Trust Center?
We have carefully selected a list of languages and their regional variants, removing some options which did not represent real-life regional variants. The following languages are available:
|
Language |
Language Code |
|---|---|
|
Afrikaans |
af |
|
Albanian |
sq |
|
Albanian (Albania) |
sq-al |
|
Amharic |
am |
|
Arabic |
ar |
|
Arabic (Bahrain) |
ar-bh |
|
Arabic (Egypt) |
ar-eg |
|
Arabic (Jordan) |
ar-jo |
|
Arabic (Kuwait) |
ar-kw |
|
Arabic (Lebanon) |
ar-lb |
|
Arabic (Oman) |
ar-om |
|
Arabic (Qatar) |
ar-qa |
|
Arabic (Saudi Arabia) |
ar-sa |
|
Arabic (Tunisia) |
ar-tn |
|
Arabic (United Arab Emirates) |
ar-ae |
|
Armenian |
hy |
|
Armenian (Armenia) |
hy-am |
|
Assamese |
in-as |
|
Azerbaijani |
az |
|
Azerbaijani (Azerbaijan) |
az-az |
|
Basque |
eu |
|
Belarusian |
be |
|
Belarusian (Belarus) |
be-by |
|
Bengali |
bn |
|
Bodo |
in-brx |
|
Bosnian |
bs |
|
Bosnian (Bosnia and Herzegovina) |
bs-ba |
|
Bulgarian |
bg |
|
Bulgarian (Bulgaria) |
bg-bg |
|
Burmese |
my |
|
Burmese (Myanmar) |
my-mm |
|
Catalan |
ca |
|
Central Khmer |
km |
|
Chinese (Simplified) |
zh-hans |
|
Chinese (Traditional) |
zh-hant |
|
Corsican |
co |
|
Croatian |
hr |
|
Croatian (Croatia) |
hr-hr |
|
Czech |
cs |
|
Danish |
da |
|
Danish (Denmark) |
da-dk |
|
Dogri |
in-dgo |
|
Dutch |
nl |
|
Dutch (Belgium) |
nl-be |
|
Dutch (Netherlands) |
nl-nl |
|
English |
en |
|
English (Australia) |
en-au |
|
English (Botswana) |
en-bw |
|
English (Canada) |
en-ca |
|
English (Great Britain) |
en-gb |
|
English (India) |
en-in |
|
English (Ireland) |
en-ie |
|
English (New Zealand) |
en-nz |
|
English (Singapore) |
en-sg |
|
English (South Africa) |
en-za |
|
English (U.S.) |
en-us |
|
Estonian |
et |
|
Estonian (Estonia) |
et-ee |
|
Filipino |
fil |
|
Finnish |
fi |
|
Finnish (Finland) |
fi-fi |
|
French |
fr |
|
French (Algeria) |
fr-dz |
|
French (Belgium) |
fr-be |
|
French (Canada) |
fr-ca |
|
French (France) |
fr-fr |
|
French (Luxembourg) |
fr-lu |
|
French (Morocco) |
fr-ma |
|
French (Switzerland) |
fr-ch |
|
French (Tunisia) |
fr-tn |
|
Frisian (Netherlands) |
fy-nl |
|
Galician |
gl |
|
Georgian |
ka |
|
Georgian (Georgia) |
ka-ge |
|
German |
de |
|
German (Austria) |
de-at |
|
German (Belgium) |
de-be |
|
German (Germany) |
de-de |
|
German (Liechtenstein) |
de-li |
|
German (Luxembourg) |
de-lu |
|
German (Switzerland) |
de-ch |
|
Greek |
el |
|
Greek (Cyprus) |
el-cy |
|
Greek (Greece) |
el-gr |
|
Greenlandic |
kl |
|
Gujarati |
gu |
|
Hausa |
ha |
|
Hebrew |
he |
|
Hebrew (Israel) |
he-il |
|
Hindi |
hi |
|
Hungarian |
hu |
|
Hungarian (Hungary) |
hu-hu |
|
Icelandic |
is |
|
Icelandic (Iceland) |
is-is |
|
Indonesian |
id |
|
Indonesian (Indonesia) |
id-id |
|
Irish |
ga |
|
Irish (Ireland) |
ga-ie |
|
Italian |
it |
|
Italian (Italy) |
it-it |
|
Italian (Switzerland) |
it-ch |
|
Japanese |
ja |
|
Japanese (Japan) |
ja-jp |
|
Javanese |
jv |
|
Kannada |
kn |
|
Kanuri |
kr |
|
Kashmiri |
in-ks |
|
Kazakh |
kk |
|
Kazakh (Kazakhstan) |
kk-kz |
|
Khmer (Cambodia) |
km-kh |
|
Kirghiz |
ky |
|
Konkani |
in-kok |
|
Korean |
ko |
|
Korean (South Korea) |
ko-kr |
|
Kurdish |
ku |
|
Lao |
lo |
|
Lao (Laos) |
lo-la |
|
Latvian |
lv |
|
Latvian (Latvia) |
lv-lv |
|
Lithuanian |
lt |
|
Lithuanian (Lithuania) |
lt-lt |
|
Luxembourgish |
lb |
|
Macedonian |
mk |
|
Macedonian (North Macedonia) |
mk-mk |
|
Maithili |
in-mai |
|
Malagasy |
mg |
|
Malay |
ms |
|
Malay (Brunei) |
ms-bn |
|
Malay (Malaysia) |
ms-my |
|
Malayalam |
ml |
|
Maltese |
mt |
|
Maltese (Malta) |
mt-mt |
|
Manipuri |
in-mni |
|
Maori |
mi |
|
Marathi |
mr |
|
Mongolian |
mn |
|
Montenegrin |
me |
|
Montenegrin (Montenegro) |
me-me |
|
Nepali |
ne |
|
Norwegian |
nb |
|
Norwegian Bokmål (Norway) |
nb-no |
|
Oriya |
in-or |
|
Pashto, Pushto |
ps |
|
Persian |
fa |
|
Persian (Iran) |
fa-ir |
|
Polish |
pl |
|
Polish (Poland) |
pl-pl |
|
Portuguese |
pt |
|
Portuguese (Angola) |
pt-ao |
|
Portuguese (Brazil) |
pt-br |
|
Portuguese (Portugal) |
pt-pt |
|
Punjabi |
pa |
|
Romanian |
ro |
|
Russian |
ru |
|
Russian (Belarus) |
ru-by |
|
Russian (Kazakhstan) |
ru-kz |
|
Russian (Moldova) |
ru-md |
|
Russian (Russian Federation) |
ru-ru |
|
Samoan |
sm |
|
Sanskrit |
in-sa |
|
Santhali |
in-sat |
|
Serbian |
sr |
|
Serbian (Serbia) |
sr-rs |
|
Shona |
sn |
|
Sindhi |
sd |
|
Sinhala |
si |
|
Sinhala (Sri Lanka) |
si-lk |
|
Slovak |
sk |
|
Slovak (Slovakia) |
sk-sk |
|
Slovenian |
sl |
|
Slovenian (Slovenia) |
sl-si |
|
Somali |
so |
|
Southern Sotho |
st |
|
Spanish |
es |
|
Spanish (Argentina) |
es-ar |
|
Spanish (Belize) |
es-bz |
|
Spanish (Bolivia) |
es-bo |
|
Spanish (Chile) |
es-cl |
|
Spanish (Cocos (Keeling) Islands) |
es-cc |
|
Spanish (Colombia) |
es-co |
|
Spanish (Costa Rica) |
es-cr |
|
Spanish (Dominican Republic) |
es-do |
|
Spanish (Ecuador) |
es-ec |
|
Spanish (El Salvador) |
es-sv |
|
Spanish (Guatemala) |
es-gt |
|
Spanish (Honduras) |
es-hn |
|
Spanish (Mexico) |
es-mx |
|
Spanish (Nicaragua) |
es-ni |
|
Spanish (Panama) |
es-pa |
|
Spanish (Paraguay) |
es-py |
|
Spanish (Peru) |
es-pe |
|
Spanish (Puerto Rico) |
es-pr |
|
Spanish (Spain) |
es-es |
|
Spanish (United States) |
es-us |
|
Spanish (Uruguay) |
es-uy |
|
Spanish (Venezuela) |
es-ve |
|
Sundanese |
su |
|
Swahili |
sw |
|
Swedish |
sv |
|
Swedish (Sweden) |
sv-se |
|
Tagalog |
tl |
|
Tagalog (Philippines) |
tl-ph |
|
Tajik |
tg |
|
Tamil |
ta |
|
Tatar |
tt |
|
Telugu |
te |
|
Thai |
th |
|
Thai (Thailand) |
th-th |
|
Traditional Chinese (Hong Kong) |
zh-hk |
|
Traditional Chinese (Taiwan) |
zh-tw |
|
Turkish |
tr |
|
Turkish (Turkey) |
tr-tr |
|
Ukrainian |
uk |
|
Ukrainian (Ukraine) |
uk-ua |
|
Urdu |
ur |
|
Uzbek |
uz |
|
Vietnamese |
vi |
|
Vietnamese (Vietnam) |
vi-vn |
|
Welsh |
cy |
|
Xhosa |
xh |
|
Yiddish |
yi |
|
Yoruba |
yo |
|
Zulu |
zu |
|
Zulu (South Africa) |
zu-za |
Does the Trust Center meet WCAG 2.1 or other accessibility standards?
Work to address accessibility concerns across eligible areas of the OneTrust platform, including the Trust Center, is ongoing. We update VPAT reports each quarter for Universal Consent & Preference Management and Privacy Rights Automation (DSR), which may include known areas of accessibility nonconformance related to the Trust Center.
Will using the Trust Center improve load times compared to the preference center?
We have not measured load times on either interface. If load times were a concern when you used the preference center, please raise an idea detailing the measurements used.
Are there any limitations on embedding multiple Trust Centers across different domains?
There is no limitation on embedding the same Trust Center on multiple domains, or multiple Trust Centers on the same domain. Make sure you add each domain to the Trust Center’s safelist.
Will redirects stop after 90 days, or can they be extended if required?
Redirects will stop after 90 days and they cannot be extended. If there are any concern, please contact OneTrust Support or your account representative.