Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device.getInfo pollutes localStorage without warning/consent #367

Closed
boennemann opened this issue Apr 29, 2021 · 1 comment · Fixed by #370
Closed

Device.getInfo pollutes localStorage without warning/consent #367

boennemann opened this issue Apr 29, 2021 · 1 comment · Fixed by #370

Comments

@boennemann
Copy link

boennemann commented Apr 29, 2021

Bug Report

Plugin(s)

device

Platform(s)

web

Current Behavior

When calling Device.getInfo() on the web this plugins writes a unique id to the localStorage.

Expected Behavior

Storing information on the users device requires consent under the EPrivacy Regulation

It is totally unexpected that an innocent sounding API like getInfo is actually creating the information in question, writing to the disk and thus very likely messing with the compliance of the consuming application.

This functionality should either be warned about, or even better not be the default.

Code Reproduction

await Device.getInfo()
localStorage.getItem('_capuid')
@boennemann boennemann changed the title Device.getInfo pollutes localStorage without consent Device.getInfo pollutes localStorage without warning/consent Apr 29, 2021
@ionitron-bot
Copy link

ionitron-bot bot commented Sep 30, 2022

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of the plugin, please create a new issue and ensure the template is fully filled out.

@ionitron-bot ionitron-bot bot locked and limited conversation to collaborators Sep 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants