Yes, click here for more information .

Yes, click here for more information.

Yes, click here for more information.

Yes, click here for more information.

Yes, the Sprinklr SDK supports Swift Package Manager (SPM) starting from version 10.0.0

Click here for more information

No, we do not have any SDK available in Xamarin, but you can write your own wrapper above our native SDK.

Yes, we support both Kotlin and Java.

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

The following table shows the supported locales:

Yes, Live Chat SDK supports RTL and LTR locales both.

From version v11.0.0, the Sprinklr Live Chat Mobile SDK supports iOS 15.1 and above.

From version v11.0.0, the Sprinklr Live Chat Mobile SDK supports API Level 24 and above.

The increase in app size after integrating the Live Chat SDK depends on the platform and framework:

• Native / Flutter

  • iOS: ~6MB

  • Android: ~14–16MB per architecture (ARMv7, ARM64, x86)

• React Native

  • iOS: ~7MB

  • Android: ~6MB per architecture (ARMv7, ARM64, x86)

No, this is not supported. You cannot switch Live Chat app_ids once the Sprinklr Live Chat SDK is initialized (i.e., once takeOff is called).

The following details are captured by default:

• Mobile SDK Version

• User Agent

• Operating System

• Operating System Version

• Device

• IP Address

• Time Zone

• Country and City

• Device Brand

• Device Name

• Language/Locale

No, once the app is uninstalled, we do not maintain any session data.

Please refer here to know how Sprinklr stores session data on the mobile device of an app using our SDK.

We have an active connection established within the SDK. However, this connection is broken when the application goes into the background or is killed. We have not observed any performance issues due to this behavior.

Images or videos captured through the camera are stored in a temporary folder within the app's cache. These files are not saved permanently and can be cleared either manually by the user or automatically by the operating system when it needs to free up space.

Transcripts are stored in a temporary folder within the app's cache. It is not saved permanently on the device and can be cleared either manually by the user or automatically by the operating system when it needs to free up space.

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

Yes, our SDKs handle Push notifications. You can refer to this article here

There are 2 approaches:

1. Please refer here to see push notification setup configuration.

2. The second approach will be through API Integration so that our backend can send the notification directly to your backend. For more information, Please refer here

Please refer here to know how to find your mobile API key.

Chat trigger icon is managed by brands, not Sprinklr. So any customisations required around visibility/customisations will have to be handled by the Brand themselves.

As of now, no older SDK Versions are deprecated. Starting August 2025, Sprinklr will support v7.0.0 and onwards.

If there are any future updates or new versions of the SDK, rest assured that we will promptly notify you via email. Our commitment is to maintain backward compatibility with previous and current versions, ensuring a seamless experience for our users. In the rare event that we anticipate a breaking change due to external dependencies in a previous version, we will proactively inform you well in advance, along with a working solution.

• For React Native apps, you can customise the peer dependencies. Please refer here.

• For Native and Flutter Apps: To ensure the proper functioning of the SDK, you must install all the dependencies as specified in the documentation.

Yes, the SDK leverages react-native-keychain (Android Keystore / iOS Keychain) to securely derive and store data.

For more information, see Live Chat Mobile - Storage Details.

Currently, Sprinklr's Live Chat Mobile SDK encrypts sensitive data before storing it locally to ensure user privacy and safeguard against unauthorized access.

For more information, see Data Stored on Device.

For native iOS projects, we deliver the SDK as a framework that includes the necessary header files, while the core implementation logic resides in an accompanying executable, keeping the internal details hidden.

Our core business logic is implemented in JavaScript (React Native), and the bundled code is packaged with the framework in an obfuscated form.

Our SDK does not include a polymorphic engine or self-mutating code. We follow industry-standard code protection practices rather than runtime code mutation.

Our core business logic is implemented in JavaScript (React Native), and the bundled code is packaged with the framework in an obfuscated form.

This is in the roadmap and not prioritized currently since our core business logic is implemented in JavaScript (React Native), and the bundled code is packaged with the framework in an obfuscated form.

We distribute it through a private npm registry and verify package integrity using checksums, so the artifacts you install are validated at source.

Not applicable – as part of shared responsibility we would rely on the parent app to take care of it.

Yes. For more information, see the following:

• Android

• iOS

The following data is stored on the user device:

Data Stored on Device

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

Not applicable - as part of shared responsibility we would rely on the parent app to take care of it.

Yes, the following data is stored on the user device:

Data Stored on Device