As of July 1, 2025, DataDome will no longer support the following browsers for CAPTCHA and Device Check:

• Improve thread safety of internal components

• Add challengeLanguage option to force challenges for XMLHttpRequest or Fetch requests to be displayed with a specific language and ignore language settings from the browser

• Unset conflicting enriched headers from client requests to prevent unintended overrides of DataDome empty value

• Remove Authentication field from the User structure
• Add AccountUpdateWithAuthentication functional option to set the Authentication field for account update events
• Add RegistrationWithAuthentication functional option to set the Authentication field for registration events
• Add PaymentMethodUpdated field to the User structure for account update events

Breaking changes

• Add mounted check to the challenge page to prevent calling setState after the page is disposed of, avoiding potential crashes

• Add CookiesList to payloads sent to Protection API

• Fix large HTML responses buffering to avoid truncation
• Fix crash in manual integration when requestId is not provided and an exception is raised
• Ensure manual response handling executes on a background thread to avoid blocking UI thread

• Fix race condition in challenge modal to ensure only one modal is shown at a time and block execution until it is resolved
• Replace @react-native-async-storage/async-storage with Android native CookieManager for cookie handling, to prevent potential challenge loops caused by manual cookie injection
• Improve support for TypeScript by generating types for the DataDome SDK
• Fix potential Captcha loop on iOS