Skip to content

Privacy settings

Alexander Boldyrev edited this page Oct 31, 2024 · 14 revisions

MobileMessaging SDK has several options to provide different levels of users privacy for your application. The settings are represented by PrivacySettings class and may be accessed and modified as follows:

MobileMessaging.privacySettings.carrierInfoSendingDisabled = true
MobileMessaging.privacySettings.systemInfoSendingDisabled = true
MobileMessaging.privacySettings.applicationCodePersistingDisabled = true
MobileMessaging.privacySettings.userDataPersistingDisabled = true

Descriptions

  • carrierInfoSendingDisabled: A boolean variable that indicates whether the MobileMessaging SDK will be sending the carrier information to the server. Default value is false.

  • systemInfoSendingDisabled: A boolean variable that indicates whether the MobileMessaging SDK will be sending the system information such as OS version, device model, application version to the server. Default value is false.

  • applicationCodePersistingDisabled: A boolean variable that indicates whether the MobileMessaging SDK will be persisting the application code locally. This feature is a convenience to maintain SDK viability in case of possible application code changes. Default value is false.

    Notice

    There might be situation when you want to switch between different Application Codes during development/testing. If you disable the Application Code persisting (value true), the SDK won't detect the Application Code changes, thus won't cleanup the old Application Code related data. You should manually invoke MobileMessaging.cleanUpAndStop() prior to start otherwise the SDK would not detect the Application Code change. Another option is to use MobileMessaging.withApplicationCode(_ code: String, notificationType: MMUserNotificationType, forceCleanup: Bool) fabric method with forceCleanup parameter set to true each time you want to change your Application Code.

  • userDataPersistingDisabled: A boolean variable that indicates whether the MobileMessaging SDK will be persisting the User Data locally. Persisting user data locally gives you quick access to the data and eliminates a need to implement the persistent storage yourself. Default value is false.

In-App messages

Feature is available since 11.0.0-rc version. Javascript is enabled for the webView for this feature to work properly, but it's possible to Disable In-app messages

Clone this wiki locally