Hello,
we are facing a problem regading a local storage entry, which is set by the bitmovinplayer-ui.js. Please see attached screenshot. On behalf of our data privacy we have to get rid of this entry. Is it possible to remove that part of the code in the ui.js?
https://cdn.bitmovin.com/player/web/8/bitmovinplayer-ui.js?ver=2023-06-12
Best,
Michael
Hi Michael,
As you can see also in the code of our open source UI, this is just used to test if localStorage would be even available, and the item is immediately removed again: https://github.com/bitmovin/bitmovin-player-ui/blob/c7e1a1927e9185ba16b9af4481736a782b0fb455/src/ts/storageutils.ts#L15-L16
I’m wondering if it is still an issue as the data is immediately removed again?
The localStorage in the Player UI is only used to store/load user settings for subtitle styling, as can be seen here: https://github.com/bitmovin/bitmovin-player-ui/blob/c7e1a1927e9185ba16b9af4481736a782b0fb455/src/ts/components/subtitlesettings/subtitlesettingsmanager.ts#L101-L119
This save/load is not done per default, the implementation is only in place so developers can easily make use of it.
Having said that, there is currently no built-in way to completely disable the localStorage access. The only option at the moment would be to fork the UI repository and make some changes.
I can also forward your request to our engineering team to change this behavior but I’m afraid I can’t provide any timeline and when this might get changed.
Hi Daniel, thanks for your feedback. According to our legal department, setting the entry is a data privacy problem, even if it is immediately deleted. It would be great, if you could check the topic with your engineers. Best regards, Michael
Sorry Michael, I missed to update this post. I did create an internal ticket for this but there is no ETA at the moment.
As our UI is open source, please feel free to submit a Pull Request with desired changes if you have the resources to implement this improvement.
Hi @michael.adomeit,
I’m happy to let you know that UI version 3.57.0 was released, which has a solution for this problem by exposing a new disableStorageApi configuration.
