Developer Portal

Compliance Visualiser

We’ve introduced a major upgrade to our Compliance Visualiser: when configuring your product in the Developer Portal, the Engine and Overrides tabs are now combined, allowing you to configure and view overrides directly within the Compliance Visualiser.

👉 Read the full blog post. 🚀

Global Minimums

You can now set global minimums for Digital Consent Age, Civil Age and permission-specific age criteria (Minimum Age, Threshold Age and Default Off If Under Age) that apply across all markets.

These global minimums will only take effect when:

• They are higher than a market’s existing age requirements, or

• A market has no specified ages.

This ensures that your global settings enforce stricter standards where necessary while preserving any local configurations, helping you enhance compliance across all jurisdictions.

Product API

We’ve added a new Product API (/age-gate/check-age-category) for retrieving the Age Category of the user: Digital Minor, Digital Youth or Adult.

👉 Read our blog post on Understanding Age Requirements. 🚀

Bugs & Enhancements

Family Portal

• UI Update: Redesigned the age verification success/failure acknowledgement screen across all flows to improve clarity and ensure a seamless user experience post-verification.

• Localisation Fixes: All user-facing pages in the Verifiable Parental Consent (VPC) flow — such as Access Request, Select Child, and Data Collection — now display additional translations for supported non-English locales (e.g., Japanese, French, German). Product-specific terms remain in English, and untranslated tags and labels have been removed.

Product API

• Security Enhancement: Added an optional targetOrigins parameter to Age Verification APIs. This ensures JavaScript events are securely delivered only to specified trusted domains, mitigating risks associated with wildcard (*) usage while maintaining backward compatibility.

• Digital Consent Age Override: Fixed an issue where overriding a jurisdictions’s Digital Consent Age (DCA) to a lower value caused the /age-gate/check endpoint to incorrectly enforce the default DCA during OTP validation. This update ensures that all age-gate validations now consistently respect jurisdiction-specific DCA overrides regardless of whether they are higher or lower than the default.