The flags for creating profile data.
enum ids_bbprofile_create_data_flag{
IDS_PROFILE_CREATE_DATA_DEFAULT = 0x00000000
IDS_PROFILE_CREATE_DATA_ENCRYPT_D2D = 0x00000001
IDS_PROFILE_CREATE_DATA_CACHE = 0x00000010
};
BlackBerry 10.2.0
No options specified, and the creation will follow the default behavior where no caching and no extra encryption will be performed for the new entry.
To have additional encryption performed on the data prior to being stored remotely. Data is encrypted with dynamically generated keys shared between devices using the same BlackBerry ID user. Only devices with the same user will have the keys to decrypt this data. The keys are shared between devices and not included in backups or transferred as part of device swap, so if a user only has one device, and it is lost, the keys are not recoverable, and any remote data stored with this encryption will be non-recoverable. Performing a "Security Wipe" will retain the keys and the stored data is recoverable if the same user logs back into the device. If the user has multiple devices, and are data enabled, the devices with the same BlackBerry ID user will exchange the keys securely so that all of them can store and retrieve the data stored with this encryption. Operations will return IDS_NOT_READY while the encryption keys are exchanged; the app can repeat the request after a short wait to avoid failures during this one time key exchange window.
Override the default behavior to enable local data caching for this entry. In cases where the application may need data stored locally for quick or repeated access, the value can be cached securely on the device and retrieved on demand, even when not connected to the remote storage copy. The cache is synchronized with the remote copy so that the cache is always up to date while the device has appropriate data coverage.
Multiple flags can be combined using bitwise 'OR' unless stated otherwise. See the flags parameter in the ids_create_data() function for more information.