ID-Vault takes away the hassle of wallets and blockchain by providing a free and easy to implement OAuth interface and unlocking variable credentials, claims and proof. Ever implemented Facebook or Gmail? Then ID-Vault should be a breeze !
ID-Vault wouldn't be ID-Vault if we didn’t have some thoughts on tracking cookies. So that why we offer our own cookie alternative. That, does not collect data about users but collects data for users.
So how does that work? When you place the ID-Vault trace code on your website the users actions aren’t logged to a big data set where you can analyse them. InsteadIn stead the are logged into the respective user wallet’s (if that user is known to us) or to anonymized dataset.
What does that mean?
In general an applications gets way less info then with (for example) an facebook or gmail tracing cookie. You see what amounts of users visit what page, how long they stay there and when they leave your website. You won’t see there age, sex, etc. And you cant follow individual users trough your website.
So wait, this provides way less information then google? ehm, yes…. that exactly the point.
So way should I use it as an application? First of all (since we don’t follow behavior) you won’t need a cookie warning, but more importantly because its the right thing to do.
But here is a twist, since a user has al of his account in its vault it can actually choose to share its data with you (that goes a bit further then a cookie warning). In that case you can trace actions to a specific user and actually get more data then you get with for example google. You just need to convince the user to voluntarily share it with you.
ID-Vault wouldn't be ID-Vault if we didn’t have some thoughts on tracking cookies. So that why we offer our own cookie alternative. That, does not collect data about users but collects data for users.
So how does that work? When you place the ID-Vault trace code on your website the users actions aren’t logged to a big data set where you can analyse them. InsteadIn stead the are logged into the respective user wallet’s (if that user is known to us) or to anonymized dataset.
What does that mean?
In general an applications gets way less info then with (for example) an facebook or gmail tracing cookie. You see what amounts of users visit what page, how long they stay there and when they leave your website. You won’t see there age, sex, etc. And you cant follow individual users trough your website.
So wait, this provides way less information then google? ehm, yes…. that exactly the point.
So way should I use it as an application? First of all (since we don’t follow behavior) you won’t need a cookie warning, but more importantly because its the right thing to do.
But here is a twist, since a user has al of his account in its vault it can actually choose to share its data with you (that goes a bit further then a cookie warning). In that case you can trace actions to a specific user and actually get more data then you get with for example google. You just need to convince the user to voluntarily share it with you.