Introducing Osano Automated DSAR Summaries and Deletion
Processing data subject access requests (DSARs) is a core part of...Read Now
The simple, all-in-one data privacy platform
Manage consent for data privacy laws in 50+ countries
Streamline the DSAR workflow
Ensure your customers’ data is in good hands
Gain insights with privacy assessment templates and workflow management
Discover how Osano supports CPRA compliance
Learn about the CCPA and how Osano can help
Achieve compliance with one of the world’s most comprehensive data privacy laws
Don’t let data privacy compliance get in the way of growth
Preserve your competitive edge
Manage data privacy at scale
Expert insights on all things privacy
Subscribe and become a Privacy Insider
Research the most essential privacy topics
We'll scan your website for privacy risk at no cost
The Osano story
Become an Osanian and help us build the future of privacy!
We’re eager to hear from you
No fines, no penalties
Add Osano data privacy ratings and recommendations to your application
Fresh duds for data privacy fans
June 8, 2022
From info requests to full deletion requests, DSAR intake forms do a lot of heavy lifting. Depending on the nature of the request and local laws, you may need more or less information from the data subject before they submit the form. But creating one form with every possible field you might want to know about is a poor user experience. The additional complexity of such a form can lead to mistakes in filling them out and prolong the time needed to process the DSAR.
Now, with conditional fields, you can create optional fields that only appear if a previous answer was selected. For example, conditional fields enable you to ask if a data subject has a power of attorney, and then provide a file upload field only if they answer, “yes.” Optional conditional fields can be configured on both dropdown and multiselect dropdown fields. Check out the docs for how to create a request submission form to learn more about setting up and configuring DSAR forms.
This month we added some language improvements to our Consent Management Platform (CMP) banners for Norwegian, Hungarian, and English.
ISO 639 is a common international standard used for websites and browsers to denote language using a 2-letter code. Norwegian has 3 possible language codes: Norwegian (no), Norwegian Bokmål (nb), and Norwegian Nynorsk (nn). Previously Osano CMP only supported no, but now contains support for nb and nn as well!
Osano supports banners in 40+ languages. Our pledged legally compliant banner text is generated in English, and then we use a combination of AI and manual translation to generate the text for each supported language. Because privacy laws are continually changing, we continually update our banners as well. From time to time we get feedback from native speakers on ways to improve our translations. Based on recent feedback from Hungarian users, we’ve tightened up our translations for Hungarian language banners.
Finally, some banner text has been updated for customers using IAB TCF 2.0 mode enabled when they want different options for opening the preferences drawer. Previously, the text said that customers could modify their cookie preferences, “by clicking on the cookie icon.” However, for users who want to use a link to open the drawer rather than our cookie icon, the text now reads, “by clicking on the cookie icon or link.” These changes are currently only available in English (en and en-gb language codes.)
Osano Data Discovery finds data fields in your apps and categorizes them using AI. Our growing catalog of 90+ integrations helps you:
This month’s new integrations:
For a full list of improvements see the May 2022 release notes.
Writer at Osano
Writer at Osano
Osano is used by the world's most innovative and forward-thinking companies to easily manage and monitor their privacy compliance.
Osano makes it easy. Ready to get serious about data privacy? Choose your plan and get started. All plans come with a 30-day FREE trial!