D1d1sxeyes·Jan 17, 2023
Also not a lawyer, but I think it would technically count as personal information because it's a preference. Even if it's to provide functionality requested by the user, it would still be necessary to inform the user that this preference is being stored, etc.
However, I agree to your second point, that asking the user's browser to store the information, and then have the browser make decisions based on that without anything being shared back probably does not violate GDPR as it wouldn't count as 'processing'.
It would seem (although, without a deep dive into the codebase, I can't be 100% sure) that the tool just adds a class to the body: https://github.com/themesberg/flowbite-react/blob/765fedb3c9...
If this is the case, I think it unlikely that this would be found to be a GDPR violation as Flowbite (or the company which has deployed Flow
Read the rest
bite) would not normally be able to detect this preference.
It would be different if for example the preference caused a different stylesheet to be downloaded, which could then be combined with server logs, but overall, it seems as though all of the processing of the data (whether you consider it personal or not) is done entirely on the user's computer, and there would be no processing of any data by the company which has deployed Flowbite, therefore it would not open up any GDPR liability.
Once again though, IANAL.