I have been asked to identify myself with CheckedID (and have questions)

CheckedID identification

We understand that when you are first asked to identify yourself with CheckedID you may want to know a little more. How does CheckedID relate to the requesting party, who is behind it?

On this website, the accompanying privacy statement and CheckedID terms of use (found in the app) we have explained who we are and how we handle ID verification and your personal data with care.

If you still have additional questions, they may be answered below.

FAQ

What is the relationship between JanusID and the client that asks me to identify myself with CheckedID?
JanusID acts in GDPR terms as a processor for a client, the controller for the relevant personal data. How we do this for them is described in detail in our privacy statement which you can find at the bottom of the web pages.
Why am I not allowed to hide certain data from my ID when using CheckedID?
Our customer, your requesting party, receives from us only those data and images that are appropriate for the processing purposes applicable to them. So if, for example, they are not allowed to process the person number, this will not be reported to them. The reasons why you should not hide data: 1) In order to verify the authenticity of your ID document, we need to be able to read the MRZ (Machine Readable Zone) at the bottom of your ID in its entirety. 2) The MRZ also contains the key with which we can unlock the chip in your ID document and then read it out. 3) We use your passport photo to determine, by comparing to the selfie you have taken, that you are the actual owner of the ID document.
I would like to know 1) what technical measures you have taken to store personal data securely, 2) what retention period you use, and 3) for what purpose you store my personal data.
What is important in answering these questions is the role we play as JanusID (processor) in relation to our customers (controller). This is described in the CheckedID privacy statement. Information regarding the exact operation of our system in relation to our customer / your requesting party, such as retention period used, shared personal data, etc. is only available to our customers. We refer you to them for any further information.
Why do I have to download an app?
The reason we use a (native) app is conscious one: it offers 1) the best user experience, 2) no risks as a result of phishing, 3) no chance of data leaks, and 4) the certainty of a correct result in one go (e.g. by reading ID-document chip). As for the last point, with a web-based solution, the quality of the ID copy and (if even possible) the selfie can vary greatly. This makes the correct (optical) reading of the ID document and the comparison of the selfie with the photo of the ID document more difficult, with a greater chance of errors and so-called false rejects. With CheckedID we offer the certainty that you have a correct result in one go. That is also the reason that banks use native apps for their services, and not web-based apps. Native apps are the norm in the financial world. We believe the protection of personal data is so important that we only entrust it to "bank grade" native apps.

Want to know more about CheckedID?

Read more