Joystream / Joystream/joystream-org
Clarify privacy statement about tracking of keystrokes, mouse movements, scrolls, taps, and clicks
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
## Problem
What are we talking about: https://wccftech.com/websites-keylogging-session-replay
**This is ok for testing purposes but it might be worth considering if these are really needed in production.**
As you can see #409 joystream.org uses livesession.io to submit keystrokes and mouse movements to google cloud servers in the USA.
In response to #438 the privacy policy was updated in #462 to [list](https://github.com/DzhideX/joystream-org/blob/352aa48c75c6ba81a5a66bed2831a028bed17f4d/src/locales/en/privacy-policy.json#L35) livesession and link its [security statement](https://livesession.io/security/) (thanks @DzhideX!).
> "content": "Company uses <0>Google Analytics, with IP anonymization, to collect statistics on Website and the version of App hosted by us. All customisable data sharing settings are turned off to improve the privacy of Users. <1 /><1 /> Company also uses <3>Livesession to help us find bugs, improve UX and more by using session replays. Sensitive data such as passwords and IP addresses are anonymized. <1 /><1 /> <2>Company will not sell your data for advertising, or other purposes."
https://livesession.io/security/
> LiveSession provides encryption, security, and stability for all of the customers’ data. We always handle the data only in a scope permitted by the relevant regulation and by our customers.
> The data is stored in the United States (Iowa) datacenter on GCP infrastructure.
https://livesession.io/help/gdpr/
> A session replay is a reconstruction of the user’s journey on a website or within a web application. It consists of mouse and keyboard movements, scrolls, taps, and clicks. Watching a session replay feels like sitting next to the user and watching them interact with your website.
> When you use LiveSession on your website, you allow the service to process user data. There are two main ways of processing data, passive and active.
> Passive processing is related to session replays stored on Google Cloud. As our client, you’re the only person who can access this data.
> Active processing involves the data you send us intentionally, such as company details, email addresses, and the names of your employees. You need to share this information to use our service.
## Solution
The privacy statement needs to be more clear about what user data is stored / transmitted and where (to). Cookies are only one part. Anyone familiar with GDPR knows that data of EU citizens must not leave the EU. A common misconception is that it is sufficient to inform users. Including trackers before [consent](https://gdprinformer.com/gdpr-articles/5-consent-practices-avoid) is in violation of the policy. There needs to be a process for deletion (“right to be forgotten”) of user data (in backups!). Does JSG employ a [DPO](https://gdprinformer.com/gdpr-articles/company-need-dpo)?
The most impressive cookie popup i have seen so far was on https://mouseflow.com.
Users can protect themselves with browser extensions like uBlock or PrivacyBadger or Brave / Tor Browser.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.