Privacy Notice Post-Migration Guide
All users who previously had access to the Policy & Notice Management product will now have Privacy Notice Management once the migration is complete. Users can migrate existing content on their own using the manual process or they will be automatically migrated by the OneTrust Product Team. Once all users are successfully migrated, OneTrust will no longer support the Policy & Notice Management product and the services it supports. Due to this, the Policy & Notice Management product will no longer be visible to users in their tenants.
Users leveraging notice system roles will continue to have the same permissions and roles because roles are shared across the notice products. For more information, see Using System Default Roles.
Post-Migration Customer Actions
Live notices will continue to render on webpages post-migration for notices implemented using our SDK or plain text method. The table below describes the actions that must be taken by users based on implementation type once the migration is complete. These actions will help to ensure your notice content appears as expected.
|
Implementation Type |
Action Required |
|---|---|
|
SDK Integration |
Users who are not leveraging the entire SDK script in their notice implementation will be required to update the SDK scripts across their digital channels post-migration when a new version of the notice is published in Privacy Notice Management. Notices will continue to load after migration even if they have not used the whole SDK. Users leveraging the entire SDK script in their notice implementations across their digital channels will be migrated to the new privacy notice SDK post-migration. Leveraging the whole SDK refers to copying and pasting the whole notice SDK on your webpages without any manipulations. Any subsequent notice versions created in Privacy Notice Management will be reflected on the webpage upon publishing. For more information, see Frequently Asked Questions. |
|
Plain Text Integration |
Users using the plain text implementation should update their webpages post-migration to continue to render notice content. |
|
Integration Manager |
Users with existing integrations should recreate their integrations in the Integration tool for privacy notice pre- or post-migration. For more information, see Creating Integrations. |
|
APIs |
Customers using APIs must recreate APIs with the public Privacy Notice Management APIs pre- or post-migration. For more information, see Policy Management APIs in the Developer Portal. The parity GET APIs available today include: |
Things to Know
-
Users in a user group without the correct Privacy Notice Management permissions will not be migrated. This helps to reduce the number of users unable to access the product as the Policy & Notice Management version had no permission checks. OneTrust will provide users with a report and allow them to decide whether to give the user permissions or not.
-
Individual users without the correct Privacy Notice Management permission will not be migrated. In this scenario, OneTrust will use the default approver of the tenant's parent organization. If this user doesn't have appropriate Privacy Notice Management permissions, then we will leave the owners and approvers fields empty.
-
User groups associated with the Policy & Notice Management product with 100+ users will not be included in the migration.
-
The privacy notice time stamp and language drop-down will appear differently post-migration due to the enhanced user interface.
Frequently Asked Questions
What should I do if I would like to maintain access to the Policy & Notice Management product post-migration?
You can request access to the Policy & Notice Management product post-migration by contacting OneTrust Support. Once approved, you will only have access for 30 days. If you do not request access, you will no longer have access to Policy & Notice after the migration. The product will appear as read-only and the Preview and Integration tabs will be unavailable.
How do I know how if my privacy notice was implemented via SDK or plain text?
Notices Implemented via SDK
In Policy & Notice Management, if a notice is implemented with an SDK script, the notice will have populated website locations on the Locations tab of the Privacy Notice Details screen. To view website locations, the location must be enabled in the SDK.
Another way to confirm if the privacy notice was implemented with an SDK script is to check if the script is visible on Elements tab of the webpage where the notice is located. To access the Elements tab, right-click on the notice webpage and select Inspect. Your SDK script can be found on the Integration tab of the Privacy Notice Details screen in the OneTrust platform.
Notices Implemented via Plain Text
How do I know if my privacy notice is using the whole SDK script on my webpage?
You can follow either steps outlined below to confirm if your notice is using the whole SDK script.
Option 1: Check the inspection elements tab
-
Navigate to the webpage where the privacy notice is published. For example, the OneTrust Privacy Notice.
-
Right-click on the webpage and select Inspect.
-
On the Elements tab, press Ctrl + F (PC) or Command + F (Mac) and search for Privacy Notice start in the search bar.
-
Review the SDK code for the webpage. A privacy notice using the whole SDK script will have about 15 lines of code that are bracketed between <!-- OneTrust Privacy Notice start --> and <!-- OneTrust Privacy Notice end -->.
Option 2: Check for otnotice-1.0min.js and LoadNotices scripts
If both scripts below are found on the webpage your notice is located, the SDK will redirect to Privacy Notice Management and no actions are required post-migration.
-
Navigate to the webpage where the privacy notice is published. For example, the OneTrust Privacy Notice.
-
Right-click on the webpage and select Inspect.
-
On the Elements tab, press Ctrl + F (PC) or Command + F (Mac) and search for otnotice-1.0.min.js in the search bar. Ensure a script similar to the item highlighted below is present.
-
On the Elements tab, press Ctrl + F (PC) or Command + F (Mac) and search for LoadNotices in the search bar. Ensure a script similar to the item highlighted below is present.
What actions are required for existing customers not using the whole SDK script?
The Policy & Notice Management customers not using the whole SDK script will be required to update the SDK scripts in their webpages when a new version of the notice is created in Privacy Notice Management. Our recommendation would be to update notice SDKs post-migration to avoid any content rendering issues. For more information, see Integrating Privacy Notices.
Are there are any actions on customers to help with the migration?
There are no actions for customers to facilitate the migration, however, customers are advised to limit their activities in Privacy Notice Management on their migration date to ensure a successful migration. This guide provides customers with the post-migration steps necessary depending on how they originally implemented their notices.
Where can I engage with a migration expert and ask questions?
OneTrust is committed to supporting our customers through this change. If you have questions or concerns, please create a new post in the Product Announcements myOneTrust group. This is the dedicated community group for Privacy Notice Management migration where you can reach out to OneTrust experts for input.
Where can I access Privacy Notice Management resources to better understand the product?
Privacy Notice Management resources can be reviewed in the OneTrust knowledge base. Newly added functionality and enhancements will be mentioned in release notes.