Adding GDPR consent manager into the DApp

[arrenv]

Specification

Story

With Colony adding more features that help to make the app user experience better, it requires storing more user data that does not need to be or is not suited to be stored on chain and using 3rd-party services. All of these updates require that we abide by GDPR policies with two main implications in the app including enabling consent functionality for storing user data, allowing users to download their data, and allowing users to delete their data that we are storing.

Description

As a start, we need to implement consent management, as we move to CDApp we will need to implement data downloading and deletion.

There seems to be a lot of ways to implement consent management GDPR, so, please feel free to review options and arrange a chat to discuss the most suitable ways to implement. Here are some examples:

• Build our own solution
• Use a package - https://github.com/hashbite/consent-manager
• Using Segment - https://github.com/segmentio/consent-manager, this also would require adopting the full Segment stack which is paid.
• Using an open source service - https://github.com/kiprotect/klaro
• Using paid services:
  • https://www.cookieyes.com/
  • https://www.onetrust.com/products/cookie-consent/
  • https://www.consentmanager.net/

Design

Figma link - Consent Banner