Enhancements

• Streamlined domain management: We've implemented stricter validation rules during onboarding to prevent the addition of duplicate domains, ensuring a more organized and efficient domain management experience.

• Enhanced UI clarity: Improved the visibility of the loader within input fields, providing clearer feedback to users during ongoing actions.

BugFixes

• Modal interaction: Resolved an issue where the "X" button within modals could be clicked, potentially disrupting the intended user flow.
• Script URL consistency: Ensured script URLs are now environment-specific, guaranteeing proper functionality across different environments.
• Domain validation accuracy: Addressed a bug that caused domain validation to fail in specific onboarding scenarios.
• Domain validation responsiveness: Fixed an issue where domain validation would become unresponsive within the UI.
• Trial banner accuracy: Corrected an incorrect message displayed in the trial banner for users without owner roles, ensuring accurate information is presented.
• API performance: Improved the performance for a subset of APIs, leading to a more responsive user experience.

• Prevent script installation without successful scan report
  
• Managed long cookie names to avoid overlapping in declarations
  
• Legacy account users are now redirected to login form automatically
  
• Save button field in Banner template builder is always enabled
  
• Restored functionality of contextual consent preview
  

• "Undefined" instances in cookie declaration are now replaced with “-”

• The issue that caused the loader to not show on Pref Center loading has been fixed.

• We fixed discrepancies in the TCF v2.2 toggle state

This bugfix improves our scanner's functionality of accurately detecting certain cookies where the script sources begin with whitespace characters

Enforced "opt-in" mode for PIPEDA compliance module (SPV1-2979)

Case-sensitivity was added for whitelisted/blacklisted pages in the scanner "Settings" tab (SPV1-2965)

- Under some circumstances, cookies were not fully released when performing a rescan (SPV1-2902)

- Cookies with the same name placed by different sources are now showing as single entry (SPV1-2942)