Two updates to the Tizen TV SDK: Preference Center links can now open in the TV's system browser, and remote-control navigation across the Consent Banner and Preference Center has been sharpened throughout.

External link handling (v0.1.93)

• Preference Center links open in the system browser — External links surfaced in the Preference Center — privacy policy, cookie policy, support pages — now hand off to the TV's system browser instead of dead-ending inside the app. Users can read the linked content and return without losing their place in the consent flow.
• application.launch privilege support — The SDK now supports the Tizen application.launch privilege, which is what allows the app to open external URLs. Add it to your app's privilege list if you want external links enabled.

Navigation & interaction improvements (v0.1.92)

• Improved D-pad navigation — Focus movement across the Consent Banner and Preference Center is more predictable, so every control is reachable with the directional pad without unexpected jumps or dead ends.
• Left/Right toggling in the Preference Center — Consent toggles can now be switched with the Left and Right remote buttons, matching how Samsung TV users expect on/off controls to behave.
• Clearer focus visibility — The currently selected item is more visually distinct, making it easier to track position while navigating from across the room.
• Improved DSAR keyboard interaction — Entering details into the DSAR form using the on-screen TV keyboard is smoother and more reliable.
• Faster interaction response — General performance improvements to input handling for a more responsive feel on TV hardware.

Where to get it: Tizen TV SDK v0.1.93 is live now. For setup and configuration, see the Tizen TV SDK documentation.

We've added a new Consent Details section to the Preference Center, giving end users visibility into the exact consent record captured for them.

What's changed:

• Consent ID now visible to users — After a user grants consent, the Preference Center displays a unique Consent ID — the database identifier of their consent record. This ID can be used by account admins to look up the corresponding entry in the Consent Hub on the CMP Dashboard.
• Consent Date shown alongside the ID — The date and time the consent was provided is displayed together with the Consent ID, giving users a clear record of when they agreed.
• Section hidden until consent is given — The Consent Details section only appears once consent has been captured; it stays hidden for users who have not yet interacted with the banner.
• Configurable in Design settings — Display of the Consent ID can be disabled per Design if you prefer not to surface it to end users.
• Withdraw button in the Preference Center — Users can now withdraw their consent directly from the Preference Center without needing to interact with the banner again.

Support article was added here - Cookie Banner Buttons Explained: Accept All, Decline, Save and Withdraw Consent

Seat-Based Pricing — Add Users Without Changing Plans

We've introduced seat-based pricing for paid plans, giving teams flexible, on-demand control over how many users can access their account.

What's changed:

• Extra seats, on demand — Paid plans include a base number of user seats. Now you can purchase additional seats directly from your CMP dashboard at €5/month (or €50/year) per seat in EUR, and $6/month (or $60/year) in USD — no plan upgrade or support contact required.
• Immediate proration — Extra seats are added as a separate line item on your existing subscription and billed immediately with proration, so you only pay from the day you add them.
• Safe seat reduction — To reduce seats, remove the relevant users from your account first. The platform validates the change before applying it.
• Existing accounts unaffected — If your account predates this update and currently has more users than your plan's included limit, nothing changes. The cap applies only when you next add a user or switch plans. Enterprise and Advanced plans with unlimited users are unaffected.

Dedicated Sign-In for Google Tag Users

Users arriving from Google Tag or Google Tag Manager now have a sign-in experience built specifically for them.

What's changed:

• Google-first entry point — The new page surfaces Continue with Google as the primary — and only required — action. No email/password field to navigate past, no "Forgot password" detour.
• Deep-linkable URL — Available at a stable URL ready to bookmark
• Works on all devices — Responsive on desktop and mobile, with clear error messaging and a retry path for OAuth failures or cancellations.

CCPA Default Updated to Explicit Consent (Opt-In)

New Secure Privacy accounts now have CCPA configured with explicit (opt-in) consent and default cookie blocking enabled out of the box — no manual setup required.

This reflects current best practice in California, where enforcement around cookies dropped without prior user consent has increased significantly.  If you're an existing customer, we recommend reviewing your CCPA settings and switching to opt-in consent to stay aligned with this standard.

You can find the setting under your the CCPA template under your CMP Dashboard.

If your site sits behind a firewall, WAF, or other access controls, our compliance website scanner must be able to reach your pages. Without the correct allowlist, scans can be blocked and results may be incomplete or inaccurate.

Current scanner IP addresses (add these to your allowlist):

What to do

1. Add the IPs above to your firewall, WAF, or hosting provider allowlist.
2. Allow traffic both inbound and outbound for these addresses.
3. If you use a CDN or DDoS layer (e.g. Cloudflare, Akamai, AWS WAF), add the same IPs there if they enforce separate rules.

Important: Scanner IPs may change as we scale or maintain infrastructure. Check the allowlisting documentation regularly or subscribe to updates so your allowlist stays current.

Still blocked after whitelisting? Contact support@secureprivacy.ai.

iOS v0.3.4 and Android v0.4.5 are now available, with DSAR form alignment to the Preference Center API, backend-driven validation, and standardised error handling.

DSAR form & Preference Center (iOS v0.3.4)

