• Increase length limit from 128 to 512 characters for DataDome cookie to support upcoming features
• Handle 429 status code (Too Many Requests) responses from Protection API to support upcoming features

• Increase length limit from 128 to 512 characters for DataDome cookie to support upcoming features
• Handle 429 status code (Too Many Requests) responses from Protection API to support upcoming features

• Increase length limit from 128 to 512 characters for DataDome cookie to support upcoming features
• Handle 429 status code (Too Many Requests) responses from Protection API to support upcoming features
• Add support for custom fields on payloads using static or dynamic values

The target date announced here has been updated in order to leave more time to make the required change.

New target date

Monday, February 23, 2026

Required change (reminder)

If you are using the frame-src directive in your Content-Security-Policy headers with a direct reference to geo.captcha-delivery.com, you will need to proceed with the change below:

• ❎ Before: frame-src geo.captcha-delivery.com
• ✅ After: frame-src *.captcha-delivery.com

Without this change, some of your end users might experience issues with displaying response pages in case of false positives.

Reference documentation: JavaScript Tag

• Fix module configuration issue

• Detection improvements

• Detection improvements

• Initial release

• Fix a potential StackOverflowError when handling cookies in version 3.0.7 after upgrading from a previous SDK version

Fix cookie management issue inside the iOS native module