EDRLab: Difference between revisions

Line 11:

EDRLab is one of the main contributors to [[Readium]] LCP DRM. Their EPUB reader application, Thorium Reader, which uses LCP, does claims to be private, yet it has "non-personal" data collection that the user cannot opt out of. It also contacts EDRLab's servers every time the application is started.

This is not apparent, since Thorium's installer doesn't inform the user of this, there are no "agree/disagree" options and Thorium's interface does not directly link to either the ~~terms~~ of service or the ~~privacy~~ policy. Users also wouldn't be notified if the privacy policy were to change, since that would require them to manually check the ~~privacy~~ policy page for updates.

This is not apparent, since Thorium's installer doesn't inform the user of this, there are no "agree/disagree" options and Thorium's interface does not directly link to either the Terms of service or the Privacy policy. Users also wouldn't be notified if the privacy policy were to change, since that would require them to manually check the Privacy policy page for updates.

The Terms of service also mentions that the user agrees to "indemnify and hold harmless the EDRLab" even for "alleged" breaches by the user of the ~~terms~~ of service. It is also stated that "EDRLab Parties have the right to monitor the use of the Application."

The Terms of service also mentions that the user agrees to "indemnify and hold harmless the EDRLab" even for "alleged" breaches by the user of the Terms of service. It is also stated that "EDRLab Parties have the right to monitor the use of the Application."

The application is also marketed as open source yet it is stated in the privacy policy that it is in fact not entirely open source, but rather has a "small software library used as core for the Readium LCP DRM, which does not store or send any data." This requires users to trust the company on their word, since users cannot inspect the application, as they may not "rent, sell, modify, decompile, disassemble, reverse engineer or transfer the Application in whole or in part", according to the Terms of service. Furthermore, this connects directly to the 2nd paragraph.

@@ Line 11: / Line 11: @@
 EDRLab is one of the main contributors to [[Readium]] LCP DRM. Their EPUB reader application, Thorium Reader, which uses LCP, does claims to be private, yet it has "non-personal" data collection that the user cannot opt out of. It also contacts EDRLab's servers every time the application is started.
-This is not apparent, since Thorium's installer doesn't inform the user of this, there are no "agree/disagree" options and Thorium's interface does not directly link to either the terms of service or the privacy policy. Users also wouldn't be notified if the privacy policy were to change, since that would require them to manually check the privacy policy page for updates.
+This is not apparent, since Thorium's installer doesn't inform the user of this, there are no "agree/disagree" options and Thorium's interface does not directly link to either the Terms of service or the Privacy policy. Users also wouldn't be notified if the privacy policy were to change, since that would require them to manually check the Privacy policy page for updates.
-The Terms of service also mentions that the user agrees to "indemnify and hold harmless the EDRLab" even for "alleged" breaches by the user of the terms of service. It is also stated that "EDRLab Parties have the right to monitor the use of the Application."
+The Terms of service also mentions that the user agrees to "indemnify and hold harmless the EDRLab" even for "alleged" breaches by the user of the Terms of service. It is also stated that "EDRLab Parties have the right to monitor the use of the Application."
 The application is also marketed as open source yet it is stated in the privacy policy that it is in fact not entirely open source, but rather has a "small software library used as core for the Readium LCP DRM, which does not store or send any data." This requires users to trust the company on their word, since users cannot inspect the application, as they may not "rent, sell, modify, decompile, disassemble, reverse engineer or transfer the Application in whole or in part", according to the Terms of service. Furthermore, this connects directly to the 2nd paragraph.