Consent evidence

Everytime we collect consent from a user we collect and store the following data points to provide you with evidence of the specific consent.

The data points range from user input to system information and the audit trail and information will be available to you in our product. This means that you have full access to all consent metadata.

Metadata Description Example
User id The person who gave or retracted a specific consent. This is referenced in our product as “user id” and form the foundation of the audit trail. The user id will never change (but other pieces of information can, see below) 9PpUHcQbSPRTjVhW4nhDKtkd
Users name The name of the user at the same that the user gave his/her consent. The user’s name can be changed, but in the consent evidence it will never change. Niklas Stephenson
User email The email of the user in the moment the consent was collected. The email on the user can be changed, but in the consent evidence it will never change.
User identifier The identification of the user given by the company. 87654
User agent The user agent of the browser. Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36
User IP The IP adresse of the user when they gave consent.
User role The role defined by the company (B2C or B2B) B2B
Agreement revision A reference to the specific revision of the agreement that the user consented to. TrCxrkpnH4RFyhPZAG4ydJDz
Consent timestamp The date and time the user gave consent. In case of double opt-in, the consent is determined to be given at the time when the user confirmed by clicking the link in the email. Fri, 09 Aug 2019 07:50:33 UTC +00:00
Consent method The method used to collect the user’s consent. opt-in
Consent wording / text The text that was presented to the user when collecting the consent. I accept Openli ApS' Terms of Service and Privacy Policy
Date and timestamp of consent retraction The date and time the user retracted a specific consent. Fri, 09 Aug 2019 08:50:33 UTC +00:00
Agreement title The actual agreement text that the user consented to. This is applicable when users are consenting to long form agreements It will consist of a full copy of the current version of the agreement. E.g the full text of the privacy policy.
Form submit text (the call-to-action button text) The text of the button that the user clicked to submit the form (i.e. gave his/her consent). Sign up now
Language The language used to collect the user’s consent. English (en)
Jurisdiction The presumed jurisdiction of the user. This can be determined either by the IP address of the user or the information can be provided by the company. GB
Page URL The URL of the page where the consent was obtained. /signup/
Source The source of the consent. Can be legal.js (our widget), API or imported by the company. legal.js
Legal.js version The version of our legal.js code that saved the consent. 2.0.5
Snippet JS version The version of our snippet running on your website. 1.2.5
API SHA The version of our API saving the consent. e63859f2c68a93c86...
Location service version The version of location service used to determine the location of your user. 4.0.3