Frequently asked questions.
What is use.id and why do I have one?
You have a use.id account because you created one via the use.id website or via one of our partners. If you have gotten your use.id account via one of our partners, it is because this partner wants that you remain owner of your personal data so that you can have full control.
Your use.id account is a WebID just like your gmail account is an email address.
With your use.id WebID, you can store and exchange data, just like your email address enables you to store and exchange messages. A WebID does not rely on the email protocol, but instead relies on the Solid protocol.
With a use.id WebID you can easily compile and reuse your digital truth, regardless of where it is stored. Organisations that store data about you (e.g. your bank, …), can make this data available to you by sharing it in a digital Solid vault. You can easily compile all this data by connecting these vaults to your WebID. Once these vaults are connected, you can easily reuse the data that is stored in those vaults by granting other parties access.
Don't know which vaults to connect to your use.id WebID? Don't worry, we have you covered. By default, you get a use.id vault just for yourself. If more Solid vaults become available, we will make sure to send you a message.
Will use.id remain free to use?
There will always be a free version of use.id.
How can I contact the use.id team?
If you have a suggestion or if you want to contribute, feel free to contact email@example.com.
What is use.id's relationship to Solid?
The use.id service follows the latest version of Tim Berners-Lee's Solid protocol.
Is use.id open source?
A large part of the software on which use.id is built, is open-source.
Why can't I login to legacy apps like Penny?
Historically, many Solid compatible applications (like Penny, PodPro, ...) have been built against an old version of the spec. These legacy apps typically rely on user impersonation and do not have a WebID/ClientID document.
User impersonation happens when an application uses the token of the user to inherit the user's access rights. This is considered to be insecure because, using this method, an app can access all data which the user has access to (instead of certain parts of the data).
An app needs a WebID/ClientID document to specify what redirect URI's are allowed for authentication with Solid-OIDC. Typically, legacy apps have no WebID/ClientID document. For security reasons, use.id does not support logging in to apps without such a document.