CONSENTUA captures the consent from a user via a unique user interface. Which provides the proof statement for the data controller/processor to have access to the users personal data.
This then allows an organisation to query what consents have been granted by what set of users. Which is a great report for marketing, an get of jail report for the DPO and legal team.
Check out the iframe UX.
Note all the data retrieved is delivered direct by the API.
Common user identifier (e.g. email/GUID) that your system identifies the user as. Consentua will inherit that identifier too.
Ability to access an external API (unless licensed in which case it is installed on premise).
Two routes. For a basic service, that has minimal change capability. Have instant access to Consentua today.
For standard, advanced and enterprise customers then a trial route is recommended. The Consentua team will help make sure you get the best out of the API.consentua.com/contact
Check out this blog here which gives an exampleconsentua.com/blog
Clearly articulating what personal data is going to be used - ‘Data Type”. As well as clearly describing what that personal data will be used for - ‘ Data Purpose’.
Consentua puts the consent service owner in control of describing both the type and purpose descriptions. This even extends to multi-lingual support.
Consentua takes the settings the user has saved on their screen via the Consentua WebSDK into a saved consent receipt.
This consent receipt is stored in a secure repository.
Consentua is a participant and member of the Kantara Initiatives Consent Receipt specification.
More details can be found here:kantarainitiative.org
The consent receipt can be shared and acted upon by requesting systems. This same view also allows the user to change what they have consented/agreed to.
The client consent owner is the arbiter of who can access the consent service and the receipts attached to that consent service.
Binary consent is your simple yes & no. Linear consent builds up as the interaction and data exchange grows.
Binary is great for single purpose with minimal data types. Linear is more useful when different service levels/quality can be delivered depending on the data exchanged.
We have a notifiable template that will email the consent service owner when invoked. The aim is that this template is available to be served via iframe the WebSDK when the user requests the ‘right to be forgotten’.
Ready in minutes. Read this blog here:
No further consulting or up front costs are incurred.consentua.com/blog
Designed to be business user led. The focus is on the language used to ask for consent. How the consent is captured in the user journey.
Some developer integration skill is required to deploy the webSDK into your page.
A report view is available that shows who has consented to a specific purpose. As well as what purposes a specific user has consented too.
Very useful for handling subject access requests and breach of notification notices. As it is possible to work out potentially what personal data is being processed based on the consent/opt-in provided.
A series of modules are available for integration with a wider range of SaaS platforms.
Modules under construction include: Salesforce; Wordpress, Moodle, Zoho, Mailchimp.
Supporting consented digital advertising. This is due to Consentua’s ability to have a retrievable consent receipt.
For insurance use cases the flexibility of the linear consent is beneficial, as the data request changes depending on the interaction (registering for insurance, versus making a claim).
Consentua can be used to present opt-in/opt-out choices. This is where legitimate interest means the notice of use of personal data is notifiable.
The endgame would ideally be the demise of your standard terms and conditions. Replaced by Consentua.
Registered as a data processor at the UK ICO. Signed up as an IAB Consent Management Platform.
Cyber Essentials certified.