Use Secure Preference and DB

[jboxx]

Is your feature request related to a problem? Please describe.
Sensitive information exposed on the CleverTap SDK, preference should using secure preference since there's no one sure what client will sent to CleverTapAPI#onUserLogin

Describe the solution you'd like
As of security crypto was lowering down to SDK v21, please consider to use EncryptedSharedPreference

Describe alternatives you've considered
Use 3rd party library to make the SDK still available for v19

Additional context

[darshanclevertap]

@jboxx We are internally debating the use of Encrypted Shared Prefs for our SDK but since we support v19 and above, using this library is not a direct solution for us. Could you suggest 3rd party libs for versions below 21?
Meanwhile, to answer your question, we do use HTTPS when the onUserLogin API is used so your data is secure during transit.

[gerosprime]

Could you suggest 3rd party libs for versions below 21?

Got the same situation of OP. Would providing a custom storage or abstraction for different storage or even custom sharedpreference/SQLite database be possible?