• Dynamic required fields — Required-field indicators on the DSAR form are now driven by your Preference Center API configuration.
• Backend validation — Validation happens on the backend at submission; the SDK displays returned error messages in the UI.
• Standardised DSAR types — DSAR type values match backend enum definitions across platforms.

Error handling (Android v0.4.5)

• Error codes — New and standardised error codes with the ACP prefix for clearer diagnostics.
• DSAR type fix — Request type selection now correctly submits the user’s chosen DSAR type.

Where to get it: iOS — v0.3.4 on CocoaPods / Swift Package Manager. Android — v0.4.5.

Consent expiry and re-collection are now available across iOS, Android, and tvOS, so you can keep consent in sync with your configuration and expiry rules on all platforms.

Consent expiry & re-collection (iOS v0.3.3, Android v0.4.1, tvOS v0.1.5-beta)

Dynamic consent expiry — Consent can expire based on your configuration; the SDK automatically marks status for re-collection so users see the banner again when needed.

Re-collection on config change — When your package/category structure changes in the CMP, the SDK triggers re-collection so consent stays in sync.

More reliable consent state — Consent state is evaluated more reliably across app launches.

Do Not Store Consent — Option to avoid storing consent locally when your privacy policy requires it; the SDK skips local persistence when enabled.

Android only — DSAR form improvements (February patch)

Optional fields no longer block submission — The DSAR form no longer fails when optional fields are left empty; submissions succeed with required fields only.

Clearer validation messages — Better feedback when something needs to be corrected.

Where to get it:

• iOS — v0.3.3 on CocoaPods / Swift Package Manager
• Android — v0.4.1 for consent/re-collection; v0.4.3 for the DSAR patch
• tvOS — v0.1.5-beta

Laws Report

We have improved the Laws Report from the aspect of performance, accuracy, and overall user experience.

With this improvement, we are looking at enhanced visitor tracking and UI/UX consistency. Head over to Domain Settings -> Laws report. 

Refactored Data Mapping Logic:
Previously, the chart was mapped through template names. The new implementation maps data based on predefined regions, ensuring cleaner, more meaningful visualizations.

Visitor Tracking Update:
The report now tracks visitor data instead of only consent data. This change is supported by an improved backend logic for more accurate reporting and region-specific insights.

Cookie Classification Quality of Life (QoL) Improvement

You can now jump straight from a cookie in the scan report to its classification screen with a single click.

Review the Scan Report -> Cookies section today!

We’re excited to announce that Meta Consent Mode is now supported in Secure Privacy! 🎉

With this update, you can:

• Control how the Meta Pixel and Conversions API behave based on your users’ consent choices.
• Ensure no Facebook requests or cookies are sent until consent is granted.
• Automatically send grant or revoke signals to Meta when users update their preferences.
• Stay compliant with GDPR and other privacy regulations while continuing to measure ad performance.

For a full guide on setup and usage, see our Support Article on Implementing Meta Consent Mode.

We’ve also introduced the ability to fully customize your Data Subject Access Request (DSAR) form in Secure Privacy.

What’s new?

• Add custom controls such as textboxes, checkboxes, and more
• Reorder or remove fields to match your business needs
• Provide clearer instructions to users directly on the form
• Save changes instantly and update your live form with one click

Head over to our support article for more information on How to Customize the Data Request Form in Secure Privacy

We’ve added support for tables in the Secure Privacy Policy Editor.

With this enhancement, you can now:

• Insert tables directly into privacy and cookie policies
• Add and edit content inside table cells
• Easily customize tables by inserting or deleting rows and adjusting properties

This makes it easier to organize information and present policies in a clear, structured format.

For more information, refer to the support article.

We've rolled out an important update to our web platform, bringing enhanced functionality and tighter alignment with our Mobile App SDKs.

These improvements will help you manage compliance for your mobile applications directly from your Secure Privacy dashboard.

Direct Legal Template Assignment for Mobile Apps:

You can now assign legal templates (e.g., Privacy Policies, Cookie Policies) directly to your mobile applications via the dedicated mobile app screen within the web platform. This simplifies the process of ensuring your app's legal documentation is always up-to-date.

Policy Assignment for Mobile Apps 

Similar to templates, policies can now be directly associated with your mobile applications through the mobile app screen, providing a unified management experience for your app's compliance settings.

Bug Fixes & Styling Improvements

We've implemented various bug fixes and styling enhancements across the platform to ensure a smoother, more reliable, and visually consistent user experience.

With our latest Android SDK v0.2.9-beta release, we have rolled out updates to give you more control and clarity in managing user consent:

Flexible Consent Options

• Added full support for both explicit and implicit consent types, giving you greater flexibility in how you capture user permissions based on your legal requirements and user experience goals.

Smarter Category Mapping

• Significantly improving category mapping, we have ensured our SDK's behavior perfectly aligns with your backend and web configurations.
• This resolves previous issues, including the Customer Interaction category being visible, so your consent settings are consistently applied everywhere.

Streamlined Opt-Out Experience

• For those using opt-out templates, the Preference Center now intelligently auto-enables relevant categories, simplifying the setup and ensuring a smoother user experience while maintaining compliance.