Users that consume content published with Prenly should expect that their personal data is processed according to the current applicable laws. The Prenly platform offers different tools to ensure this.
Within EU, as a Prenly customer you are responsible for informing your users about the data collected from the reader's device and the purpose of the collection.
Also, the user has the right to deny Prenly to store cookies or other data on their device (the computer's web browser or their mobile device), as long as it is not necessary for the service to function properly.
Software for handling user's consent are often called CMP:s (Content Manangement Platforms). Prenly offers a built-in consent handling feature called Prenly CMP that is managed in Prenly Workspace. Also, there are external CMP:s on the market for handling user consent, and Prenly supports a few of them. Currently we support Didomi, Cookiebot and Usercentrics.
The consent dialog is managed in Prenly Workspace by a user with the “owner” role. A customer can have multiple configurations - also different types of CMP:s - for different applications and even different devices. This means that in theory, one Prenly application can have a Prenly CMP consent dialog for web, a Didomi consent dialog for Android and a Usercentrics consent dialog for iOS.
A consent dialog configuration can also be used in multiple applications owned by the customer.
A guide on how to setup your consent dialog is found here:
For customers within EU/EES, to start using Prenly services a DPA (“Data Protection Agreement”) is signed, thatregulates how personal data within Prenly should be handled.
We aim at being specific regarding what personal data is handled and how, to make it easier for Prenly customers to comply with current laws and to be transparent against the actual users.