March 2026 Release Notes

What's new for Osano in March 2026

Note: Any Consent Manager Platform (CMP) changes will be inherited by consent manager configurations after they are republished. Please be sure to test all changes.

Enhancements

• March 18 12:00 PM CDT

  • Subject Rights

    • You can now complete multiple manual action items at once with a note that results were found and acted on. This expansion of the bulk complete functionality allows you to more accurately record the work done outside of Osano to fulfill subject rights requests.

• March 17 9:00 AM CDT

  • Cookie Consent (Web application and script)

    • We've added an optional setting that lets you automatically delete category-specific cookies and local storage when a user withdraws consent.

      • New toggle in the Web App to delete storage on category opt-out (off by default).

      • When enabled, cookies/local storage associated with an opted-out category are removed after the user saves their updated consent.

• March 13 12:00 PM CDT

  • Assessments

    • Assessment Admins are no longer required to answer assessment questions that have been assigned to other users. You can now submit without answering these questions even if they are required.

• March 12 4:30 PM CDT

  • Cookie Consent (Web application)

    • You can now export account-level data for your consent configurations directly from the Configurations listing page. In order to see the export button, a user must be an Admin role in the account. The export will include all non-deleted configurations in the account and does not respect UI filters.

    • This CSV export provides raw, account-wide data designed for use in a reporting or BI tool.

Bug Fixes

• March 30 4:00 PM CDT

  • Cookie Consent (Script)

    • Resolved several WCAG compliance issues reported by customers following accessibility audits, including:

      • Grouped form controls (radio buttons, checkboxes) now have proper accessible names per WCAG guidance.

      • Additional ARIA labeling improvements to banner UI components.

      • Consent banner's close button was not properly exposed to assistive technologies.