Datavault Holdings

Privacy Policy

Our Privacy Policy

Introduction

This policy sets out the basis on which we will process any personal data or usage information we collect from you, or that you provide to us, in connection with your use of our website at https://data-donate.com (the “Website”), our Data Vault function at https://vault.data-donate.com and use of our tools: Protocol, DVT Network Token, DVT Hub.

Please read this policy carefully so that you understand your rights in relation to your personal data, and how we will collect, use and process your personal data. If you do not agree with this Privacy Policy in general or any part of it, you should not access the Website, use our Chat or Lisk Services.

You may visit our site anonymously

if you choose to register on our website, four categories of data to and on behalf of you will be processed:



“Account data”

When you register for an account on our site, place an order, subscribe to our newsletter or respond to a survey, basic contact details are collected such as the e-mail address and name of your contact person, company name, address, phone number, VAT number, preferred language and currency, any purchase order number, any e-mail address of invoice receivers and masked credit card or bank account details.



“Configuration data”

We collect your direct input to our cloud service Cookiebot (the “Service”) after login, like the domain name(s) of the website(s) where you implement the Service and configuration of the content, looks and behavior towards website visitors (“End Users”).



“End User Data”

Data generated by End Users browsing your website(s) using the Service. When an End User submits a consent from your website(s), the following data are automatically logged at DVT:

The End User’s IP number in anonymized form (last three digits are set to ‘0’). The date and time of the consent. User agent of the End User’s browser. The URL from which the consent was submitted. An anonymous, random and encrypted key value. The End User’s consent state, serving as proof of consent. The key and consent state are also saved in the End User’s browser in the first party cookie “CookieConsent” so that the website can automatically read and respect the End User’s consent on all subsequent page requests and future End User sessions for up to 12 months. The key is used for proof of consent and an option to verify that the consent state stored in the End User’s browser is unaltered compared to the original consent submitted to Cybot.

If you activate the Service feature “bulk consent” to enable consent for multiple websites by a single End User submission, the Service will also store a separate random, unique ID with the End User’s consent. If all of the following criteria are met, this key will be stored in an encrypted form in the third party cookie “CookieConsentBulkTicket” on the End User’s browser:

What do we use your information for?

You may visit our site anonymously

 

if you choose to register on our website, four categories of data to and on behalf of you will be processed:

 

 

“Account data”

When you register for an account on our site, place an order, subscribe to our newsletter or respond to a survey, basic contact details are collected such as the e-mail address and name of your contact person, company name, address, phone number, VAT number, preferred language and currency, any purchase order number, any e-mail address of invoice receivers and masked credit card or bank account details.

 

 

“Configuration data”

We collect your direct input to our cloud service Cookiebot (the “Service”) after login, like the domain name(s) of the website(s) where you implement the Service and configuration of the content, looks and behavior towards website visitors (“End Users”).

 

 

“End User Data”

Data generated by End Users browsing your website(s) using the Service. When an End User submits a consent from your website(s), the following data are automatically logged at DVT:

 

The End User’s IP number in anonymized form (last three digits are set to ‘0’). The date and time of the consent. User agent of the End User’s browser. The URL from which the consent was submitted. An anonymous, random and encrypted key value. The End User’s consent state, serving as proof of consent. The key and consent state are also saved in the End User’s browser in the first party cookie “CookieConsent” so that the website can automatically read and respect the End User’s consent on all subsequent page requests and future End User sessions for up to 12 months. The key is used for proof of consent and an option to verify that the consent state stored in the End User’s browser is unaltered compared to the original consent submitted to Cybot.

 

If you activate the Service feature “bulk consent” to enable consent for multiple websites by a single End User submission, the Service will also store a separate random, unique ID with the End User’s consent. If all of the following criteria are met, this key will be stored in an encrypted form in the third party cookie “CookieConsentBulkTicket” on the End User’s browser: