Consent Management App & Web

since the introduction of the general data protection regulation, known as gdpr gdpr in 2016, it’s mandatory within the eu to ask your users for permission to track and analyse their user data gdpr gdpr mandates that consent must be freely given users must have a genuine choice to accept or decline consent without facing adverse consequences specific consent must be granular, covering distinct processing purposes informed users should be adequately informed about data processing activities unambiguous there must be a clear affirmative action indicating agreement revocable users must be able to withdraw their consent easily at any time a consent management platform (cmp) is a specialized tool designed to help organizations comply with gdpr gdpr 's consent requirements cmps provide a user interface for collecting, storing, and managing consents across various digital platforms, ensuring that all interactions with users are compliant with gdpr standards how consent management works in purple apps purple offers integrations with various cmps, such as consent manager docid 8bzzqxdxp7zrsr5ryql7r sourcepoint docid 3mu9ilvg zkx49k1yrwtw traffective docid\ orgzsneznsm01ti06py6 usercentrics docid\ nttmf59uybwwrxvjsq7bl every customer uses their own respective cmp and has a particular contract with the cmp provider product in the product, we neither know what cmp must be configured nor its external configuration and access please refer to the sub pages or the respective documentation of the cmps to learn more about their capabilities additionally, purple apps on ios comply to apple's app tracking transparency (att) framework, a privacy feature introduced by apple that requires app developers to ask for user consent before collecting data across apps and websites owned by other companies att is part of apple's broader effort to enhance user privacy and give users more control over their personal information explicit consent requirement apps must request permission to track a user's activities across apps and websites through a standardized prompt transparency users are informed about what data will be tracked and for what purposes, providing a clear understanding of how their data will be used user control users can grant or deny tracking permissions on a per app basis, allowing them to tailor their privacy settings to their preferences compliance and enforcement apps must comply with att guidelines or face removal from the app store, ensuring adherence to apple's privacy standards first consent screen this is an example modal consent screen of a configuration with 'sourcepoint' in a purple app in this example, the primary buttons are 'reject all' and 'accept all' and additionally there is a 'show options' link a specific tracking/analytics service in your app will only be loaded if the user has consented to the service either by consenting to all or to the specific tracking/analytics service by clicking " accept all " otherwise the tracking/analytics service(s) are not loaded this consent can be revoked at any time second consent screen often there are two layers used, the first one is like the one on the screenshot above and the second one displays the detailed configuration of all services this screen can also be made accessible for the user via the app menu, so that she/he has the option to change the settings anytime for you to open the screen, in the purple experience or another html in the app, it can be shown via js api or action ur l read details below js api you can use the js api as follows anywhere in your code await window\ purple consent showprivacymanager(); action url you can use the action url as follows anywhere in your html show privacy settings find an example of this 2nd screen, made with a 'consentmanager' configuration, below