Our product evolution continues, thanks to your invaluable feedback!

Google Consent Mode OR IAB Framework

Starting today, users of Secure Privacy can select between Google Consent Mode and IAB framework. his stems from the valuable feedback we've received from our customers!

Head over to {Your Domain Name} -> Domain Settings -> Framework -> Type to choose between Google Consent Mode or IAB framework

Improved Detection of Google Cookies in Scans

In previous instances, customers utilizing Google Consent Mode reported an issue with relevant Google cookies not being blocked. This release addresses this issue by ensuring that relevant cookies are now detected during scans when consent mode is enabled.

Trial Subscription

As a part of this release, we have changed the way your subscription is treated when the trial ends. After the trial, you’ll transition from the Advanced Plan to the Business Plan.

Enhanced Email Filter

We’ve trained our email filter block some spam emails that sneak through the platform. 

Tinkering Behind the Scenes

We’ve also been busy improving our public APIs, refining product analytics, and fixing those bugs that love to hide in the details.

• Resolved an issue where the SecurePrivacy signup page incorrectly displayed banners intended to appear only after the user has logged in.
• Updated placeholder on the SignUp form, which will indicate that we only accept business email addresses.
• We also fixed some issues related to caching and the translation in IAB banner

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)