Before You Begin

Before you start using the SDK, learn about the latest features, supported languages, third-party dependencies, and our data collection policy. Refer to the Messaging Glossary to familiarize yourself with the messaging terms we use at Salesforce.

To learn about new features, API changes, fixes, and known issues, refer to the release notes.

• Release Notes for iOS
• Release Notes for Android

• The iOS SDK stores information in the app’s keychain data. If you explicitly delete this content, the SDK won’t be able to access essential information and may fail to work properly.
• The Android SDK stores information in the app’s shared preferences and key store. If you explicitly delete this content, the SDK won’t be able to access essential information and may fail to work properly.

The Messaging for In-App mobile SDKs support the following languages:

• Arabic: ar
• Chinese (Simplified): zh-Hans (iOS), zh (Android)
• Chinese (Traditional): zh-Hant-TW (iOS), zh-rTW (Android)
• Czech: cs
• Danish: da
• Dutch: nl
• English: en
• Finnish: fi
• French: fr
• German: de
• Greek: el
• Hebrew: he (iOS), iw (Android)
• Hungarian: hu
• Indonesian: id (iOS), in (Android)
• Italian: it
• Japanese: ja
• Korean: ko
• Norwegian: nb (iOS), no (Android)
• Polish: pl
• Portuguese: pt-BR (iOS), pt-rBR (Android)
• Romanian: ro
• Russian: ru
• Spanish: es
• Swedish: sv
• Thai: th
• Turkish: tr
• Ukrainian: uk

To learn more about customizing strings in the SDK, see Customize Strings for iOS and Customize Strings for Android.

Your Salesforce org can support the languages specified in the Supported Languages document.

The Messaging for In-App SDKs use the following third-party libraries.

• Encrypted Core Data SQLite Store
• Simple Keychain
• SQLCipher

• Android Material Components (com.google.android.material:material)
• Bumptech Glide (com.github.bumptech.glide:glide)
• Jetbrains Kotlin Libraries (org.jetbrains.kotlinx:kotlinx-coroutines-android, org.jetbrains.kotlin:kotlin-reflect, org.jetbrains.kotlin:kotlin-script-runtime, org.jetbrains.kotlin:kotlin-stdlib-jdk8)
• JSON Web Token Libraries (io.jsonwebtoken:jjwt-api, io.jsonwebtoken:jjwt-impl, io.jsonwebtoken:jjwt-orgjson)
• Moshi JSON Libraries (com.squareup.moshi:moshi-adapters, com.squareup.moshi:moshi-kotlin, com.squareup.moshi:moshi-kotlin-codegen)
• OkHttp Libraries (com.squareup.okhttp3:logging-interceptor, com.squareup.okhttp3:okhttp-sse)
• Retrofit Libraries (com.squareup.retrofit2:retrofit, com.squareup.retrofit2:converter-moshi, com.squareup.retrofit2:converter-scalars)
• Salesforce Mobile SDK Encryption (com.salesforce.android:encryption)
• Zetetic SQLCipher (net.zetetic:android-database-sqlcipher)

The software development kits (“SDKs”) provide access to software tools, that when embedded into a mobile application, help enable the collection and transmission of data to perform basic operations required for the service. Data collected through Messaging for In-App and Web falls into three categories: pre-chat data, messaging data, and logging data. For more detailed information about each category, refer to these sections.

• Data types collected:
  • Personal info such as name and email. Most pre-chat forms contain some personal info.
  • Other info. Other data collected depends on how you design your pre-chat form.
• Details: All data specified in the pre-chat form is securely transmitted to Salesforce using HTTPS communication (TLS 1.3). Depending on how you handle pre-chat data, this data is stored in Salesforce during your service subscription, or until you take action to delete it. You can change this behavior from Salesforce. You can even remove the pre-chat form altogether.

• Data types collected:
  • In-app messages. User messages get sent to agents through Salesforce.
  • Photos. Users can send photos to agents.
  • Other info. Any content a user types into a message is sent to an agent or chatbot.
• Details: All user messages are securely transmitted to Salesforce using HTTPS communication (TLS 1.3). This data is stored in Salesforce during your service subscription, or until you take action to delete it.

• Data types collected:
  • App interactions
  • Other actions
• Details: For logging purposes, we send anonymized information to Splunk servers using HTTPS communication (TLS 1.3). This data doesn't contain any customer-identifiable or hardware-identifiable information. We log info about how users interact with the SDK, and we log some basic system information while they use the SDK, such as battery stats.