Product Updates

Text Customization for Consent Manager

posted on August 16, 2021

Depending on the location where users are accessing your site and the language the browser is set to, users see a specific and localized version of Osano's Consent Manager. But we know that the language within that notice might impact your opt-in rates. Now, you can customize that message to the specific ways it fits your company's customer base.

It's important to note that Osano's default pop-up language is what we believe complies with applicable cookie laws, so companies modifying the language should check with legal counsel to be sure any changes don't impact your compliance status.

Why does this matter?

It’s a documented fact now that online users are starting to feel worried about the number of cookies sites deploy on them. Consumers are becoming more savvy on the ways sites are collecting their personal information. This is partly due to newsmaking privacy laws like the California Consumer Privacy Act, which requires a visible opt-out button for consumers to reject the sale of their personal information by the site collecting the information to third parties. 

So the more transparent you can be, the better. But it can be difficult to explain that in a very small box in a very succinct way. So communication is key. 

In a 2020 Deloitte study on cookies, researchers looked at 167 websites across 12 countries in the EU to take the pulse. How are companies deploying cookies? Which are doing so effectively? 

The study found that the “perception of an organization can be largely influenced by the way it handles its cookies. Implementing user-centric methods to manage cookies and adopting sophisticated tools to gather consent can be important and unique selling points and can grant organizations a relative competitive advantage.”  

That is, the way you communicate to users what it is you’re asking them for within your consent pop-up or banner will impact your opt-in rates. While there are certain requirements from which you can’t deviate (you have to notify users and obtain consent before you place cookies, period) there is some room to tailor that depending on the message you want to convey. You may have even conducted internal testing that indicates what kind of language, colors or fonts help customers feel comfortable clicking “yes.” For example, maybe your customers are more likely to click a cookie preferences button that says “Got It” versus a button that says “Save.”

Product(s) Affected

Core Platform



Legacy Browser Support

posted on May 10, 2021

The Osano consent management platform now includes a legacy browser support toggle.

Legacy Browser Toggle

Within a website’s code includes everything required for the site to function. That lump sum of code is called a “bundle.” The bigger the bundle, the slower a site will load.

Because very few sites use Internet Explorer 11, Osano now allows customers to disable Legacy Browser Support off, which will remove support for older browser such as IE11 from the bundle, decreasing the time it takes the page to load.

Why does this matter?

One element of SEO is page performance. Customers who don’t need to support IE 11 now have the ability to turn off support for end-of-life legacy browsers. Osano performance is improved when legacy browser support is disabled.

Product(s) Affected

Consent Management



Role-Based Access Control

posted on May 10, 2021

Role-Based Access Control allows Osano administrators to restrict application access based on a person's role within the organization. 

It's essential to keep your systems tight. Deciding what happens with a user's data is an important decision that should be based on training on laws and regulations, as well as the promises a company has made to customers within the privacy policy. Role-Based Access Control (RBAC) allows Osano administrators to decide who has access to which data within an organization. User access takes into consideration a multitude of factors, including authority, responsibility and job function. You can also limit access to specific product features and control the user's ability to view, create or modify those features. The aim is to keep data secure and allow users to focus on relevant tasks while restricting access to functions outside their access level.

An example might be: A company has many people all in charge of specific features within it. There's a customer support team that deals specifically with data subject access requests. But you don't want that group to have access to changing aspects of your website's consent manager, vendor litigation or product analysis. Role-Based Access Control allows you to assign roles to individual users that limit that access.

Why does this matter?

Role-based access control gives customers the ability to manage which areas of a particular system their users can access at a granular level to maintain compliance with various security standards. The solution is in line with the security principle "Give the fewest amount of people the least amount of access possible to do their jobs." 

The National Institute for Standards and Technology proposed RBAC in 1992. Since then, it's become the standard for many large organizations, as well as government organizations. While the EU General Data Protection Regulation doesn't specifically mandate RBAC, it does call for organizations to "implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk."

Implementing RBAC should include a data inventory, defining roles (who should have access to what), an information-campaign for employees on the policy and regular audits to ensure it's working.

Product(s) Affected

Core Platform



The managed data privacy platform

Get started with Osano today

Explore Osano

What's New at Osano

Stay GDPR compliant under new French ruling

Privacy regulators at the CNIL in France recently declared that Google Analytics violates GDPR. Osano’s new block list feature can disable Google Analytics in France to keep you compliant while allowing you to use Google Analytics in regions where it is still legal.


New in May 2022: DSAR conditional fields, 28 new integrations, and more!

Customize DSAR forms with conditional fields, serve consent banners in additional languages, use 28 new integrations for Data Discovery, and more! Check out our latest product announcement blog for demos, links, and more information.


New in April 2022: Admin notes, IAB TCF updates, and more!

Collaborate on DSARs with internal notes for request submissions. IAB TCF 2.0 Consent Management support has been updated per the latest IAB specifications. 11 new Data Discovery integrations and more! Check out our latest product announcement blog for demos, links, and more information.


New in March 2022: attachments, config sorting, and more!

Send and receive attachments in the Data Subject Rights secure messaging portal, filter and sort capabilities for your Consent Management configuration, and much more! Check out our latest product announcement blog for demos, links, and more information.


Introducing AMP support for Osano Consent Manager

Capture and manage consent across your standard and AMP pages using the same Consent Management Platform.

Learn more about Osano for AMP

View more product updates

Osano product & engineering teams have been hard at work. View the full list of all product updates.

View Product Updates